Effective . Raion One is the suite containing Mail and Calendar, with a shared Raion account. This policy covers those services, booking guests and contact or invitation requests. It does not describe Mark42 or LEO.
- Who this covers
- Your Raion account
- Raion Mail
- Raion Calendar
- Booking guests
- Mail and Calendar together
- Google user data
- Where it is stored
- Who else processes it
- How long we keep it
- Export and deletion
- Security
- Cookies
- Children
- Changes
- Contact
Who this covers
RaionAI makes Raion One. Your Raion account signs you into Raion Mail and Raion Calendar. Sign-up is invite only. The apps are for the person who was invited, on the mail and calendar accounts they are allowed to use.
For questions about this policy or your data, write to hello@raionai.com.
If you email us or request an invitation, we receive your email address and the information you choose to include. We use it to respond and manage the request, not to subscribe you to marketing. You can ask us to delete that correspondence by emailing the same address. Our website and email hosting provider, Namecheap, processes the website requests and correspondence needed to provide those services.
Your Raion account
Your Raion account (account.raionai.com) is the sign-in for the Raion apps. You sign in with a passkey. There is no password. The private key stays on your device. We store the public key and the details needed to recognise that passkey: a credential id, a signature counter, transports, whether the passkey is backed up, when it was last used, and a name you can edit.
We also store:
- The name you give your account.
- Sign-in sessions for the account site, and a record of which apps you have signed in to.
- A security log of sign-ups, sign-ins, passkeys added or removed, signing out everywhere, and deletion.
- Short-lived sign-in state. Invite codes and enrollment links are stored only as hashes.
We keep this so you can sign in, add or remove a passkey, sign out everywhere, and delete the account. The sign-in service, internally called Raion Key, never receives your mail or events. Passkey ceremonies happen only on the account site. Hosting and backup providers are described below.
Raion Mail
Raion Mail (mail.raionai.com) is not a mail server. It uses your Raion account and syncs mailboxes you connect (IMAP, including Gmail with an app password). Your mail stays with that provider. Raion keeps a copy so it can show one inbox, search, sort, and send through the provider when you send.
For each mailbox we store:
- The address, and a sealed password, app password or token for that mailbox.
- A copy of messages: sender, recipients, subject, date, and the body. The server can read this copy. Sync and push need that. Mail in Raion is not end-to-end encrypted.
- How you organise it: threads, tags, rules, views, drafts, and mail waiting to send.
- Contacts derived from mail you send and receive, and a security log you can see.
- Notes pulled from messages, such as a flight, a delivery, a subscription or an appointment.
Cloud AI is off unless you turn it on for that mailbox. While it is off, message text is not sent to a model. On an iPhone, sorting can still run on the device. When you turn cloud AI on, Raion may send message text (not attachments) to OpenAI to sort mail, summarise a thread, draft a reply, extract those notes, or answer a question you ask. OpenAI may retain inputs and outputs in abuse-monitoring logs for up to 30 days by default, with longer retention possible for legal or safety reasons. We asked for zero retention and were declined. We send Responses calls with storage off; that does not turn off abuse monitoring. API data is not used for training, and we do not use your mail for advertising.
Cloud AI is enabled only for the owner’s accounts in Mail and Calendar. Cloud AI is off for other accounts during invited testing. Each app’s permission is separate; signing into Raion One does not enable it.
The privately tested Mail iPhone app keeps sign-in tokens and a local mail cache on your device. We store its APNs device token and a wrapped notification key to deliver alerts. On supported iPhones, some sorting and writing help can run on the device.
Remote images in a message load through Raion, so the sender sees our server rather than your address. You can turn remote images off. Notification text for the iPhone app is encrypted so Apple does not see the message. A web push service sees ciphertext, not the body.
Logs do not contain message bodies, subjects or credentials. Email addresses in logs are hashed.
Raion Calendar
Raion Calendar (calendar.raionai.com) is one calendar for each Raion account. You can connect Google calendars and keep calendars that live only in Raion. For a Google calendar, Google stays the source of truth. Raion keeps a synced copy, and the changes you make, so the app can show them and work offline. The web app keeps a local copy in that browser and deletes it when you sign out.
We store:
- Calendars and events: title, time, place, description, attendees, your response, and the provider’s own copy of the event where we need it to edit without losing fields.
- Your preferences, such as time zone, working hours and which calendar is the default.
- Tasks, flexible blocks, planner notes, mirror rules, booking pages and booking records.
- Reminder subscriptions, device tokens and the keys needed to deliver notifications.
- A sealed token for the Google connection. Provider secrets are sealed per connection.
Raion writes to Google when you create, change or delete an event, answer an invitation, or let a guest book, cancel or reschedule through a page you enabled. With busy mirroring on, it also creates, updates and removes its tracked Busy copies on the target calendar, including Google. A copy has the rule’s title (Busy by default), time and a tracking marker, private visibility, and no description, guests, location or reminders.
Planning uses a solver, without a model, to place flexible blocks linked to tasks or habits on native Raion calendars. It can move tentative blocks when busy time changes and leaves a note; pinned, defended or started blocks stay put. Defended blocks can reach Google as Busy copies through a mirror you enabled. The planner does not move your meetings or answer invitations for you.
Web quick add runs without cloud AI and shows an event draft for you to check before saving. Plan in plain words first parses locally. Only when words remain unexplained and Calendar cloud AI is on does it send your typed sentence, the local date, stored time zone and week start to OpenAI to fill a flexible-block draft. It sends no calendars, events or identifiers. You review and save the draft yourself. The meeting brief can also use cloud AI, as described below. Calendar data is not used for training or advertising.
Calendar reminders use Web Push and, in the privately tested iPhone app, Apple’s APNs. We store browser push endpoints and keys, and APNs device tokens and wrapped notification keys. Web Push encrypts the payload. APNs carries encrypted reminder text alongside fixed placeholder words and event identifiers; Apple does not receive the event title or location in readable form. Reminders depend on notification permission and service setup; native iPhone reminders are still being tested.
The Calendar iPhone app stores sign-in tokens in the device’s Keychain and keeps a local calendar copy, removed on sign-out. Widgets read that shared local copy. Quick add runs on the phone, using Apple’s Foundation Models when available or a local parser otherwise; those words do not leave the phone for parsing. Saved events then sync normally.
Personal access tokens let a tool read calendars or change events within the scopes you choose. ICS feed links let anyone holding the URL read events from that calendar without signing in. Treat both as secrets. Create and revoke them in Calendar’s web Settings. We store hashes of the secrets, their scope or calendar, and use and revocation details. Revoking a feed stops new reads after any cached response expires; it cannot erase copies someone already downloaded.
Logs do not contain event titles, descriptions, attendees or locations. Descriptions are shown as plain text. Raion does not load remote images from them.
Booking guests
You do not need a Raion account to book at book.raionai.com. We collect your name, email, chosen time and duration, any note you provide, and your time zone if supplied. We use these to reserve the slot, show the host your booking and let you manage it. Rate limits and a short-lived proof-of-work challenge protect the form without a third-party captcha. For rate limits we temporarily keep your IP address or network prefix and a keyed hash of your email in server memory.
Your name, email and time appear on the host’s calendar, including Google if that is the page’s target. Your optional note stays in Raion’s booking record. The confirmation is a calendar invitation sent by Google or, for a native calendar with invitation sending enabled, through the host’s own mail account. It carries a secret manage link for cancelling or rescheduling a future booking. Anyone with that link can manage the booking; keep it private. Invitation delivery remains limited during invited testing.
Booking records have no automatic expiry. They stay while the host’s Raion account is open, including after cancellation or deletion of the booking page, and are deleted with that account. Provider calendar and email copies follow those providers’ retention; our encrypted backup copies expire on the schedule below. For a data request, email hello@raionai.com.
Mail and Calendar together
When the services are connected, Mail sends Calendar the invitation found in a message and the response you choose. Add to calendar sends an extracted flight or appointment’s title, times, time zone, location and source-thread link as a draft for you to confirm; unsaved drafts expire after 24 hours. Calendar sends Mail your next event’s details for Mail’s schedule strip, asks for mail accounts and identities when linking a calendar, and gets contact names and addresses for guest suggestions. Calendar can ask Mail to send invitations, updates and replies through your own linked mail account. Invitation sending is limited during invited testing.
Opening meeting details near its start can request a meeting brief. Calendar sends Mail the guests’ email addresses to find recent threads. With Calendar cloud AI on, it also sends up to the first 200 characters of the event title; otherwise it sends no title. Mail returns thread subjects and links even without cloud AI. For matching mail accounts with cloud AI on, it may send that title, thread subjects and short message previews to OpenAI for a summary. Guest addresses are used for lookup, not sent as a separate model field. The brief is not stored by either service. None of this mail or event content goes to the sign-in service, Raion Key.
Google user data
When you connect a Google account, Raion Calendar asks for these OAuth scopes and no others:
calendar.calendarlist.readonly(https://www.googleapis.com/auth/calendar.calendarlist.readonly). Read the list of calendars on the Google account you connect.calendar.events(https://www.googleapis.com/auth/calendar.events). Read events on those calendars and write changes you request, bookings, and Busy copies under mirrors you enable.userinfo.email(https://www.googleapis.com/auth/userinfo.email). Identify the Google account you connect and check that a reconnect uses the same account.
Raion uses that data to show and sync your calendars and perform the edits, invitation responses, bookings and busy mirroring described above. Google user data is not used for advertising, not sold, not used to decide credit, and not used to train models. We do not let a person read it except with your consent, for security (for example investigating abuse), or when the law requires it.
A meeting title from Google is Google user data. If you have turned on Calendar cloud AI, Calendar can pass its first 200 characters to Mail for the user-facing meeting brief. Mail may send it to OpenAI with subjects and previews only from matching mail accounts whose cloud AI is also on. This transfer serves that feature, follows the Limited Use requirements, and is not for training, advertising or another purpose. Responses storage is off, but OpenAI’s abuse-monitoring retention described above still applies; this is not zero retention. Plain-words planning sends no calendar records to OpenAI, though the sentence you type may itself contain personal details. Deleting your Raion account attempts to revoke Google tokens and deletes Raion’s copy.
RaionAI's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Where it is stored
The apps run on servers we operate at Oracle Cloud. Keys that seal provider secrets are held in Oracle Cloud Vault. The servers can read mail and events in order to provide the apps. That store is not end-to-end encrypted.
The database backup system encrypts dumps before uploading them to Cloudflare R2. After a successful upload it keeps the newest 14 daily copies and 8 weekly copies. A deleted account can remain inside a backup until that copy expires. The backup is the database only, and the file is ciphertext.
Who else processes it
- OpenAI, for Mail and Calendar only where cloud AI is enabled, with the inputs and retention described above. Not for advertising or model training. It remains owner-only during invited testing.
- Google, when you connect Google Calendar. The calendar already lives there. Raion uses the API scopes above.
- Your mail provider, which already holds your mail. Raion sends and syncs through it. Disconnecting Raion does not delete the mailbox.
- Apple, for a passkey on an Apple device (the private key stays there) and for APNs notifications in both iPhone apps. We encrypt the mail and reminder text before sending it to Apple.
- A web push service, for Mail alerts and Calendar reminders. It handles the subscription endpoint and encrypted payload, not readable message or reminder text.
- Oracle Cloud, for app hosting and the vault that wraps secret keys.
- Cloudflare R2, for database backups encrypted before upload.
We do not sell personal information. We do not send it to advertisers, data brokers or anyone who wants it for their own marketing. The marketing site uses system typefaces. It sets no cookie of its own and does not use an analytics or advertising tag.
How long we keep it
- While your account is open, we keep the data the apps need to provide them, including the synced copy of mail and events.
- Removing a mailbox from Raion Mail deletes that mailbox’s messages, sealed secrets and related rows within 24 hours. Nothing is deleted on the mail host.
- Deleting Raion Mail data removes Raion’s copy shortly afterwards (the purge runs about ten minutes later). The Raion account stays, and so does the mailbox.
- Deleting the Raion account marks it deleted at once, ends its sessions, and tells every Raion app. Raion Calendar revokes the Google tokens, tries once to remove Busy copies it created, and deletes its rows. Raion Mail deletes its copy as above. The account service purges its own rows 30 days later.
- A web session lasts about 30 days and is extended while you use it. You can revoke it. An expired mail session that ended more than 30 days ago is pruned.
- Booking records have no timed cleanup, as described in Booking guests.
- OpenAI’s abuse-monitoring retention applies to cloud-AI inputs and outputs as described above. Encrypted backups roll off on the 14-daily and 8-weekly schedule.
Export and deletion
Email hello@raionai.com and we will send a copy of the account data Raion holds. Your messages and your provider calendars also stay with those providers, and you can export them there. The apps do not yet have a download button.
Delete the Raion account at account.raionai.com. That deletion is sent to every app, and it revokes Google tokens. Delete only Raion Mail’s copy from Raion Mail’s settings. That leaves the Raion account and the mailbox in place. Signing out of a single app ends that app’s session. Signing out everywhere ends the Raion account sessions and tells each app.
Security
Traffic uses HTTPS. Mailbox passwords and Google tokens are sealed with a key per account or per calendar connection, and that key is wrapped by a key in Oracle Cloud Vault. Database access for the apps is limited to the signed-in user. Connecting or removing an account, and deleting the account, ask you to sign in again with your passkey.
The servers can read the mail and events they store. A person at Raion does not read them unless you agree, we need to for security, or the law requires it. This is not end-to-end encryption.
Cookies
We use session cookies only. We do not use advertising or analytics cookies, and we do not set a cookie on raionai.com.
account.raionai.comsets a host-only session cookie for sign-in, and__Host-account_sessionfor the account pages.mail.raionai.comsets__Host-mail_session, and a short-lived__Host-mail_authcookie while a sign-in is in progress.calendar.raionai.comsets__Host-calendar_session.
The __Host- session cookies are HttpOnly, so a page script cannot read them. Both Raion iPhone apps use tokens stored on the device instead of a browser cookie. Public booking routes do not use sign-in cookies.
Children
Raion One and its apps are not directed at children under 13, and an account requires an invite. We do not knowingly collect personal information from a child under 13. If you believe we have, email hello@raionai.com and we will delete it.
Changes
If we change this policy, we will post the new one on this page and change the effective date. If we want to use Google user data for a purpose this policy does not already describe, we will ask you before we do.