You are trusting us with more than a resume.
Severance math. Runway numbers. The things you would only write down at 1am. This page answers the question that actually matters: who can see it, and who cannot.
Every claim below maps to a specific control in our code. We keep a claims register, audited it in July 2026, and fixed what did not hold up.Get started freeWho can see what.
| What you put in | You | Offboard staffthrough the product | LUMOour AI guide | AI providersOpenAI |
|---|---|---|---|---|
| Your Career Contextwork history, projects, and outcomes | Yes. Always | Limited. Not in admin screens. Support can open your resume, only with a logged reason | Yes. Yes. This is what it works from | Limited. Processed to run a feature you asked for. Never for training |
| Resumes and documentsuploads, drafts, cover letters | Yes. Always | Limited. Only for support, after a typed reason and a second sign-in step. Every opening is logged | Limited. Only what you share in a conversation or run through a resume feature | Limited. Processed to power tailoring and parsing. Never for training |
| Money numbersseverance, runway, budgets | Yes. Always | No. Not shown in any admin screen. A database admin role exists for account support, and analytics store a risk band only | Limited. A computed runway estimate, only if you saved numbers and keep it enabled. Never the raw amounts | Limited. Only inside a feature you run. Never for training |
| LUMO conversationswhat you ask and what it answers | Yes. Always | No. No read path exists in the product | Yes. Yes. It is the conversation | Limited. Sent to generate the reply. Never for training |
| Google Calendarif you connect it | Yes. Always | No. No | No. Excluded from AI context entirely | No. Never sent to AI models |
Your Career Contextwork history, projects, and outcomes
- You
- Yes. Always
- Offboard staff
- Limited. Not in admin screens. Support can open your resume, only with a logged reason
- LUMO
- Yes. Yes. This is what it works from
- AI providers
- Limited. Processed to run a feature you asked for. Never for training
Resumes and documentsuploads, drafts, cover letters
- You
- Yes. Always
- Offboard staff
- Limited. Only for support, after a typed reason and a second sign-in step. Every opening is logged
- LUMO
- Limited. Only what you share in a conversation or run through a resume feature
- AI providers
- Limited. Processed to power tailoring and parsing. Never for training
Money numbersseverance, runway, budgets
- You
- Yes. Always
- Offboard staff
- No. Not shown in any admin screen. A database admin role exists for account support, and analytics store a risk band only
- LUMO
- Limited. A computed runway estimate, only if you saved numbers and keep it enabled. Never the raw amounts
- AI providers
- Limited. Only inside a feature you run. Never for training
LUMO conversationswhat you ask and what it answers
- You
- Yes. Always
- Offboard staff
- No. No read path exists in the product
- LUMO
- Yes. Yes. It is the conversation
- AI providers
- Limited. Sent to generate the reply. Never for training
Google Calendarif you connect it
- You
- Yes. Always
- Offboard staff
- No. No
- LUMO
- No. Excluded from AI context entirely
- AI providers
- No. Never sent to AI models
Sponsors are not a column here because they see none of it. That rule has its own section below.
Four things we can show you, not just say.
Only your account reaches your rows
Row-Level Security is enforced on every sensitive table in our database. Your session can only ever query data that belongs to you. Cross-account leakage is prevented at the database layer.
Support access is narrow and logged
Journals, private messages, LUMO chats, job applications and AI reflection sessions have no admin read path. Admin screens show counts, never contents, and never your financial entries. For support, an owner-level admin can open your uploaded files, resume and activity timeline, only after typing the reason and entering a code from a second sign-in step. Every opening is written to an audit log with who opened it, whose account, when and why.
One AI provider, no training
OpenAI runs our AI features, and OpenAI does not train on our API data. A few features send data to one other service each, such as voice practice and web search. Our Privacy Policy names every one.
Delete means delete
When you delete your account, we delete your data and every file you uploaded, including the messages and posts you wrote to others. We keep payment records, a sponsor's record of your seat, and the do-not-email list. Database backups expire on our database host's schedule.
A sponsor sees the program. Never the person.
Your former employer, school, or workforce program may cover your Offboard access. That pays for the account. It does not buy a view into it.
Not the CEO, not HR, nobody. Our Terms of Service make that a commitment, not a preference.
What a sponsor sees
- The roster it uploaded
- Each person's seat status: invited, claimed, paused or expired
- Activity counts, only once 10 or more people are counted, each rounded to the nearest 5
What a sponsor never sees
- Your resume
- Your applications
- Your LUMO conversations
- Your money numbers
- Anything you write
A connection you authorize sends your record somewhere we do not run.
Offboard can connect to assistants you already use. Each one gets its own access level: full access, read only, or off. Full access can read and update your account and run tools that spend credits. Read only can see your account but cannot change it or spend credits.
From that point, the conversation lives in your account with that provider, under that provider's terms. You can change or turn off access at any time in Settings. Your record stays with Offboard.
See how connections workWhere the line actually sits.
Offboard does not use end-to-end encryption. Our AI features need to read your text as text: a resume tailor cannot rewrite a bullet it cannot see. That means our servers process your data in readable form, and, like every cloud product, the company that hosts our database and the people who hold our service keys could technically reach it.
We weighed the alternatives. On-device AI is not good enough yet to do this work. A key only you hold would mean one forgotten password erases your record forever, and it would break everything that helps you while you are away, like reminders and weekly summaries. So we chose readable processing plus strict access control, and we tell you exactly where the line sits. If that ever changes, it will change on this page first.
What stands between that technical possibility and a person reading your record: support access needs a typed reason and a second sign-in step, identifiers are minimized in our server logs, admin actions are written to an audit log, and every sentence on this page is tied to a control in our claims register.
We do not hold a SOC 2 or ISO certification, and we will not imply otherwise. When that changes, it will say so here.
Found a security issue? Our vulnerability disclosure policy says how to report it.
For the reader who wants receipts.
Sign-in and sessions
Google or email and password, handled by Supabase Auth with the PKCE flow. Sessions use short-lived tokens that refresh automatically. AI provider keys live only on our servers as encrypted secrets, and never reach your browser.
Your files
Your resumes, documents and Messages files sit in private storage, in a folder tied to your account. The app opens them through signed links that stop working after one hour or less. Each new file gets a random name in storage. The storage server refuses a file over its size limit or of a type the app does not take. It checks the file type the upload declares, not the file's contents. A Messages file link made before October 18, 2026 can work for up to a year.
AI, precisely
OpenAI runs our AI features, and OpenAI does not train on our API data. Chat and analysis requests are sent with storage off. Voice, transcription and file reads cannot turn storage off, and OpenAI may keep API data up to 30 days for abuse monitoring. Google Calendar data is excluded from AI context entirely, under Google's Limited Use policy.
Validation and abuse limits
Many server functions check requests before acting on them. AI and abuse-prone endpoints are rate-limited per account.
Infrastructure and accountability
Our database and file storage are managed by Supabase, which encrypts data at rest and in transit at the hosting layer, not end to end. We minimize identifiers in our server logs: user IDs are truncated and emails are masked. Admin actions are written to an audit log. We maintain a claims register that maps every public security claim to the code that enforces it, and we ran a full audit and hardening pass against it in July 2026.
These are product features, not legal concessions.
You do not need to cite a regulation to use any of them.
- 01 See and edit everything you have put in, at any time.
- 02 Delete a single document, a single entry, or your whole account. Account deletion removes your files too.
- 03 Export your resumes and documents whenever you want.
- 04 We do not sell your data. To power AI features it goes to OpenAI, under the no-training terms above.
These map to the rights GDPR and CCPA give you, wherever you live. Found something, or have a question this page does not answer? Email info@offboard.co. A human reads it.
Asked our team for help through our request form? Those answers are health information, kept apart from your Offboard record. Our health data privacy policy covers them.
Now you know exactly what you are trusting us with.
Build your Career Context knowing who can see it, who cannot, and what you can delete.
Independent support. Start free.
