Privacy Policy
Last updated: November 10, 2026
This policy tells you what data Telosnex collects, why, where it goes, how long we keep it, and how you delete it. It applies to the Telosnex apps, the web app at app.telosnex.com, and the website at telosnex.com. Telosnex Inc. ("Telosnex", "we", "us") operates them.
Summary
- You can use Telosnex without an account. On-device AI models and your own API keys work without one.
- If you sync, the app encrypts your conversations and other synced items on your device before upload. Telosnex servers store only the encrypted copy. We do not have the key.
- When Telosnex relays a request to an AI provider, the relay does not store or log the content of the request.
- Telosnex stores the sign-ins of your connected accounts and MCP servers on its servers, encrypted. Telosnex servers can decrypt them. They are not end-to-end encrypted. See Sign-ins of connected accounts and MCP servers.
- We do not sell your data. We do not use your data for ads. We do not use your data to train AI models.
- To delete everything, delete your account in the app. See Delete your data.
Data that Telosnex collects
Your account
If you make an account, Telosnex stores your email address. If you sign in with a password, Supabase Auth stores a hash of the password, not the password. If you sign in with Apple, Apple can give us your name. If you sign in with Google, Google gives us your email address.
Supabase Auth keeps an audit log of sign-in events, with the IP address. It deletes each event after 30 days.
Payments
Telosnex does not receive or store your card number.
- iOS and Android: Apple or Google takes the payment. RevenueCat tells us the status of your subscription.
- Web, macOS, Windows, and Linux: Stripe takes the payment on its own page. We give Stripe your email address and your account ID. Stripe gives us a customer ID. RevenueCat also gets the status of your Stripe subscription.
For each paid request, for example a chat message or an image, Telosnex stores a billing record. The record has the model, the number of tokens or characters, the image size, and the cost. It does not have the content of your request. We keep billing records until you delete your account.
Synced data
Sync needs an account and a membership. New items sync by default. You can make an item private, and then it does not sync. Synced items include conversations, attachments, settings, the API keys in your settings, MCP server settings, skills, spaces, and notification schedules.
The app encrypts each synced item on your device before upload (AES-256-GCM). The key stays on your devices. A recovery phrase of 12 words protects a copy of the key. Telosnex servers store only the encrypted copy and cannot read it.
The servers can see the data that they need to sync: the account ID of the owner, item IDs, file sizes, and the times of changes and deletions. When you delete a synced item, the servers keep the encrypted copy for 2 weeks, then delete it.
If you make a script public, its label and description are not encrypted. Anyone can read a public script.
Remote runs
If you start a run on one of your devices from another device, the command and the output pass through Telosnex servers. The app encrypts them before upload. The servers delete the output 5 minutes after the run ends, and the commands after 7 days.
Error reports
The apps and our servers send error reports and performance data to Sentry. The app reports can include the device type, the operating system, the app version, and the error. The app does not add your account ID to its reports. Server reports include a one-way hash of your account ID, the name of the server function, and timings. Sentry cannot use the hash to find your account. We can, when you ask us for support. Server reports can include the address of a web page that you asked Telosnex to fetch, and the address of an MCP server. We do not put the content of your conversations in error reports.
The app sends error reports by default. To turn them off, open Settings and turn off Error Reports. The app then stops sending them at once. If you are signed in, the setting also applies to your other devices when they next get your settings. Feedback that you send is not affected. Our servers always send error reports, with the hash of your account ID.
Feedback
If you send feedback from the app, we receive your note and the email address of your account. By default, the app also attaches its logs. The logs can contain text from your conversations. If you do not want to send the logs, turn off Include Logs before you send.
Device permissions
The app asks for a permission only when you use the feature that needs it:
- Microphone: for voice input and live conversations. The app does not store your voice. See AI requests for where audio goes.
- Camera and photos: to send a photo to the AI, to save AI images, and to scan a pairing code.
- Location (iOS): only because the camera can embed a location in a photo. The app does not read your location.
- Local network: to connect to Telosnex Widgets on your network.
The app does not ask for access to contacts, calendars, or health data. If you connect a Google, Microsoft, or iCloud account, the assistant can read contacts and calendars through that account. See Connected accounts.
Cookies and local storage
The website and the web app do not set cookies for tracking or ads. They do not use analytics. The web app keeps your sign-in session and your sync key, encrypted, in the local storage of your browser.
Cloudflare and our web host receive your IP address and the details of each request, as for any website.
AI requests
You choose where each request goes:
- On-device models and voices: the request stays on your device.
- Your own API key or account: the app sends the request directly from your device to that provider. The terms of your provider apply. Some providers train on data from some plans. Read the terms of your plan.
- Telosnex relay: the app sends the request to a Telosnex server, which sends it to the provider with Telosnex's account. The relay does not store or log the content. It logs the number of tokens. When Telosnex relays a request, it uses only AI provider accounts that do not train on it. To most providers, the relay also sends a one-way hash of your account ID, different for each provider, so that a provider can tell us about misuse by one account. The provider cannot use it to find your account.
A request contains the conversation and its attachments, for example text, images, files, or audio. Providers can keep requests for a limited time under their terms, for example to detect abuse.
The relay sends requests to these providers:
| Purpose | Providers |
|---|---|
| Chat models | Anthropic, DeepInfra, Fireworks, Google (Gemini API and Vertex AI), Groq, Inception, Meta, Mistral, OpenAI, Perplexity, xAI |
| Structured decisions | OpenAI, TypeSafe |
| Images | fal, Google, OpenAI |
| Voice and transcription | ElevenLabs, Google, OpenAI |
| Web search | Brave, Exa, Parallel, Serper |
| Photo search | Unsplash |
OpenRouter works only with your own key.
When you ask Telosnex to read a web page, for example a YouTube video page, the request can go through a Telosnex server. The website then receives the request from Telosnex, not from your device.
Connected accounts
You can connect a Google, Microsoft, or iCloud account. The assistant can then use tools that read or change your data in that account, for example your calendar or your email. The app calls the Google, Microsoft, or Apple service directly from your device. The tool result goes into your conversation. The conversation goes to the AI model that you picked, as described in AI requests.
You can also sign in with your ChatGPT account to use your ChatGPT plan. On the native apps, requests go from your device to ChatGPT. On the web app, they go through a Telosnex server, which calls ChatGPT with your sign-in. The terms of your ChatGPT plan apply. Personal ChatGPT plans can train on your data unless you turn this off in ChatGPT.
Sign-ins of connected accounts and MCP servers
What Telosnex stores, and why
If you are signed in to Telosnex, Telosnex stores each sign-in on its servers. Your other devices can then use the sign-in, and you do not have to sign in again on each device.
| Sign-in | What Telosnex stores |
|---|---|
| MCP server that uses OAuth (for example GitHub) | The access token, the refresh token, the server address, the address of its authorization server, the granted scopes, the expiry time, and, if the app gives them, the client ID and the token and revocation addresses |
| The access token, the refresh token, your Google email address, the granted scopes, and the expiry time | |
| Microsoft | The access token, the refresh token, your Microsoft email address, the granted scopes, and the expiry time |
| iCloud | Your Apple ID email address and the app-specific password that you made for Telosnex |
| ChatGPT | The access token, the refresh token, your ChatGPT account ID, and the expiry time |
If you are not signed in to Telosnex, the app keeps MCP sign-ins in memory only. They go away when the app closes.
How they are protected
Telosnex encrypts each token and password with a Google Cloud KMS key that is kept in a hardware security module. Then it stores the encrypted value in Supabase Vault.
These sign-ins are not end-to-end encrypted. Telosnex servers decrypt them to:
- refresh an access token before it expires
- give your devices a short-lived access token
- revoke a sign-in when you remove it
- call ChatGPT for you on the web app
Telosnex servers do not send refresh tokens to your devices. For iCloud, the access token that your devices receive contains the app-specific password.
Some sign-ins pass through Telosnex servers, because only they hold the client secret: Google, Microsoft, GitHub, and ChatGPT.
How long Telosnex keeps them
Telosnex keeps a sign-in until one of these events:
- You sign out of that account or MCP server.
- You remove the MCP server.
- You disconnect the account in Connected apps.
- You delete your Telosnex account.
When you sign out of Telosnex, Telosnex keeps your sign-ins for your next sign-in.
At each of these events, Telosnex asks the provider to revoke the sign-in. Then it deletes its copy. It deletes its copy also if the provider refuses or does not answer. In these cases, Telosnex only deletes its copy:
- Microsoft: Microsoft has no way to revoke a single sign-in. To remove access, remove Telosnex from the apps that can access your Microsoft account.
- iCloud: delete the app-specific password at account.apple.com, in Sign-In and Security.
- MCP servers without a revocation address.
- Google or GitHub, when another of your stored sign-ins uses the same grant. When you delete your Telosnex account, Telosnex revokes these too.
Data that you send to MCP servers
An MCP server is a service that you add. Telosnex does not operate it. Tool names, the arguments that the assistant sends, and the results go to the operator of that server. The privacy policy of that operator applies.
On the web app, some MCP requests go through a Telosnex server: the sign-in setup, the first request to each server, and each request without an access token. Other requests go directly from your browser to the MCP server. The Telosnex server forwards the request, which can include your access token. It does not store the request. It logs the address of the MCP server, the request method, and the response status. It does not log the content or the token.
Google user data
The use of information received from Google Workspace scopes will adhere to the Google User Data Policy, including the Limited Use requirements.
Telosnex gets data from your Google account only for the Google services that you turn on. The assistant uses this data only to do what you ask, for example to read your calendar or to send an email.
When the assistant uses a Google tool, the result goes into your conversation. The app sends the conversation to the AI model that you picked, so that the model can answer. If you use your own API key, the app sends it directly to that AI provider, and your provider's terms apply. If not, the app sends it through a Telosnex relay server. The relay does not store or log the conversation. When Telosnex relays a request, it uses only AI provider accounts that do not train on it.
Conversations are stored on your device. If you turn on sync, the app encrypts each conversation on your device before upload, and Telosnex servers store only the encrypted copy. Telosnex stores your Google refresh token encrypted on its server. The app never receives it.
Telosnex does not sell your Google data. It does not use your Google data for ads. It does not use your Google data to train AI models. No person at Telosnex reads your Google data, unless you ask us to for support, it is necessary for security, or the law requires it.
You can disconnect your Google account and delete your Google data from Telosnex at any time. See Google.
Service providers
These companies process data for Telosnex:
| Provider | What it does for Telosnex |
|---|---|
| Supabase | Database, sign-in, file storage, and server functions |
| Fly.io | Servers for the AI relay |
| Cloudflare | Network and DNS for telosnex.com, app.telosnex.com, and api.telosnex.com |
| Google Cloud | The KMS key that encrypts stored sign-ins |
| Stripe | Payments on the web and desktop |
| RevenueCat | Subscription status |
| Apple, Google Play | Payments on iOS and Android |
| Sentry | Error reports and performance data |
| AI and tool providers | See AI requests |
How we use data
We use data only to:
- give you the features that you ask for
- take payments and keep billing records
- find and fix errors
- keep the service secure and stop abuse
- answer your messages
- obey the law
We do not sell your personal data. We do not share it for ads. We do not use it to train AI models. No person at Telosnex reads your data, unless you ask us to for support, it is necessary for security, or the law requires it.
For people in the European Economic Area and the United Kingdom: we process your data to perform our contract with you, for our legitimate interest in a secure service that works, to obey the law, and, for connected accounts, with your consent.
How long we keep data
| Data | Kept until |
|---|---|
| Account and billing records | You delete your account |
| Sign-ins | The events in How long Telosnex keeps them |
| Synced items | 2 weeks after you delete the item, or when you delete your account |
| Remote run output and commands | 5 minutes after the run ends (output), 7 days (commands) |
| Sign-in audit log | 30 days |
| Error reports | The retention period of Sentry |
Delete your data
- Everything: open the menu, then Account, and tap Delete Account.
- One item: delete it in the app. If it is synced, the servers delete it 2 weeks later.
- One connected account: disconnect it in Connected apps.
- Your Google data: see Google.
When you delete your account, Telosnex:
- deletes your Stripe customer records and your RevenueCat subscriber record
- deletes your files in storage
- asks each provider to revoke your sign-ins, then deletes them
- deletes your account, your credits, your billing records, and all your synced data
CAUTION: Delete Account does not cancel a subscription that you bought from Apple or Google. Cancel it in the App Store or in Google Play first.
Error reports stay until Sentry deletes them. Backups of our database can keep deleted data until the backups expire. Data on your devices stays until you delete it or the app.
To get a copy of your data, open Backup in the app. It saves your data in one .zip file.
Your rights
Where you live can give you the right to access, correct, delete, or get a copy of your personal data, and to object to or limit its use. You can also complain to a data protection authority. To use a right that the app does not give you directly, send an email to [email protected]. We can ask you to prove that the account is yours. We do not treat you differently when you use a right.
California residents: we do not sell or share personal information, as the California Consumer Privacy Act defines these words.
Security
We use TLS for all network traffic. Synced data is end-to-end encrypted. Stored sign-ins are encrypted with a key in a hardware security module. No method of storage or transfer is 100% secure.
International transfers
Telosnex is in the United States. Our service providers process data in the United States and in other countries.
Children
Telosnex is not for people under 18. We do not knowingly collect data from children. If you think that a child gave us data, send an email to [email protected], and we will delete it.
Changes to this policy
When we change this policy, we change the date at the top of this page. Before an important change takes effect, we tell you in the app or by email.
Contact
Telosnex Inc.
1111B S Governors Ave STE 7711
Dover, DE 19904
United States
Email: [email protected]