Skip to content
Amy Chamber
VotingResultsBack to Amy
Log In
Amy Chamber/Privacy

Amy Chamber

Amy Chamber Privacy Notice

Version 1.0Effective 10 November 2026

PrivacyTerms

On this page

  1. 1. Who is responsible
  2. 2. Information involved
  3. 3. Evaluation environments
  4. 4. Special category information
  5. 5. Why information is used and lawful bases
  6. 6. Uses we do not make
  7. 7. Access and sharing
  8. 8. How long information is kept
  9. 9. Service exit, deletion and backups
  10. 10. International transfers
  11. 11. Cookies and browser storage
  12. 12. Security
  13. 13. Your rights
  14. 14. Changes to this notice
On this page · 14 sections
  1. 1. Who is responsible
  2. 2. Information involved
  3. 3. Evaluation environments
  4. 4. Special category information
  5. 5. Why information is used and lawful bases
  6. 6. Uses we do not make
  7. 7. Access and sharing
  8. 8. How long information is kept
  9. 9. Service exit, deletion and backups
  10. 10. International transfers
  11. 11. Cookies and browser storage
  12. 12. Security
  13. 13. Your rights
  14. 14. Changes to this notice

This notice explains how personal information is handled when you visit the Amy Chamber public pages, make a Chamber enquiry or use an approved Chamber evaluation or workspace.

An organisation that uses Chamber for real meetings will normally also need to give participants, members and staff its own privacy information.

1. Who is responsible

Amy Chamber is provided by Amy On Bera Ltd, a company registered in England and Wales with company number 17260558.

Registered office: 67 Elm Road, Leigh-On-Sea, England, SS9 1SP.

Email: theteam@amyonbera.com.

For public enquiries, account administration, our own business records and security processing that we determine, Amy On Bera Ltd is a controller.

An organisation using Chamber for a real meeting normally decides why participant, meeting and voting information is used and is the controller for that information. Where Amy handles that information only on the organisation’s documented instructions, Amy acts as its processor.

Where support or diagnostic records contain the organisation’s meeting or participant information, we continue to handle that content on the organisation’s instructions when acting as processor. Separate business administration or security processing for which Amy determines the purpose is identified and handled according to that separate purpose.

A signed service agreement and data processing schedule will define the roles for a live site in more detail.

2. Information involved

A Chamber enquiry may include your name and email address and, if you choose to provide them, your organisation, message and photos or screenshots.

The current enquiry design allows up to three PNG, JPG or WebP files, with a 5 MB limit per file and 10 MB in total. Do not send confidential, sensitive or personal information unless it is necessary for the enquiry and you are authorised to share it.

There is no public self-service Chamber registration. Amy creates named access for an approved evaluation or under a site-specific agreement.

Account and access information may include your name, work email address, organisation, access level, login and password-reset events, activity and support records.

A real deployment may handle meeting setup, participant names and identifiers, seat or device assignments, attendance or identification status, discussion-unit state, votes and results, and equipment or connector events. The actual data fields used for a live site must be documented for that site.

Technical systems may also process IP addresses, timestamps, browser details, error information and security events.

Information may come from you, your organisation and its authorised operators, connected conference equipment, the Amy Connector and the hosting or authentication systems used to provide the service.

3. Evaluation environments

Evaluation environments are intended for fictional or properly anonymised meeting content. They are not approved for live council, committee or other real meeting data.

Evaluation access may use broader permissions than a contracted production site. A live deployment requires a site-specific access model, named authorised users and tested permissions before real meeting information is loaded.

Real evaluator contact details, login records and support information are still personal information even where the demonstration meeting content is fictional.

4. Special category information

Party affiliation or an attributable voting record can reveal a person’s political opinions. Political opinions are special category personal data.

The organisation using Chamber is responsible for identifying an appropriate lawful basis under Article 6 of the UK GDPR and, where special category information is processed, a separate Article 9 condition and any additional safeguards required by law.

