Privacy Policy

1. Who we are and who is responsible

QuiC is a workplace communication service for messaging, calls, meetings and an AI assistant. It is run by AeonX Digital Technology Limited, a company registered in India (“AeonX”, “we”, “us”). This policy covers the QuiC apps for iPhone, iPad, Android and Mac, and the web app at quic.chat.

QuiC is provided by AeonX Digital Technology Limited. The QuiC apps are published on the App Store, Google Play and for macOS by its wholly owned subsidiary, AeonX Digital Solutions Pvt. Ltd.

Organisations buy QuiC and invite their people to it. For the content and account data of an organisation’s workspace, that organisation decides why and how the data is used: under India’s Digital Personal Data Protection Act 2023 it is the Data Fiduciary (under the EU GDPR, the controller), and AeonX processes the data on its behalf. For a small set of data we handle for our own purposes, such as running billing, securing the service and the consent records described below, AeonX is responsible directly. If your organisation has its own privacy notice, it applies too.

2. What we collect

Account and profile

Name, work email address, organisation, role, department and job title where your administrator sets them, and an optional photo, bio and phone number. If you sign your organisation up yourself, we also ask for a phone number; we do not currently verify it by SMS.

What you send

Messages, files, voice notes, polls, reactions, status updates and anything else you share in QuiC. How much of this our servers can read depends on encryption, explained in Encryption: what it covers and what it does not.

Communication records

Who is in which conversation, who sent what to whom and when, delivery and read receipts, and call and meeting records: who took part, when it started, how long it lasted and whether it was answered. We need these to deliver messages and show your history. They are not end-to-end encrypted.

Meetings, recordings and transcripts

If your organisation turns recording on and the host records a meeting, we store the recording and create a transcript from it. If your organisation also turns on AI notes, we create a summary and action items from the transcript. Participants are told when a meeting is being recorded.

Devices and connections

For each device you sign in on: a device identifier, the kind of device, its name and operating system, the app version, the IP address it last connected from and when it was last active. We also keep push notification tokens so we can reach the device, and, on phones, an identifier for this installation of the app.

Security and diagnostic records

Records of administrative and security-relevant actions (for example changes to settings, group invitations and recording events), connection logs for the real-time service (including IP address and browser or app details), and crash reports with technical details such as a stack trace, device model and operating system.

Service health counts

The apps report counts of technical events, such as how many messages failed to decrypt in an hour. These are totals per organisation, platform and app version only: they contain no message content and no user, device or conversation identifiers.

Location

Only when you choose to share a location in a conversation, including live location for the period you pick. QuiC does not track your location in the background.

What we do not collect

QuiC does not upload your phone’s address book. People are found through your organisation’s directory. We do not use advertising trackers or third-party analytics in the apps or on the website.

3. Why we use it

• To provide QuiC: deliver messages and files, connect calls and meetings, keep your devices in sync, send notifications and show your history.
• To keep accounts and the service secure: sign-in, device management, preventing abuse, investigating incidents and enforcing our Terms of Service.
• To fix and improve QuiC: crash reports and health counts tell us what is broken. We do not read message content for this.
• To bill your organisation: seat counts and the volume of AI usage, never the content of what was asked.
• To meet legal obligations and respond to valid legal requests.

Where the law asks us to name a legal basis: we rely on performing our contract with your organisation (and the Terms with you) to provide the service; on our and your organisation’s legitimate interest in keeping it secure and working; on legal obligation where one applies; and on your consent where we ask for it, such as for notifications on your device. Under the DPDP Act, your organisation’s use of QuiC for employment purposes may be a “legitimate use” that does not require your separate consent; where consent is required, we or your organisation will ask for it.

We do not sell personal data, use it for advertising, or use your content to train AI models.

4. Encryption: what it covers and what it does not

We would rather be exact here than impressive. Everything QuiC sends is encrypted in transit (TLS), and our databases and file storage are encrypted at rest. End-to-end encryption, where only the people in a conversation hold the keys, is a stronger promise, and it applies to some things and not others.

Messages and attachments

Chats and groups in QuiC are end-to-end encrypted by default, with the Signal Protocol. Messages, attachments and polls are encrypted on your device, and only the devices of the people in the conversation can decrypt them. Each device creates its own keys; the private keys never leave it. QuiC’s servers store and relay only the encrypted content and cannot read it. For attachments they keep only the encrypted file, its size and a generic label; the real file name, type and key travel inside the encryption. The one exception is a chat that includes someone whose organisation uses an organisation-controlled key: that organisation can read it too.

