AIOS Privacy Policy
Last updated 6 November 2026
1. Who we are
AIOS is a set of products made by Automation Architecture AI ("we", "us", "our"). This policy explains what information AIOS collects, how we use it, who we share it with, and the choices you have.
Automation Architecture AI, 4122 W Sevilla St, Tampa, Florida 33629, United States. Contact: privacy@automationarchitecture.ai.
This policy covers these products:
- AIOS Coffee. A daily briefing and meeting prep tool. It reads your email, calendar, and meeting transcripts, then summarizes what matters today, prepares you for meetings, and suggests draft replies for you to review.
- AIOS IQ. Your personal knowledge base. AI drafts it from your emails, documents, and meetings. You then confirm or correct each entry. Coffee and Signals read from IQ so their output reflects what you have confirmed.
- AIOS Signals. Relationship intelligence built from contacts you import. It gives you three ranked next actions, such as who to follow up with.
- AIOS CDP. The data connector layer that links your data sources (such as Google and Fireflies) to the products above. It is not sold separately.
2. The short version
- We only access the data you choose to connect, and only to run the features you use.
- We do not sell your data. We do not use it for advertising.
- We never use your Google data to train general AI models.
- People at AIOS do not read your email, calendar, or files, except in the narrow cases described below.
- Your data is encrypted in transit and at rest. So are your connection tokens.
- You can disconnect Google, or any other connected source, at any time. When your AIOS access ends, we delete your data within 30 days.
3. Google user data
This section explains exactly how AIOS handles data from your Google Account. It applies to data we receive from Google APIs and to anything we derive from that data, such as summaries, IQ entries, and draft replies.
Limited Use. AIOS'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.
AIOS's use of information received from Google Workspace APIs will adhere to the Google Workspace API User Data and Developer Policy, including the Limited Use requirements.
3.1 What Google data we access
AIOS only asks for Google access when you choose to connect a Google service. You see Google's consent screen and decide what to allow.
| Google service | Permission (scope) | What AIOS can see | Can AIOS change it? |
|---|---|---|---|
| Gmail | Read-only. https://www.googleapis.com/auth/gmail.readonly | Your email messages and their content, including subject, body, and attachments. Also message metadata: sender, recipients, date, labels, and thread. | No. AIOS cannot send, delete, or change your email. |
| Google Calendar | Events, read-only. https://www.googleapis.com/auth/calendar.events.readonly | Your calendar events: title, time, location, attendees, description, and attached meeting links. | No. AIOS cannot create, edit, or delete events. |
| Google Drive | Read-only. https://www.googleapis.com/auth/drive.readonly | The files in the Drive folders you choose, and their content, so AIOS can use them in IQ. Nothing is read until you choose folders. | No. AIOS cannot create, edit, or delete your files. |
| Google Account basics | openid, email, profile | Your name, email address, and profile picture, so we can sign you in. Sign-in is a separate Google connection from data access. | No. |
3.2 How we use Google data
We use Google data only to provide and improve the features you can see in AIOS. We do not use it for any other purpose.
| Google data | Feature | How it is used |
|---|---|---|
| Gmail messages and metadata | Coffee daily briefing | Find important and unanswered emails and summarize them in your briefing. |
| Gmail messages and metadata | Coffee draft replies | Suggest a reply for you to review, edit, and send yourself. AIOS does not send email for you. |
| Calendar events | Coffee meeting prep | Show today's meetings and prepare notes on attendees, past emails, and open items. |
| Gmail, Calendar, and Drive files | IQ knowledge base | Draft entries about your projects, people, and preferences. You confirm or correct each one. |
| Gmail and Calendar metadata (who, when) | Signals | Show when you last talked with a contact, so Signals can rank your three next actions. |
| Name and email | Sign-in and account | Create your account and identify you. |
"Improve" means making these same features work better for you, such as fixing bugs or making your briefing more accurate. It never means building products for anyone else from your data.
3.3 What we never do with Google data
- We do not sell it.
- We do not use it, or share it, to serve ads. This includes retargeting and personalized or interest-based ads.
- We do not transfer it to advertising platforms, data brokers, or information resellers.
- We do not use it to decide credit-worthiness or for lending.
- We do not use it to create, train, or improve general AI or machine learning models.
- We do not request access to Google data we do not need for a current feature.
3.4 AI and your Google data
- AIOS uses large language models from Anthropic (Claude) and OpenAI. OpenAI extracts information from your email and meeting text and creates embeddings (numeric representations of text) so AIOS can search your data. Anthropic powers the AIOS assistant, meeting prep, and opportunity insight.
- Your Google Workspace data is never used to create, train, or improve generalized or non-personalized AI or ML models. This applies to us and to our providers.
- Your data may only power your own personalized features, such as your own IQ knowledge base and your own briefings. It is never used to build features for other users.
- The terms we use with Anthropic and OpenAI bar them from training their models on your data. They may only process it to return results to AIOS. Anthropic deletes API inputs and outputs within 30 days. OpenAI keeps API abuse-monitoring logs for up to 30 days.
- AI output can be wrong. That is why IQ asks you to confirm or correct what it drafts, and why Coffee never sends a reply for you.
3.5 Who can see your Google data
Your Google data is processed by automated systems. People at AIOS do not read it, except in these cases:
- You ask us to. You give clear consent for us to look at specific items, such as one email or one event, so we can help with a support request. We record that consent.
- Security. It is needed to investigate a bug, abuse, or a security incident.
- Law. It is needed to comply with applicable law.
- Aggregated and anonymized data. The data is aggregated and anonymized so it cannot identify you, and is used only for internal operations, as the law allows.
Our team members, contractors, and successors must follow these same rules.
3.6 When Google data is shared
We only transfer Google data in these cases:
- To provide the features you use. This includes our service providers ("subprocessors") that host, process, or deliver AIOS. They are listed in section 3.7. They may only use the data to provide services to us.
- For security. For example, to investigate abuse.
- To comply with the law. For example, a valid court order.
- In a merger, acquisition, or sale of assets. Only after we get your explicit prior consent.
We do not share Google data for any other reason.
3.7 Subprocessors that may handle Google data
| Provider | Purpose |
|---|---|
| OpenAI | AI processing to extract information from your email and meeting text, and to create search embeddings. No training on your data. |
| Anthropic (Claude) | AI processing for the AIOS assistant, meeting prep, and opportunity insight. No training on your data. |
| Railway (hosting and self-hosted Postgres) | Application hosting, background jobs, and the database that stores your synced data and its embeddings. |
Stripe, Sentry, Resend, and Cloudflare do not receive the content of your Gmail, Calendar, or Drive data. Sentry is set up not to send personal data. Sign in with Google is handled directly between Google and AIOS.
3.8 How we store and protect Google data
- All data is encrypted in transit using HTTPS (TLS).
- All data is encrypted at rest on our systems and our providers' systems.
- Google OAuth access tokens and refresh tokens are encrypted at rest and are never shown in the app or in logs.
- Encryption keys are kept in a managed key management system.
- Access to production systems is limited to authorized staff who need it, and uses strong authentication.
- We use protections against prompt injection, so content in an email or file cannot trick AIOS into acting against you.
- We complete the security assessments Google requires for apps that use restricted scopes.
3.9 Keeping and deleting Google data
- We keep Google data only as long as needed to provide your features.
- If you disconnect a Google service under Settings → Integration, we erase the data from that source right away.
- When your AIOS access ends, we delete your data, including your Google data and anything derived from it, within 30 days. This includes summaries, IQ entries, search embeddings, and draft replies built from that data. We keep only your email address and the account name you gave us (see section 9).
- To have your data deleted sooner, email privacy@automationarchitecture.ai. We'll end your access and delete your data within 30 days of your request.
- Backups are overwritten within the same window. We may keep data longer only if the law requires it.
- You can remove AIOS's access at any time from your Google Account permissions page: https://myaccount.google.com/permissions. Once you revoke access, AIOS can no longer read new Google data.
4. Other information we collect
4.1 Information you give us
- Account details. Name, email address, and sign-in details. If you sign in with Google, we receive your name, email address, and profile picture directly from Google.
- Billing details. Payments are processed by Stripe. We receive your plan, billing status, and the last four digits and expiry of your card. We do not store full card numbers.
- Content you create. IQ confirmations and corrections, notes, settings, and feedback.
- Contacts you import. For Signals, contact details you upload or connect, such as names, emails, companies, and roles.
- Messages to us. Support requests and emails you send us.
4.2 Information from other services you connect
- Fireflies. If you connect Fireflies using your own Fireflies API key, we read meeting transcripts, summaries, titles, dates, and participants through the Fireflies API. We store your key encrypted. We use this data for Coffee meeting prep and IQ.
- Your use of Fireflies is under your own Fireflies account and covered by its privacy policy. AIOS does not have its own contract with Fireflies. You can disconnect Fireflies in AIOS at any time.
4.3 Information collected automatically
- Usage analytics. We use PostHog to see which features are used, such as pages viewed and buttons clicked. PostHog also receives your account ID, name and email address so usage is tied to your account. It also records your sessions in AIOS (session replay) so we can see how the app is used and fix problems. Replay masks all text and form inputs, so recordings show the layout of the screen but not what you type or the content shown on it. Recordings are kept for 30 days.
- Error reports. We use Sentry to find and fix bugs. Error reports include technical details like browser type and the steps that led to the error.
- Device and log data. IP address, browser, device type, and timestamps, used for security and to keep the service running.
5. How we use information
We use the information in section 4 to:
- Provide Coffee, IQ, Signals, and the CDP connector layer.
- Create and manage your account and process payments.
- Send sign-up verification emails. We use Resend to send them. These emails do not include Google data.
- Understand how AIOS is used so we can improve it.
- Find and fix bugs, prevent fraud and abuse, and keep AIOS secure.
- Comply with the law and enforce our terms.
Google user data is only used as described in section 3, even where this section is broader.
8. Third-party services
AIOS connects to services you choose, such as Google and Fireflies. We only access the data you allow, through each service's official API. Each service has its own privacy policy. We are not responsible for how those services handle your data. You can disconnect any of them in AIOS, and in most cases from the service itself.
9. How long we keep information
- Your data is shared across all the AIOS products you use. We keep it while any of them is active.
- To delete your data, end your AIOS access by cancelling your plan or letting your trial end. We delete all your data within 30 days of your access ending, except your email address and the account name you gave us, which we keep so you can return or contact us.
- To have your data deleted sooner, or to have your email address and account name deleted too, email privacy@automationarchitecture.ai. We'll end your access and delete your data within 30 days of your request.
- To remove one connected source right away, disconnect it under Settings → Integration.
- To get a copy of your data, use Export under Settings → Data & Privacy.
- We may keep data longer only where the law requires it.
- We keep billing records as long as tax and accounting laws require.
- Usage analytics are kept for up to 3 years, session recordings for 30 days, and error reports for up to 90 days. After that they are deleted automatically. Since 6 November 2026, PostHog uses your IP address only to work out your rough location and then discards it, so new usage analytics hold no IP address. Analytics recorded before that date may still hold one until they are deleted.
10. Security
We protect your data with encryption in transit and at rest, encrypted storage of connection tokens, limited staff access, strong authentication, and regular security reviews. No system is perfectly secure. If we learn of a breach that affects your data, we will notify you and the authorities as the law requires.
11. International transfers
We and our providers may process your data in the United States and other countries. Those countries may have different data protection laws from yours. When we transfer data from the European Economic Area, the United Kingdom, or Switzerland, we use safeguards such as Standard Contractual Clauses.
12. Your rights and choices
Depending on where you live, you may have the right to:
- Access the personal information we hold about you.
- Correct information that is wrong.
- Delete your information.
- Get a copy of your information in a portable format.
- Object to or limit some processing.
- Withdraw consent at any time, such as by disconnecting Google.
- Not be treated differently for using these rights.
Many of these you can do yourself in the app. For anything else, email privacy@automationarchitecture.ai. We will respond within the time the law requires. We may need to verify your identity first. If you are in the EEA or UK, you can also complain to your local data protection authority.
For EEA and UK users, we rely on these legal bases: to perform our contract with you, your consent (for example, when you connect Google), our legitimate interests (such as security and improving AIOS), and legal obligations.
13. Children
AIOS is a business tool. It is not meant for anyone under 18. We do not knowingly collect data from children. If you believe a child has given us data, contact us and we will delete it.
14. Changes to this policy
We may update this policy. We will post the new version on this page and change the "Last updated" date. If a change is significant, we will tell you by email or in the app before it takes effect. We will ask for your consent again before using Google data in a new way.
15. Contact us
Automation Architecture AI
4122 W Sevilla St, Tampa, Florida 33629, United States