Privacy Policy

Who We Are

KerrOS is operated by KerrOS Sweden AB, a company registered in Sweden (Org. nr 559501-8960).

We are the data controller for the personal data we collect through the KerrOS service. That means we decide what data is collected and why, and we're accountable for protecting it.

For data processing questions: privacy+v20260514@kerros.com

What We Collect

Google User Data

When you connect a Google account to KerrOS, you authorize us to access specific data from your Google account through the Google APIs. We only request the scopes needed for the connector you enable, and we ask Google to enforce the same limits we describe here.

This disclosure is also surfaced in-product the moment you connect a Google account, so you can review it without leaving the consent flow.

What we access

Per Google connector, the data we read or write through the OAuth scopes you grant:

How we use it

The data above is used only to provide the user-facing KerrOS features you have explicitly enabled: synchronising your data into your own KerrOS volume so the KerrOS AI can reason over it, and providing cross-channel communication tools that let you read, reply to, schedule, and share across Gmail, Chat, Calendar, Meet, and Drive from a single surface.

Limited Use — what we will not do with your Google data

• We will not use, transfer, or sell your Google user data for serving, targeting, measuring, or personalising advertising (including retargeting and interest-based advertising).
• We will not transfer your Google user data to third parties except (a) as necessary to provide the user-facing features described above and prominently disclosed in this policy, (b) for security purposes such as investigating abuse, (c) to comply with applicable law, or (d) as part of a merger, acquisition, or sale of assets where the recipient is bound by an equivalent commitment and you receive prior notice.
• We will not allow any human at KerrOS to read your Google user data, except: when you have explicitly asked us to (for example, support troubleshooting on a specific message), when it is required for security purposes, when it is required by law, or when the data has been aggregated and anonymised for internal operations and no individual user can be re-identified.

See also the AI/ML Training and Google User Data section below for our position on training models with Google user data.

AI/ML Training and Google User Data

KerrOS does not use data received from Google APIs — Gmail content, Drive files, Calendar events, Chat or Meet content, Contacts data, or profile information — to develop, improve, or train any generalised or user-specific AI/ML model. This is consistent with the Google Workspace API user data and developer policy.

When you invoke an AI feature in KerrOS that requires sending data to a third-party AI provider (for example, asking the in-product AI to summarise an email), the relevant data is sent to that provider only to fulfil the specific request you made. Every provider that may receive Google user data is named in the Third Parties section below and is bound by a data processing agreement that prohibits training on customer data without explicit consent.

Why We Process Your Data

We always have a legal basis for processing. Here's how it maps:

You can withdraw consent at any time. This doesn't affect processing that happened before you withdrew.

Third Parties

We work with a limited set of trusted partners. Every partner is bound by a data processing agreement that meets GDPR requirements.

We will update this list before we add or change any provider that may receive Google user data, and we will notify you in-app at least 30 days before the change takes effect.

We never sell your data. We never share it for advertising. Full stop.

Encryption & Security

• At rest: All data encrypted with AES-256 on AWS infrastructure.
• In transit: All connections use TLS 1.2 or higher.
• Secrets: API keys and sensitive credentials are encrypted at the application layer before being stored in the database.
• Access control: Role-based access. Only the people who need access to support you have it.
• Monitoring: We monitor for unauthorized access, anomalies, and threats.
• Backups: Encrypted backups, regularly tested for integrity.

No system is 100% secure. We design ours to make breaches as unlikely and as limited as possible.

International Transfers

KerrOS is based in Sweden (EU). Some of our partners operate outside the EU.

When data leaves the EU/EEA, we protect it through:

• EU-US Data Privacy Framework where the recipient is certified.
• Standard Contractual Clauses (SCCs) approved by the European Commission, as a fallback for all other transfers.
• Supplementary measures (encryption in transit and at rest) in line with EDPB guidance.

You can request a copy of the relevant SCCs by emailing privacy+v20260514@kerros.com.

Your Rights

Under GDPR (and similar laws), you have the right to:

• Access: Get a copy of all personal data we hold about you.
• Rectification: Correct inaccurate data.
• Erasure: Request deletion of your data ("right to be forgotten").
• Restriction: Limit how we process your data.
• Portability: Receive your data in a structured, machine-readable format.
• Object: Object to processing based on legitimate interest.
• Withdraw consent: Revoke consent at any time for consent-based processing.
• Complain: Lodge a complaint with the Swedish Authority for Privacy Protection (IMY) or your local supervisory authority.

Data Retention

We keep data only as long as we need it:

After retention periods expire, data is permanently deleted or anonymized.

Google user data — retention and deletion

Because data synced from Google sits on your own KerrOS volume rather than in a shared KerrOS-controlled store, retention is mostly under your control. The table below describes what happens at each trigger:

This model reflects KerrOS's architecture: each user has their own LUKS-encrypted volume, and your data — including data synced from Google — lives on your volume rather than in a shared KerrOS-controlled store. KerrOS does not operate a general-purpose admin view that would let staff read user data.

Breach Notification

If we discover a personal data breach that poses a risk to your rights:

• We notify the supervisory authority (IMY) within 48 hours.
• We notify affected users within 72 hours via email.

The notification will include: what happened, what data was affected, what we're doing about it, and what you can do.

Children

KerrOS is not designed for users under the minimum digital-consent age applicable in their jurisdiction — 16 in the European Economic Area and the United Kingdom, 13 in the United States under the Children's Online Privacy Protection Act (COPPA), and the locally applicable equivalent elsewhere. We do not knowingly collect personal data from users below the applicable minimum age. If we learn that we have, we will delete it promptly.

Cookies

For details, see our Cookie Policy.

Changes to This Policy

We may update this policy when our practices change or when regulations require it. Material changes are communicated via email and/or in-app notification. We'll give at least 30 days notice before significant changes take effect.

Contact

• Privacy inquiries: privacy+v20260514@kerros.com
• Data protection officer: dpo@kerros.com
• Supervisory authority: Integritetsskyddsmyndigheten (IMY), imy.se