Our servers refuse to store an unencrypted message in an end-to-end encrypted chat. If your app is too old to encrypt a message, it is asked to update rather than send it in the clear.

Notifications are previewed on your device: for these chats, what Apple and Google carry contains no message text, and your device decrypts the message itself to show the preview. The sender’s name and the conversation’s name are included so the notification makes sense. In-app notification records on our servers say only “New message” or the kind of media.

Older messages. Before 4 October 2026, some apps also sent our servers a readable copy of a message alongside the encrypted one, and some older messages and in-app notification previews were stored only in readable form. Our servers no longer show those copies for any message that has an encrypted version, and they are kept encrypted at rest with keys AeonX manages until our clean-up removes them. Messages that only ever existed unencrypted, from before encryption was in place, stay readable to our servers until they are deleted.

Chats that are not end-to-end encrypted. Conversations with a business or a bot (for example an AeonX assistant or an app connected to your organisation’s systems) are not end-to-end encrypted, because that business or service must read the messages to answer them; QuiC labels business chats as not end-to-end encrypted. Chat inside a meeting set up for recording and AI notes is not end-to-end encrypted either.

Calls

On current QuiC apps, one-to-one and group voice and video calls are end-to-end encrypted. Each call gets its own key, created on a participant’s device and shared with the other participants’ devices inside Signal-encrypted messages. Audio and video are encrypted with that key on your device, so the media servers run by our provider LiveKit pass them on without being able to see or hear them. Joining an encrypted call needs a current app; older versions are asked to update.

A call started from an older version of the app, or from a browser that cannot do this encryption, is not end-to-end encrypted. It is still encrypted between each device and the media servers, but those servers decrypt it in order to route it.

Meetings

Each meeting is set up either as end-to-end encrypted or for recording and AI notes. Your organisation chooses which is the default and can require every meeting to be end-to-end encrypted; otherwise the host chooses.

• An end-to-end encrypted meeting works like a call above. It cannot be recorded, transcribed or summarised. Guests receive the meeting key in the part of the invite link after the “#”, which browsers do not send to our servers, so share the full link only with people you mean to invite.
• A meeting set up for recording and AI notes is encrypted in transit and at rest, but not end-to-end: the media servers can see and hear it, which is what recording requires. Text chat inside such a meeting is not end-to-end encrypted either.

What encryption never hides

• Communication records (who talked to whom, when and for how long), which we need to run the service.
• Anything you send to an AI feature: it is processed by our AI provider in readable form. See QuiC AI.
• Recordings, transcripts and AI meeting notes, which we store so that permitted participants can open them.
• Content on a device that someone else can unlock, or that a recipient shares on.

5. Organisations that keep a copy of their messages (organisation-controlled key)

Some organisations, such as banks, insurers and public bodies, must keep and be able to produce their employees’ messages for legal and regulatory reasons. On an Enterprise plan an organisation can turn on an organisation-controlled key. When it does, every new message and file in a chat that includes one of its members is also encrypted to a key that the organisation holds in its own key-management service. QuiC is given only the public half of that key.

Those messages are not end-to-end encrypted from that organisation’s point of view. The organisation can decrypt, keep, review and export them, outside QuiC, under its own policies. QuiC still cannot read them: we never hold or can use the organisation’s private key, and we store only encrypted copies.

• You are told first. Members of the organisation see a notice in the app at least 7 days before capture starts. Nothing sent before that date is captured.
• It covers everyone in the chat. If you are not in that organisation but chat with someone who is, your messages in that chat are captured too, so the record is complete. Every such chat shows a permanent banner saying which organisation can read it, instead of “end-to-end encrypted”.
• Exports are recorded. Only people the organisation names as compliance officers can export the encrypted copies, and every export is written to the organisation’s audit log. Whether you are told about an export of your messages is the organisation’s choice; by default you are not.
• Deleting. If you delete a message for everyone, its copy is deleted too, unless your organisation’s retention rules say otherwise in future; we will update this policy before that changes.
• Calls and meetings are not covered. This setting affects messages and files only.

6. QuiC AI

QuiC AI is powered by Claude models from Anthropic. It runs only when you use it:

