# Privacy and data use | Rexzen

Source: https://rexzen.si/privacy/

RexzenPrivacyPRIVACY · DATA USE
Privacy and data use

Your account controls access to your notes. Rexzen’s server stores and processes them. Your chosen model provider receives the context sent with each request.
Updated 13 November 2026Public pages · Private workspace · Selected providers

Public site
Account and sign-in
Workspace records
Model requests
API keys
Assistant memory
App connections
Phone alarms
Locket audio
Research publications

The public site

Rexzen’s company, project and research pages are publicly accessible. You can read them without signing in to Aero.

The public site does not use advertising trackers. Sign-in state is used to provide access to your Aero account.

Your account and sign-in

Aero uses Google sign-in. Google profile information is used to identify your account and maintain your signed-in session.

Account data is private to the authenticated user. Signing in gives you access to your own workspace records.

Your workspace records

Aero stores your notes, relationships, projects, tasks, conversations and plans on the service. Access is scoped to your authenticated account. The server processes these records to provide workspace features.

Aero is not an end-to-end encrypted service. Account privacy controls govern access to workspace records, while the server processes them as part of the service.

Workspace exports exclude provider API keys.

Requests to model providers

Aero sends your message and its selected context pack to the provider of the chosen model. Automatic context can retrieve eligible, AI-enabled records and memory; you can turn it off or require a review before each send in Controls. The older workspace flow continues to use explicitly selected sources. Private or excluded records are not retrieved into a fresh request.

The selected provider processes the information sent to it. Its own terms, account settings and data policies apply to that processing.

Provider API keys

If you bring a supported provider API key, Aero stores it encrypted on the server so the service can make requests to that provider. Keys are excluded from workspace exports.

Encryption of a stored API key is separate from end-to-end encryption of workspace content. The server uses the key when making an authorised provider request.

Assistant history and memory

Aero saves conversations independently of the model used for each reply. Switching a model keeps the same saved conversation. For each request, Aero selects a bounded context pack from recent messages and, when automatic context is enabled, eligible memories, workspace records, calendar events and library excerpts. Older messages may be shortened or omitted from a request; the original saved conversation remains in your account.

You can inspect the context and routing used for an answer, exclude eligible records, and enable review before every send in Controls. Memory importance, confidence and relationships affect retrieval. Tentative inferences are labelled and expire by default. A daily mood and capacity check-in is optional. Aero may use enabled context for a gentle check-in or reminder; it does not establish your mood as a verified fact.

Workspace and assistant records use managed server encryption and account-scoped access. They are not end-to-end encrypted. Archiving hides records from normal views; it does not erase saved history or copies already exported. Assistant exports exclude provider keys, Google refresh tokens and phone pairing credentials.

Private Spaces group study, work and research information within your account. Known institutions can be detected from saved email, document and calendar text without a model call; you can turn this off in Controls. A detected space does not establish enrolment or an affiliation. New space notes and imported curriculum text begin excluded from AI context. Each has an explicit AI-context switch. When you enable it, relevant excerpts can enter the bounded context sent to your chosen model in a future chat. Excluding an item invalidates a previously prepared request that contained it; separate email permissions remain unchanged.

PDF text is extracted in your browser. Choosing Read image sends that selected curriculum image to your chosen available vision model for transcription; the text remains editable before saving. Reading a public institutional page sends its URL to Aero's server without portal credentials. Private portals require your normal sign-in and an imported excerpt or download. Dates found in sources are suggestions to review, not confirmed tasks or submissions.

Google and other app connections

Normal Google sign-in requests basic identity information. Reading Gmail and Calendar requires a separate, explicit connection with read-only Gmail and calendar-event scopes. These scopes do not permit Aero to send, modify or delete Google messages or events.

When connected, sync can import a bounded selection of recent email and upcoming events. Google refresh tokens stay encrypted on the server. Email is excluded from model context unless you separately enable email AI context. The optional Keep Google up to date setting refreshes this read-only connection at most once per fifteen minutes while Aero is visible or a paired Android device syncs. This refresh makes no background model calls. Android may defer its background jobs.

