New: Trust & Privacy Manifesto
Read our founder's personal commitment to privacy and why OSQR is built on architectural trust, not promises.
Privacy is Capability
If you can't trust your AI, you can't use it to its full potential. OSQR is built on privacy from the ground up.
"Your data belongs to you."
OSQR exists to make you more capable — not to extract anything from you. Everything you upload, write, think, or store in OSQR belongs solely to you. Your data is never sold, and never used to train AI. The only thing it's ever shared with is the AI provider that answers your request — and only the text that request needs. OSQR uses your data to think for you, not for anyone else.
OSQR is a private intelligence engine — not a data farm.
1Our Privacy Commitments
Your Vault is Yours Alone
Your files, chats, uploads, and memories are encrypted at rest and isolated to your account. OSQR's systems use them only to work for you, and your content is never sold. We don't read your content as a matter of course — the rare exception is a named engineer investigating a specific fault on your account, which we keep to what the problem requires.
Never Used for Training
OSQR does not train any AI model on your data — ours or anyone else's — and the AI providers we send requests to don't train on it either. Not now. Not ever.
Encrypted & Secure
Your vault is encrypted at rest (AES-256-GCM) under a key unique to your account, and protected in transit (TLS 1.2+, TLS 1.3 on modern clients). Embeddings are stored as numeric vectors, not as readable text. OSQR can decrypt your content to do the work you're asking for — that's what makes an assistant that knows your world possible — so this is not zero-knowledge, and we won't claim it is.
The "Burn It" Button
Delete your data instantly. One click. Irreversible. Documents, embeddings, chats, memories, vault, profile, cached outputs and logs — gone for good. It deletes your whole workspace, which takes your business's records inside it with it: website and text conversations, voicemails, call transcripts, and the contact records of the people you deal with, with every note about them. What it does not reach: the phone number rented for you, which has to be released separately; voicemail audio held by the telephony company; and the do-not-contact list, which we keep on purpose so nobody who asked you to stop texting them is ever resurrected.
2Privacy Tiers
You control how your data is used. Choose the level that fits your comfort.
Maximum Privacy
- Nothing leaves your vault except what's sent to AI models to answer your questions
- None of your data improves OSQR globally
- No anonymization, no analytics on your content
- Fully private — the strictest setting
Improve My OSQR
- No raw content is ever shared
- Optionally allow OSQR to learn from patterns only
- Example: "User sets fitness goals but doesn't follow through"
- Improves your personal model — not anyone else's
Global Patterns
- Opt-in only, off by default, extra warnings
- Anonymously contribute patterns (never content)
- Zero identifiable data — aggregated trends only
- Help improve OSQR for everyone (the "Waze" model)
3Where Your Data Lives
| Data Type | Storage |
|---|---|
| Your Documents | Encrypted database (PostgreSQL + Neon) |
| Your Embeddings | Numeric vectors — not stored as readable text |
| Your Profile | Encrypted rows tied only to your account |
| Your Chats | Encrypted at rest; only the text needed for a request is sent to AI providers |
| AI Requests | Only the text needed to answer your question is sent to AI providers |
| Mail and texts the OSQR Mac app reads | Message bodies encrypted under your account's key; sender, subject and date stay readable so search works (see section 10) |
| Location (iPhone app) | Only arrivals at and departures from places you named, kept 30 days; your spot during a conversation is used for that conversation and not kept (see section 11) |
| Site passwords OSQR holds for you | Encrypted under your account's key so OSQR can sign in for you; you can reveal one, and every reveal is recorded |
| Connected accounts (Google, Microsoft and others) | Access tokens encrypted at rest; disconnecting revokes and deletes them |
4How Your Content Is Accessed
Being honest: OSQR is not “zero-knowledge.” Running the AI means our servers have to decrypt and read your content to answer you. So the promise isn't “we can't see it” — it's that we tightly limit who and what touches it, and never use it against you.
OSQR never:
- ✕Sells or rents your data
- ✕Trains AI models on your content
- ✕Shows you ads or builds ad profiles
- ✕Lets staff open your vault documents — no support tool can reach them
- ✕Reads your conversations without your say-so, or without leaving a record
- ✕Keeps a hidden copy after you delete
What OSQR actually accesses:
- ✓Decrypts your content on our servers, only to run the AI and features you ask for
- ✓Sends only the text needed for a request to AI providers (who don't train on it)
- ✓Lets staff see account metadata by default — email, plan, billing, error logs
- ✓Reads your conversations only when you approve a specific request, for a set number of hours, with a record you can read
- ✓Lets the founder open the memory notes OSQR keeps about you, to check the quality of its work; every look is written to a record attached to your account
- ✓Stores your content encrypted at rest, isolated to your account. A few labels stay readable so search works, such as the sender, subject and date of mail the Mac app reads
5The "Burn It" Button
Instant, Complete Deletion
When you click "Burn It," OSQR permanently deletes:
- • All your documents
- • All embeddings
- • All chat history
- • All memories
- • Your entire vault
- • All profile data
- • Cached model outputs
- • All system logs
- • Your workspace and everything filed in it
- • Website and text conversations
- • Voicemails and call transcripts
- • Your encryption keys, destroyed first
Once deleted, OSQR cannot recover your data.
There is no undo. No internal archive. No ghost copy for analytics. Our database provider keeps short-term encrypted backups of its own, on its own clock, and deleted rows age out of those with time.
What Burn It does not reach. If you rent a phone number through us, that number is not handed back to the telephone company by this button — write to us and we will release it. Voicemail audio sits on the telephony company's systems rather than ours, and is not deleted by this button either. We keep the do-not-contact list: if somebody replied STOP to your business, that stays, because erasing it would let them be texted all over again. Contact records (the people list your conversations built up, and every note about them) are deleted with the workspace.
Legal exception: In rare cases where OSQR is required by law, regulation, valid legal process (such as a subpoena or court order), or governmental request to preserve data, the "Burn It" function may be temporarily suspended for the affected account until the legal obligation is resolved. We will notify you if this occurs, unless prohibited by law from doing so.
6How AI Requests Work
When OSQR sends something to AI providers (OpenAI, Anthropic, etc.), the rule is simple:
Only the exact text necessary to answer your question goes to the model.
Example:
If you ask: "Summarize page 4 of my document"
→ OSQR only sends page 4's text to the AI
Example:
If you ask: "What were my goals last month?"
→ OSQR fetches goals from your vault internally, sends only your question and the relevant text
You control what is sent because it is always tied to your explicit action.
7Encryption & Security
At Rest
AES-256 encryption via Neon/PostgreSQL
In Transit
TLS 1.2+ / HTTPS for all connections
Your OSQR password
Hashed with bcrypt/argon2 (never stored in plain text)
Site passwords you let OSQR hold
Encrypted under your account's key, not hashed, because OSQR has to use them to sign in for you. You can reveal one (behind Face ID on the phone), and every reveal is recorded.
Embeddings
Stored as numeric vectors, not as readable text
8What OSQR Collects
Always: your email address, your password (hashed), your plan, usage counts (never content), and the profile details you choose to give.
Only what you connect or switch on:
- Google or Microsoft: your mail, calendar and contacts, read when a request needs them, plus one first read when you connect (section 13).
- The OSQR Mac app: texts from people you know, the mail in Apple Mail, and your calendar (section 10).
- The OSQR iPhone app: arrivals at places you name, and your spot while you talk to OSQR (section 11). The microphone, camera, photos and contacts are used only when you press, pick or tap.
- A business phone line or website chat: the calls, texts and chats that come to it (section 12).
No ad tracking. No selling. No shadow profiles: what OSQR knows about you comes only from what you connected, and Burn It deletes all of it.
9What OSQR Does On Its Own
Reading is quiet. Acting asks. When OSQR wants to send an email, text someone, add a guest to your calendar, post, buy something or change files on your Mac, it shows you a card with exactly what it will do, and nothing happens until you press Approve.
You decide what goes on its own. Tell OSQR in your own words (“you can handle my calendar without asking me”) and that kind of action goes without a card from then on; say stop, or press Stop under Settings → What OSQR handles, and it asks again. What you ask for in the moment goes now. How much it may spend without asking starts at $0. In Settings → Integrations each connected service can be Off, Ask first, or Auto.
Some things are never handed over: money, the first sign-in to a website, messages to people outside your circle, public posts, and any job that changes files or runs commands on your Mac. Each of those asks when it is OSQR's own idea, and a purchase asks even when you asked for it.
On a business line, answering callers, texters and website visitors live is the job the business switched on, so those replies go without a card.
Words from outside are not orders. Email, texts, customer messages and web pages from other people reach OSQR marked as coming from outside your account, so an instruction hidden in someone else's message is read as their words, not yours.
10The OSQR Mac App
The OSQR Mac app is optional. It lets OSQR work with what lives on your Mac. To do that, macOS asks you for Full Disk Access (so it can read Messages) and for permission to work with Messages, Mail and Calendar.
- Texts: new texts in Messages are read. OSQR keeps the ones from people you know (your circle, people it texted for you, people a task is waiting on). Everyone else's texts are counted and dropped, not kept.
- Mail: the mail in every account signed in to Apple Mail is copied to your OSQR account, so OSQR can find it again. The message bodies are encrypted; the sender, subject and date stay readable for search.
- Calendar: your events from yesterday to two weeks ahead.
- Jobs: OSQR can do work on your Mac, using its own Chrome window with the sites you signed in to. A job that only looks starts when you ask for it. A job that changes files or runs commands waits for your Approve.
You stay in charge of it. Disconnect it from Settings → Reach on the web and OSQR can no longer reach that Mac. From the Mac app's next version, its menu at the top of your screen also has Pause (it stops reading and stops taking jobs until you resume) and Unpair. You can also turn off any of the macOS permissions in System Settings → Privacy & Security, or quit the app.
11Location on the OSQR iPhone App
OSQR uses your location only for things it does for you:
- Places you name. Tell OSQR “this is the job site” and it notices when you arrive or leave, so it can have the right things ready when you pull up. Those arrivals and departures are kept for 30 days.
- Near me (from the app's next update). Each message you send from the app carries where the phone is, so OSQR can find a place nearby or tell you how far the job is. The spot is used to answer that message and is not saved; Google Maps sees it, to name the area and find places. OSQR's answer is saved like any message, so if the answer names where you are, the answer keeps that.
- Driving. The phone notices when you are driving, so OSQR answers out loud and keeps it short.
Anywhere else you go is not kept: a stop that is not one of your places is thrown away, and from the app's next update it is not sent at all. OSQR cannot see anyone else's location. You can turn location off in your iPhone's Settings, and from the app's next update, from its person menu too (named places, near me and the driving watch all stop).
12When OSQR Runs on a Business's Website or Phone Line
Some businesses use OSQR to power the chat on their own websites, the text lines on their own phone numbers, and — where they have switched it on — to answer those numbers when somebody calls. If you chat, text or speak with one of those assistants, you are talking to that business, not to OSQR: the business is the controller of your data. Its privacy policy governs the conversation, and OSQR processes it on their behalf under our Data Processing Agreement.
The first time you call one of those numbers and an assistant answers: before the assistant picks up, a short automated notice tells you that the call is recorded and that you are speaking with an AI assistant: “This call is recorded and answered by AI.” If you have called that business before and already heard that: the notice is a short reminder that the call is recorded: “This call is recorded.” Here “recorded” means the call is written down as it happens: the words are kept as a transcript, and the live audio of your conversation with the assistant is not kept. The owner of a number may turn off the words about recording; the call is still written down, and the notice still says the call is answered by AI. Nothing else changes on a later call — you are still speaking with an AI assistant, and whenever you ask whether you are talking to a person, on that call or any other, it will say plainly that you are not. Your voice reaches that assistant live, as you speak, through one of the two AI providers we have approved for that job — one is in use at a time, and every provider we use is on our subprocessor list. The words of the conversation are written down and kept with the business's record of you. The live audio of that conversation is not kept. If the assistant puts you through to a person at the business, that part of the call is recorded so it can be transcribed, and the audio is deleted once it has been.
A voicemail is different. If nobody answers and you leave a message, that message is an audio recording. It is held by the telephony company that carries the call, transcribed so the business can read it, and today nothing deletes that audio on a schedule — we keep the transcript, they keep the recording.
How long it is kept: for now, until the business closes its OSQR account and deletes its workspace. There is no expiry date on a conversation and no automatic clean-up that removes one: a typed chat, a text thread, a voicemail transcript and the written record of a call all stay while the account exists. We are building a proper deletion tool — a way to erase one person's records on request — and until it ships we do it by hand. Write to us at info@osqr.ai and we will carry it out and tell you when it is done.
To exercise privacy rights over one of those conversations, contact the business you were talking to — they hold the relationship, and we support them in honoring your request. For text lines, reply STOP at any time and messaging ends immediately. On a call, saying you do not want to be contacted again is enough — the assistant writes it down, and from then on that business cannot text you or dial you through OSQR on any of its lines, not just the one you were on.
13Google User Data & Third-Party Integrations
When you connect your Google account (Gmail, Calendar, Drive, Contacts, Tasks) to OSQR, OSQR receives a scoped OAuth grant from Google that lets OSQR act on your behalf inside your Google account. This section describes exactly what OSQR does with that access and what it does not do.
When you connect, OSQR reads your sent mail and the last 90 days of your inbox one time, to learn who your people are. He keeps a label and one line about each person, never the mail itself.
Scopes OSQR requests from Google
| Scope | What OSQR uses it for |
|---|---|
| gmail.modify | Read, label, archive, send, and reply to emails when you instruct OSQR (or your OSQR VA) to do so. OSQR only acts on messages in response to your explicit commands or the automations you configure. |
| calendar | Create, update, and read events on your Google Calendar when you ask OSQR to schedule, reschedule, or look up meetings. |
| drive.file | Open and save only the specific Drive files you ask OSQR to work with (per-file access — OSQR cannot browse your whole Drive). |
| contacts | Look up and create contacts when you ask OSQR to email or message someone. |
| tasks | Read and write items to your Google Tasks when you ask OSQR to capture or complete a task. |
| userinfo.email | Identify which Google account the grant belongs to. Not used for marketing. |
| webmasters.readonly, analytics.readonly | Only if you separately connect Search Console and Analytics: read your own websites' search and visitor numbers. Read-only. Asked for in its own Google screen, never at sign-in. |
| youtube.readonly | Only if you connect YouTube: list your channel's videos so OSQR can read their captions. Read-only. |
Google API Services User Data Policy & Limited Use
OSQR's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:
- OSQR does not use Google user data (including Gmail message content) to train generalized or third-party AI / ML models.
- OSQR does not sell, rent, or transfer Google user data for advertising, re-selling, or any purpose unrelated to the user-facing features you asked OSQR to perform.
- OSQR does not allow humans to read Google user data except (a) with your explicit consent, (b) where necessary for security investigations or to comply with applicable law, or (c) where the data has been aggregated and anonymized for service-operations purposes (e.g., error counts).
- OSQR only transfers Google user data to the AI providers needed to fulfill the specific request you made (e.g., summarize this thread), and only the text needed to answer that request. Sub-processors are contractually bound not to use the data for training.
Where Google data lives in OSQR
OSQR does not maintain a persistent mirror of your Gmail inbox. Messages are fetched from Google on-demand when you (or your automation) ask OSQR to act on them, and are discarded from working memory when the request completes. (One exception you control: if you install the OSQR Mac app and your Gmail is signed in to Apple Mail, the Mac app copies that mail as described in section 10.) OSQR stores:
- Your OAuth access and refresh tokens, encrypted at rest in our Neon (PostgreSQL) database.
- Minimal metadata required to support your automations (e.g., the Gmail message ID you told OSQR to follow up on).
- Logs of actions OSQR took on your behalf (who, what, when — never the message body), for audit and support.
Microsoft 365 and other connections
If you connect Microsoft 365 instead of (or as well as) Google, OSQR asks Microsoft for Mail.ReadWrite, Mail.Send and Calendars.ReadWrite (with their read-only versions), and treats that mail and calendar exactly as described above for Google: read when a request needs it, and every send or invitation behind a card unless you choose otherwise. Each other service you connect (Slack, QuickBooks, Jobber, social accounts) shows what it can do on its card in Settings → Integrations, and Disconnect there revokes it.
How to revoke OSQR's access to your Google account
You can remove OSQR's access at any time:
- 1.Inside OSQR, open Settings → Integrations and click Disconnect next to Google. OSQR immediately revokes its OAuth token and deletes the stored credentials.
- 2.You can also revoke access directly from Google at myaccount.google.com/permissions.
- 3.The "Burn It" button (described above) deletes every OAuth token OSQR holds for you as part of the full-account wipe.
A Note from the Founder
I built OSQR to be the AI assistant I always wanted — one that truly knows me, remembers my context, and helps me think better. But that kind of deep integration requires trust.
If you're going to index your entire life into an AI system — your documents, your thoughts, your goals, your struggles — you need to know that data is sacred.
That's why OSQR is built on privacy from day one. Not as a feature. Not as a marketing bullet point. As a foundation.
Your capability depends on your willingness to be honest with OSQR. And your willingness depends on trust. I intend to earn it.
Kable Record
Founder & 100% Owner, OSQR
Questions about privacy? Concerns? Ideas?
info@osqr.ai