Privacy policy
Awre ("Awre", "we", "us") provides a personal AI assistant that, with your explicit permission, connects to third-party services you use (such as Google Gmail and Calendar, and Slack) to help you stay on top of your work. This policy explains what we access, why, how we handle it, and the controls you have.
Who we are
Awre is operated by Awre AI, Inc. For privacy questions, contact privacy@awre.ai.
What data we access and why
We only access data for services you explicitly connect, and only the minimum needed to provide the assistant's features.
- Google Calendar (read-only) — the list of calendars you subscribe to and event data, including titles, descriptions, times, attendees, conferencing details, and status, to provide meeting awareness, preparation, schedule-conflict detection, and free-time suggestions. Awre does not create, update, or delete calendars or events.
- Gmail (read-only) — message headers, labels, participants, attachments, and message bodies, to search and summarize mail, track communication, surface follow-ups, and answer your questions about the inbox. Awre does not draft, send, label, archive, trash, or delete Gmail messages.
- Google account identity — your primary email address and basic public profile, used only to identify the Google account you connected.
- Slack — messages and channels you authorize, to provide team-communication context and thread tracking.
You connect each service individually. The assistant has zero access until you opt in, and you can disconnect any service at any time.
How your data is handled
- Credentials are never exposed to the AI. OAuth tokens are held by our integration provider (Composio, a SOC 2 Type II sub-processor) in an encrypted vault. The AI agent never sees your tokens; it requests data through a scoped proxy.
- Per-user isolation. Each user's data is processed in an isolated environment. Your data never enters another user's context.
- Data minimization. We request the minimum fields and scopes needed for each feature.
- Retention and deletion. OAuth credentials are retained until you disconnect the service or delete your account. Integration content such as emails and calendar events is normally processed transiently and is not retained beyond what the task or session requires. Knowledge you explicitly ask the assistant to remember is stored in your private space and is deletable by you. Disconnecting a service revokes its credentials; account deletion removes connected credentials, stored knowledge, and associated data, subject to legal retention requirements.
- No advertising. No selling. We do not sell your data and do not use it for advertising.
Google Limited Use disclosure
Awre's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:
- We only use Google user data to provide and improve the user-facing features of the Awre assistant that you have requested.
- We do not transfer or sell Google user data for serving advertisements.
- We do not use raw, derived, aggregated, or anonymized Google user data for any purpose unrelated to the features you use, including advertising, data brokerage, lending or creditworthiness decisions, generalized analytics, or model training.
- We do not allow humans to read your Google user data unless: (a) we have your affirmative agreement for specific messages, (b) it is necessary for security purposes such as investigating abuse, (c) to comply with applicable law, or (d) the data is aggregated and anonymized and used for internal operations.
- We do not use Google user data to train or improve generalized or non-personalized AI or ML models. Where the assistant uses AI models to process your data to answer your requests, that data is not used by us or our model providers to train their models.
Data transfer and sub-processors
We transfer Google user data only to service providers acting as our processors where necessary to provide the features you request. They may process only the data needed for their service under contractual confidentiality, security, and no-sale restrictions. We do not sell Google user data or share it with advertisers, data brokers, or lenders. Our processor categories are:
- Composio — integration and OAuth credential vault and API proxy (SOC 2 Type II).
- Anthropic — AI model inference, under a no-training data processing agreement.
- Fly.io — compute and per-user isolated environments.
Your controls
- Connect and disconnect any service at any time from Settings. Revocation is immediate.
- Activity view. See what your assistant accessed (metadata, e.g. "read 3 calendar events").
- Delete your account and data. On account deletion we delete your connected credentials, stored knowledge, and associated data, subject to legal retention limits.
- Access and correction rights as provided by applicable law (GDPR and CCPA).
Website analytics and diagnostics
With your permission, we use Google Analytics 4 and PostHog to understand how visitors find and use this website and whether forms are completed successfully. Optional analytics do not load until you select “Allow analytics”. You can change your choice at any time through “Cookie settings” in the footer.
- Google Analytics is configured without Google Signals, ad personalisation, or advertising storage. We do not send names, email addresses, or form answers to Google Analytics. See how Google uses information from sites that use its services.
- PostHog provides aggregate product analytics and, when enabled, session replay. Form inputs are masked, Do Not Track is respected, and conversion identifiers are pseudonymised before being sent from our server.
- Sentry and Vercel may process limited technical diagnostics, such as errors, device and browser information, and performance measurements, to keep the website secure and reliable. These diagnostics are not used for advertising.
Data location and transfers
Data may be processed in the United States. Where required, we rely on appropriate transfer mechanisms for cross-border processing.
Changes
We will update this policy as the product evolves and post the revised version here with a new "last updated" date.