Disconnecting Google revokes future token access, excludes imported email from AI context, and archives imported calendar entries and their reminders. It does not erase earlier saved conversations or data already sent to a chosen provider. Only configured, consented connections are active. System sharing opens the app you choose; it does not connect personal WhatsApp or Instagram accounts automatically. Payment accounts are not connected and Aero does not execute payments.

The released router experiments use synthetic examples. Aero does not automatically send your workspace or Google data to Colab or use it to train the released routing models.

Text and Slack export files are read into an editable import form. Saving sends the edited excerpt to your Aero account. Imported documents are excluded from model context unless you enable that access. Aero's local dictation requests browser on-device speech recognition when supported. Approximate location uses one device reading at your request. The coordinates stay in the draft until you choose to send it. Aero Local runs separately on your computer and does not use your Aero account.

For a selected Slack, Notion, or Drive preview, Aero passes the access token you supply to that provider for one read. Aero does not store the token. You can edit the preview before saving it to your library. Model access stays off unless you enable it separately.

Local memory and check-ins

On-device chat runs in your browser without an account. The first setup fetches a public model file from its publisher. Aero keeps the latest 40 messages in this browser. It reads a selected text or PDF excerpt on your device and uses it for one reply. The reply can quote the excerpt. Clear the conversation or remove the model from On-device model settings.

Aero Local saves notes in a private file under your computer user account. It can include a file excerpt that you select and review for one local reply. Attached excerpts are not kept by the runner. A reply can quote them and remains in the browser tab until cleared. Notes are private by default. When you share a note with a connected agent, that client can retrieve it and may send it to its model provider. You can stop sharing a note at any time.

Today shows schedule load based on due tasks and upcoming timed events. It does not infer mood from those counts. The optional greeting is in the browser and respects quiet hours and a three-day cooldown after a response or dismissal. You can clear your self-reported check-in.

Phone alarms and meeting links

You can set a one-time alarm on Android without an account. Its name, schedule and response stay on the phone. Phone alarms require device permissions. To receive synced reminders and meeting links, pair the app with your Aero account. A phone pairing can read reminder titles, details and meeting links and acknowledge responses. It cannot read the conversation ledger, private document library or provider keys. The server stores a hash of the pairing credential; the Android app encrypts it with Android Keystore. You can revoke a pairing in Aero. A downloaded pairing file should remain private. The app reports basic last-sync time, permission status, app version, synced reminder count and maths test results to your own Aero account for setup and troubleshooting. It does not upload other phone files or contacts.

Once synced, the phone schedules alarms locally. A response or maths challenge dismisses an alarm. Background sync is not instant push delivery. A meeting link opens only after your choice, and opening the link is recorded separately from attendance. Meeting responses are saved across devices. A five-minute snooze updates the linked reminder; the phone receives it on its next sync. “I’ve joined” records your own report, not attendance verified by a meeting provider. A calendar text update preserves that response; a changed start time or meeting link clears it. Browser alerts work while Aero is open; the website alone cannot guarantee a locked-phone alarm.

Locket audio

Voice asks for microphone access when you choose to record on your phone. It asks for nearby-device access only when you connect a Locket. A one-time download installs a speech model. The app uses it to transcribe completed clips on the phone and discards incomplete audio. An edited transcript can become a Chat draft, a local model prompt, or the label on a phone alarm. You choose its destination and confirm the alarm time yourself. The app keeps an unclaimed draft in memory for up to two minutes. Phone Models downloads only the public weight file you select. It keeps up to 20 exchanges in private app storage, uses a bounded recent context, and makes no inference requests to a remote service. Clearing the local conversation removes those saved messages.

Research publications

The Research directory shows paper titles, summaries and the scope of each manuscript. Reading or downloading a PDF requires the shared paper password.

The password is used in your browser to unlock the selected files. It is not sent to Rexzen or saved by the website. PDFs remain unlocked for that page until you lock them or leave.

Author source documents and internal research assessments are not included in the website.