• In a chat (catch-up summaries, suggested replies, translation): only when you ask. Our servers cannot read your chats, so your app decrypts the recent messages involved and sends them, with sender names, through our servers to Anthropic for that one request. We do not keep a copy of that text. This is the one way chat content leaves end-to-end encryption, and only at your request. Your organisation can turn in-chat AI off.
• The assistant: what you type, recent turns of that conversation and, to answer questions about your work, the titles and status of a few of your pending approvals and tasks. We store your assistant conversations so you can come back to them; they are kept until your account is deleted.
• Meeting notes: if your organisation enables AI notes for recorded meetings, the transcript and the participants’ display names are sent to Anthropic to write the summary.

Anthropic processes this content under its commercial terms for API customers, which do not allow it to use the content to train its models. AI output can be wrong; check it before relying on it.

7. What your organisation can see

Your organisation’s administrators manage the workspace. They can see member accounts and profile details, which devices are signed in (including the IP address and when each was last active), administrative and security records, connection logs and crash reports for their organisation. They can change settings such as recording, AI features and screenshot protection, suspend or remove members, and delete recordings.

Administrators cannot read end-to-end encrypted messages through QuiC, and they cannot play recordings of meetings they were not entitled to attend. If your organisation has turned on an organisation-controlled key, its compliance officers can export and decrypt new messages in chats that include its members. Your organisation may have other rights over work communications under its own policies and local law.

8. Service providers we use

We share data only with the providers that run parts of QuiC for us, only for that purpose, and under contracts that require them to protect it:

Some optional integrations your organisation can enable, such as voice calls placed by an AeonX assistant, use further providers; we will tell your organisation which before they are switched on. We keep this list current.

We also disclose data when the law requires it, to protect people from harm, or to defend our legal rights. We will push back on requests that are not valid. We cannot hand over content we do not hold the keys to.

9. Where your data is stored

QuiC’s servers and storage are in Google Cloud’s Singapore region. Some providers above process data elsewhere, including India and the United States. Where data leaves the country it was collected in, we rely on the safeguards the applicable law requires, such as contractual commitments from the provider. India’s DPDP Act allows transfers except to countries the Government restricts; we will follow any such restriction. For customers in the EU or UK, we rely on standard contractual clauses or another transfer mechanism the law recognises.

10. How long we keep it

Backups are kept for a limited period and then overwritten. Copies of messages also live on the devices of the people you sent them to; deleting your account does not reach those devices.

11. Your rights and choices

Depending on the law that applies to you, you can ask to:

• see the personal data we hold about you and get a copy of it;
• correct or complete it;
• have it deleted;
• object to or restrict some uses, or withdraw consent you gave;
• nominate someone to act for you if you die or become unable to (India).

Ways to do this today:

• Edit your profile in the app.
• Export a copy of the conversations you are in from the app’s backup settings.
• Delete your account from the app (Settings → Delete account), or see Delete your account. This permanently removes your account, your devices and the messages and files you sent.
• Ask your organisation’s administrator, who manages your workspace, or write to us at privacy@aeonx.digital. We reply within 30 days and involve your organisation where it is responsible for the data.

If you are not satisfied with our answer, you can complain to our Grievance Officer (below) and then, in India, to the Data Protection Board of India, or to the data protection authority where you live.

12. Your agreement and our records of it

When you choose “Agree and Continue”, we record which versions of the Terms of Service and this policy you accepted, when, and on which kind of device and app version. If we change either document in a way that matters, we will ask you again. Where we rely on your consent, you can withdraw it by writing to us; that does not affect what was done before, and some features may then be unavailable.

13. Cookies and local storage

The QuiC website and web app use your browser’s storage only to make QuiC work: keeping you signed in, remembering this browser as a device, your theme, your encryption keys for end-to-end encryption, and your acceptance of these terms. We do not use advertising or analytics cookies. Clearing your browser data signs you out and removes the encryption keys stored in that browser.

14. Security and incidents

Beyond encryption, access to production systems is limited to the people who need it, secrets are kept in managed key stores, and administrators can require sign-in limits such as a maximum session age. No system is perfectly secure.

If a personal data breach affects you, we will tell the organisations affected without undue delay and support them in informing you, and we will notify the Data Protection Board of India and other authorities within the time the law requires.

15. Age

QuiC is for people at work. You must be at least 18 to use it, and it is not designed for or offered to children. If we learn that a child’s data has reached us, we will delete it.

16. Changes to this policy

When this policy changes, the version and effective date at the top change too. If the change matters to how your data is used, the apps will ask you to review it and agree again before or soon after it takes effect.

17. Contact and Grievance Officer

• Privacy questions and requests: privacy@aeonx.digital
• Grievance Officer (India): Grievance Officer, AeonX Digital Technology Limited — privacy@aeonx.digital
• Support: support@aeonx.digital