Amy will process that information on the organisation’s documented instructions where acting as processor.

This notice does not itself authorise an organisation to collect political-affiliation or attributable voting information.

5. Why information is used and lawful bases

For Amy’s own processing, we use enquiries and attachments to understand and respond to a request, discuss a possible deployment and keep a useful record of the conversation.

We use account and support information to provide authorised access, respond to support requests, protect the service, diagnose faults and maintain appropriate security and operational records.

For Amy’s own processing, we normally rely on our legitimate interests in operating and securing the service and responding to business enquiries, steps requested before a contract where applicable, performance of a contract where we contract with an individual, and legal obligations where relevant.

The organisation using Chamber is responsible for identifying and explaining the lawful basis for its own meeting and voting purposes.

6. Uses we do not make

We do not sell client meeting information.

We do not use client meeting content or identifiable voting records for advertising, behavioural profiling, model training or unrelated product research.

We do not independently publish a customer’s meeting records. The customer organisation decides what meeting information it publishes and which authorised users can see individual voting information.

We do not make solely automated decisions from Chamber meeting records that have legal or similarly significant effects on individuals. Counting votes and displaying results supports the organisation’s own meeting process; it is not an independent Amy decision about a person.

7. Access and sharing

Access to Chamber information is limited according to the role and purpose involved.

For an evaluation, only approved users should receive access and no real meeting information should be entered.

For a live site, the customer organisation nominates its authorised users and agrees the access model. Amy personnel or named technical contractors may access information only where needed to provide, support, secure or troubleshoot the agreed service and subject to appropriate confidentiality and processing arrangements.

Hosting, email, storage, authentication, backup, monitoring and support providers may process information where needed to provide those services.

Where Amy acts as processor and uses a sub-processor, the required processing arrangements and customer authorisation are handled through the service agreement and data processing schedule.

Hiding a live total or an individual vote on a screen does not by itself make the stored vote anonymous. Storage, access, publication and export settings must be considered separately.

8. How long information is kept

These are Amy’s standard operating periods. They are business defaults based on purpose, not statutory periods that apply to every organisation. A live customer may agree a different justified meeting-data period before real data is used.

Unconverted enquiries: up to 24 months after the last meaningful contact.

Enquiry images and attachments: deleted within 90 days after the enquiry is closed unless a specific file is needed for an agreed project or documented case.

Necessary contract, billing and project correspondence: during the relationship and normally for six years after it ends.

Ordinary support correspondence: up to 24 months after resolution.

Support attachments: deleted within 90 days after resolution unless selected material remains necessary for a documented continuing case.

Account access: disabled when authorisation ends. Standalone account profile information is deleted or anonymised within 90 days after deactivation, except information still required in a separately retained meeting, support, security or contractual record.

Routine operational and security logs: up to 90 days from creation.

Raw connector diagnostic samples: up to 30 days from collection. Where specific records are necessary for an open support or security case, they are restricted to that case and the need is reviewed at least every 30 days.

Selected support or incident evidence: up to 12 months after case closure unless a legal requirement or documented legal hold requires longer retention.

Meeting content, attributable votes and related in-app meeting activity: our standard live-site offer is 12 months from meeting closure. The customer must approve that period or a documented alternative before real meeting data is used. The customer remains responsible for its official archive and for copies it exports and controls.

Standalone participant-directory information: retained while authorised and needed for the service and removed within 90 days after removal from the active directory unless a historical record separately requires the attribution.

Our agreed retention schedule applies to the relevant copies we control in active cloud systems and managed connectors. Technical delivery copies may have shorter periods. Customer-controlled exports are governed by the customer’s own arrangements.

9. Service exit, deletion and backups

At the end of a live Chamber service, the customer chooses return or deletion of its data, subject to law and the service agreement.

Our standard exit timetable gives the customer 30 calendar days to export its data. Unless earlier deletion is instructed, active client data is then deleted within a further 30 calendar days.

