Privacy
Privacy policy
What personal data Rykon Mail collects, why, the legal basis, who else handles it, how long it is kept and the rights you have.
- Version
- 2.1
- Effective
- 30 October 2026
- Last updated
- 30 October 2026
1.Who we are and our two roles
1.1Rykon Mail is provided by Rykon Technologies Inc. ("we", "us"). We handle personal data in two different roles, and this policy explains both.
- As Controller
- For Account Data (the people who sign up for and use Rykon Mail, and billing contacts), and for visitors to our websites and people who contact us. This policy is our notice to you for that data.
- As Processor
- For Customer Data: the mail in our customers’ mailboxes, and the contacts, subscribers and recipients of our customers’ campaigns, automations and agents. Our customer decides how that data is used and is its Controller; we process it only on the customer’s instructions under our data processing addendum. If you received mail from a company that uses Rykon Mail, see your privacy rights.
2.What we collect as Controller
Data
Name, work email, organisation; that you accepted the acceptable use policy, its version, and your IP address at the time
- Where it comes from
- You, at sign-up
- Why we use it
- To create and run your account, and to show the terms you accepted
- Legal basis (GDPR)
- Contract; legitimate interests in preventing abuse
Data
Sign-in details: password (held only by our identity service), passkeys or authenticator apps you add, email confirmation
- Where it comes from
- You
- Why we use it
- To keep your account secure
- Legal basis (GDPR)
- Contract; legitimate interests in security
Data
If you choose Sign in with Google: your Google account ID, email address, whether Google has verified it, and your name (section 3)
- Where it comes from
- Google, when you ask it to sign you in
- Why we use it
- To create your account and sign you in
- Legal basis (GDPR)
- Contract
Data
What you and your team do in the console: who changed what, and when (the audit log)
- Where it comes from
- Your use of the service
- Why we use it
- Security, accountability and support
- Legal basis (GDPR)
- Legitimate interests; legal obligation where records are required
Data
Billing contact, plan and charges. Card details go to Stripe and never reach us
- Where it comes from
- You, through Stripe
- Why we use it
- To take payment and keep tax records
- Legal basis (GDPR)
- Contract; legal obligation
Data
Support requests: your message, your account, plan and domains
- Where it comes from
- You
- Why we use it
- To answer you
- Legal basis (GDPR)
- Contract; legitimate interests
Data
Enquiries from our website: email, name, company, number of mailboxes, domain and message
- Where it comes from
- You, through a form on rykonmail.com
- Why we use it
- To reply and discuss Rykon Mail with you
- Legal basis (GDPR)
- Legitimate interests; steps before a contract
Data
Domains you look up with our domain checker
- Where it comes from
- You
- Why we use it
- To show you the result
- Legal basis (GDPR)
- Legitimate interests
Data
Technical data such as IP address and browser, in server logs
- Where it comes from
- Your browser
- Why we use it
- To run, secure and debug the service
- Legal basis (GDPR)
- Legitimate interests in security
2.1Where we rely on legitimate interests, we have weighed them against your rights; you may object at any time (section 10).
3.Sign in with Google
3.1You can create a Rykon Mail account, or sign in to one, with your Google account instead of a password. It is your choice, and an account made with a password can always be used without Google.
3.2When you choose it, Google asks for your permission and then tells our identity service at id.rykonmail.com your Google account ID, your email address, whether Google has verified that address, and your name. We ask Google for nothing more: only the basic “email” and “profile” permissions. We cannot read your Gmail, contacts, files or calendar, and we never post or act on your Google account. Google never sends us your Google password.
3.3We keep your Google account ID with your Rykon Mail account so we recognise you the next time you sign in, and your name and email become your account’s name and email, which you can change. Google also gives our identity service a sign-in token that expires after about an hour; it is kept only with that link to your account and is not used for anything else. We use what Google shares only to sign you in and run your account, never for advertising, and we do not sell it or share it with anyone.
3.4An address Google has verified counts as confirmed, so an account made with Google needs no confirmation email. If you already have a Rykon Mail account with the same address, it is joined to your Google account only when you have confirmed that address with us; otherwise sign in with your password first and connect Google from your account settings.
3.5You can stop using Google at any time: set a password with “Forgot username or password?” on the sign-in page, and remove Rykon Mail from your Google Account under Security, third-party connections. The link is deleted with your account.
3.6Rykon Mail’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
4.What we process for our customers
4.1As Processor, and only to provide the service, we process:
- mail in customers’ mailboxes, stored on our servers so they and their mail apps can reach it;
- people who subscribe through a customer’s forms: their address, name if given, the consent text they agreed to, when, from which IP address and which form, and when they confirmed; and their unsubscribes, bounces and complaints, so they are not mailed again;
- for campaigns and automated email: who each message went to and what happened to it, including whether it was opened or a link was clicked. Opens are counted when images load, and clicks through a link that passes through Amazon SES. The unsubscribe link is never tracked;
- for AI agents: every message an agent reads or sends, held, approved or rejected, kept as a record for the customer;
- for transactional email: who each message went to and its delivery outcome. The body of a transactional message is not stored.
4.2When a customer moves mail in from another provider, the old mailbox’s password goes to our mail server for the duration of the move and is deleted when the move finishes or is stopped. It is never stored in our own records.
5.AI features
5.1Writing help, the campaign studio and drafted agent replies use AI models through a gateway we run ourselves. The models are provided by Anthropic, with OpenAI used only if Anthropic is unavailable. A request carries only what the feature needs: the brief, the draft or block being written, and the account name. Contact lists and audience data are never sent. A drafted agent reply carries the incoming message it answers (sender, subject and up to 8,000 characters of text), and is the one AI feature that sends a third party’s message.
5.2The instructions the model follows are set on our servers and cannot be changed by a request. We do not use Customer Data to train AI models, and AI features run only when a customer uses them.
7.International transfers
7.1Rykon Mail’s servers, databases and mail storage are in Germany. Some providers process data in the United States: Amazon SES sends outbound mail from the United States, and Stripe, Anthropic and OpenAI are in the United States. Where personal data from the European Economic Area, the United Kingdom or Switzerland is transferred to a country without an adequacy decision, the transfer relies on the European Commission’s Standard Contractual Clauses (with the UK International Data Transfer Addendum for UK data) in the provider’s data processing terms, or on the provider’s certification under the EU-US Data Privacy Framework where it holds one. You may ask us for a copy of the relevant safeguards.
8.How long we keep it
Data
Account Data
- Kept for
- While the account is open. Deleted from the live service when it closes, seven days after the owner asks
Data
Audit log and billing records
- Kept for
- Kept after an account closes, as records of what happened and for tax and legal purposes
Data
Mail
- Kept for
- Until the user deletes it, the mailbox is removed, or the account closes
Data
Contacts and their history
- Kept for
- Until the customer deletes them or the account closes. Erasing a person removes the contact and its history at once
Data
Unsubscribes and suppressions
- Kept for
- While the account exists, so an address is not mailed against its owner’s wishes. When a person is erased, only their address is kept on the suppression list, for the same reason
Data
AI studio output
- Kept for
- Generated text is cleared after 90 days. Usage counts (no content) are kept to apply daily allowances
Data
Sign-in session
- Kept for
- 12 hours; a sign-in attempt, 10 minutes
Data
Encrypted backups of our databases
- Kept for
- Rotated on a rolling schedule and kept for up to about three months, after which deleted data no longer exists in them
9.Security
9.1We protect personal data with technical and organisational measures appropriate to the risk, described on our security page: encryption in transit, sealed credentials, hashed API keys, a private network for the control plane, per-customer sending identities, an append-only audit log and encrypted offsite backups. No system is perfectly secure; we tell you of a breach as section 12 describes.
10.Your rights
10.1Depending on where you live, you have the right to access the personal data we hold about you; to correct it; to have it deleted; to restrict or object to its processing, including processing based on legitimate interests; to receive it in a portable format; and to withdraw consent where we rely on it. California residents have the rights to know, delete, correct and opt out of sale or sharing (we do neither), and not to be discriminated against for using them.
10.2To exercise a right, write to privacy@rykonmail.com with "Privacy request" in the subject, or use the export and closure tools in the console. We acknowledge a request within 10 days and answer within one month (45 days for California requests), which we may extend where the law allows and will tell you if we do. We may ask you to confirm your identity first. An authorised agent may act for you with your signed permission.
10.3If your data is in a customer’s mailbox or list, that customer is the Controller: contact them first. See your privacy rights for how, and what we do to help.
10.4You also have the right to complain to a data protection authority, in particular in the EU member state where you live or work, or to the UK Information Commissioner’s Office. We would welcome the chance to address your concern first.
11.Children
11.1Rykon Mail is a service for businesses and is not directed to children. We do not knowingly collect personal data from anyone under 16. If you believe a child has given us personal data, contact us and we will delete it.
12.Personal data breaches
12.1If a breach affects personal data we control, we notify the competent supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of it, and the people affected where the breach is likely to result in a high risk to them. For Customer Data, we notify the customer as the data processing addendum sets out.
14.Contact and changes
14.1Privacy questions and requests: privacy@rykonmail.com, subject "Privacy request". We will tell you by email, and on this page, before a material change to this policy takes effect.
Change log
Version 2.1
30 October 2026Sign in with Google: what Google shares with us when you choose it, what we keep and why, how accounts are joined, how to stop using it, and the Limited Use commitment.
Version 2.0
30 October 2026Controller and processor roles set out, legal bases per purpose, AI features, international transfers, a retention table, rights under the GDPR, UK GDPR and CCPA/CPRA, children, breach notification and cookies.
Version 1.0
29 October 2026First published.