Privacy Policy

1. Scope and status

This policy explains how ANNA Intelligence (“ANNA”, “we”) handles personal data on this website and in the ANNA application. ANNA is currently in a private preview: access is limited to authorized team accounts, and public sign-up, paid plans and downloads are not yet open.

This document is a working draft and is subject to legal review. Where a fact about the company is not yet settled, it is marked as pending rather than guessed.

2. Who is responsible

• Legal entity name: [To be confirmed: registered company name]
• Registered address: [To be confirmed: postal address]
• Privacy contact: [To be confirmed: contact email address]
• Data protection officer or EU/UK representative, if required: [To be confirmed: to be determined with counsel]

3. What we collect

Account data

Your name, email address and organization name. If you sign in with a password, we store only a salted hash of it (bcrypt), never the password itself. If you sign in through an identity provider such as Google, we receive the basic profile that provider shares (such as name, email address and profile image).

Content you give ANNA

Messages and questions you send, the text of voice conversations, notes, tasks, commitments, expenses, habits, calendar items, memory entries, preferences and the details you enter during onboarding. ANNA stores this so the product can work for you.

Data from services you connect

If you choose to connect a service such as Gmail, Google Calendar or Slack, ANNA accesses the data that service shares under the permission you grant, and keeps the connection credentials. You can remove a connection at any time.

Voice

Speech is converted to text for the conversation. ANNA does not store audio recordings.

Technical and usage data

Session information needed to keep you signed in, counters used to apply plan limits, and an audit trail of approvals, refusals and actions ANNA takes on your behalf. Server logs: [To be confirmed: log contents and retention period].

This website

The public pages contain no analytics or advertising tools in the current build. The only thing they remember is your light or dark theme choice, in your own browser.

4. How we use data

• To provide ANNA: answering questions, preparing drafts and proposals, running habit routines and reminders, and using your connected services when you ask.
• To keep the service secure, apply plan limits and keep an audit trail of actions that need your approval.
• To maintain and improve reliability.

5. Service providers

ANNA relies on third parties to operate. They process the data needed for their function under their own terms and privacy policies.

Semantic search over your content runs on our own server and does not send that content to a separate search provider. Whether each provider retains data or uses it for training depends on the account settings we configure with them: [To be confirmed: confirm each provider’s retention and training settings].

Cloud Browser, where enabled, reads public web pages from an isolated browser running on our servers. It is read-only and limited per run.

6. How we protect data

• Credentials for connected services are stored encrypted (AES-256-GCM).
• Passwords are stored only as hashes.
• Sign-in sessions use signed, encrypted tokens; browser requests that change data and come from another site are rejected.
• Emails and other changes are prepared for your review first; ANNA acts after you confirm.
• Access to ANNA is currently restricted to authorized team accounts, enforced on the server.
• Plan limits and permissions are enforced on the server, not only in the interface.

No system is perfectly secure, and we do not claim any third-party security certification at this time.

7. Cookies and local storage

We use only what the service needs to work. We do not use advertising cookies.

Whether a cookie notice is required for these uses in each region: [To be confirmed: confirm with counsel].

8. Retention and deletion

• You can delete a conversation, including its spoken text, and individual memory entries, expenses and events.
• Short-lived technical records, such as the results of chat turns, are removed automatically within about a day.
• Voice rooms are deleted when a session ends. Voice tokens are not stored and expire in minutes.
• The operator can set a retention period for spoken text: [To be confirmed: default retention period].
• There is not yet a self-service “delete my account and data” screen. Until there is, send a request to the privacy contact above and we will handle it manually: [To be confirmed: response time commitment].

9. Your choices and rights

Depending on where you live, you may have the right to access, correct, delete, export or object to the processing of your personal data, and to withdraw consent. To exercise a right, contact us at the privacy contact above. Some of these can already be done in the product (for example, deleting a conversation or disconnecting a service); others are handled on request.

Applicable laws and the rights we commit to for each region: [To be confirmed: confirm with counsel].

10. International transfers

Our providers may process data in different countries. Transfer mechanisms and data locations: [To be confirmed: confirm with counsel and providers].

11. Children

ANNA is not intended for children. Minimum age: [To be confirmed: minimum age to be set with counsel].

12. Changes and contact

We will update this policy as the product changes and revise the date above. Questions: [To be confirmed: privacy contact email].