Restricted recovery backups expire within 90 days after active deletion. During that period the deleted information is beyond ordinary use and is retained only for recovery or a legally required hold.

Under this default timetable, final residual backup expiry may therefore occur up to 150 days after the service ends.

Returning an export does not extend Amy’s retention of the copies we control. A restoration must reapply deletion and expiry instructions before the restored system returns to normal use.

Legal or incident holds are limited to the relevant records, access is restricted to the purpose of the hold and the continuing need is reviewed at least every 90 days.

10. International transfers

Our hosting, email, storage, authentication, backup or support arrangements may involve processing outside the UK, including remote support access.

Where Amy is responsible for a restricted transfer, we use an applicable UK adequacy regulation or an appropriate safeguard, such as the UK International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses, together with any assessment required by law.

Where Amy acts as processor, international transfers also follow the customer organisation’s documented instructions and the applicable processing agreement.

Contact theteam@amyonbera.com for information about current destinations and safeguards and, where applicable, a copy of the relevant safeguard subject to necessary redactions.

11. Cookies and browser storage

Our policy for the public Chamber pages and Chamber service is to use only cookies or similar browser storage that are necessary to deliver, secure or authenticate the service requested.

We do not use optional analytics, advertising, behavioural tracking or fingerprinting.

Our current cookie and storage information identifies the technology in use, any relevant provider, its purpose and its duration.

If we later introduce optional technology that requires consent under our chosen policy or applicable law, we will explain it before use, ask for prior opt-in and provide an equally easy way to withdraw.

Current browser storage

The public Chamber pages do not set application cookies or use localStorage or sessionStorage. Details entered in an enquiry form stay in page memory until the page is closed or reloaded, or the enquiry is successfully sent.

Signing in at chamber.amyonbera.com uses one essential authentication cookie:

Name
chamber_session
Provider
Amy On Bera Ltd
Purpose
Maintains your approved sign-in and allows the server to check access to your sites. It is not used for advertising or analytics.
Duration
Up to 8 hours; cleared when you sign out.
Access
HttpOnly, secure in production and SameSite=Strict. Sent to the Chamber service for authentication, not to advertising services.

First-time setup and password-reset codes and verification steps are held temporarily in page memory, not persistent browser storage. Closing or reloading the page clears that in-progress form state.

12. Security

We use access controls and other technical and organisational measures appropriate to the service and information involved.

For a live deployment, the customer and Amy agree the authorised users, network and connector configuration, support arrangements and operational fallback.

Connecting Chamber to conference equipment through an Amy Connector does not by itself prove that the equipment network is isolated from every other system. The supported network design and permitted access must be defined and tested for the site.

No online or connected service can promise absolute security.

13. Your rights

For Amy’s own controller processing, you may have rights to access, correct, delete or restrict your information, receive portable information where applicable, or object to processing based on legitimate interests.

To make a request about Amy-controlled information, email theteam@amyonbera.com.

For meeting or voting information controlled by a customer organisation, contact that organisation first. We will assist it as required under our agreement. If you contact Amy directly about client-controlled information, we will direct or pass the request to the appropriate organisation and support its response.

Rights are subject to legal conditions and exceptions.

You may complain to the UK Information Commissioner’s Office at ico.org.uk.

14. Changes to this notice

We show the version and effective date of the current notice and keep a record of previous versions. Previous versions can be provided on request.

If a material change introduces a new use of personal information, we will update the notice and communicate that change before the new processing begins. Where consent is required, we will ask for it.

A new version of this notice does not retrospectively authorise a different use of information.

Amy On Bera Ltd

Amy

Amy On Bera

We build software that makes complex work easier to use. From payments to meeting operations, we bring the information and actions people need into a clearer view.

Clear tools. Hidden value.

DashboardVotingVoting history
GitHubDiscordXPrivacyTerms

© 2026 Amy On Bera Ltd. All rights reserved.

Get Started