Offerin

Privacy policy

Beta version of 2026-10-25

Beta version

This text applies while Offerin is in its invite-only beta and describes what Offerin stores and does today. It will be revised before Offerin opens to everyone, and the app will tell you before a revised version applies. Still being settled:

  • who is responsible for Offerin: the legal name of the person or company, and a postal address if the laws that apply need one
  • which model provider the server uses (this text names Anthropic), and that provider's terms for the text it receives: how long it keeps it and whether it may use it for training
  • the retention periods of section 10, which follow the current server settings
  • which privacy laws apply (for example in the EU, the UK or California) and what they require this policy to add, after a legal review
  • that privacy@offerin.app reaches the owner (until it does, Help and feedback in the app is the sure way)
  • the minimum age of 16
  • the date the open-launch version takes effect, which new accounts then record

1. Who runs Offerin

Offerin is run by its owner. For anything about this policy or your data, write to privacy@offerin.app or, when signed in, use Help and feedback.

2. What Offerin stores

  • Your account: your email address and whether it is verified, your name when your sign-in provider gives one (Google does), the name you choose to go by in Offerin, how you sign in (Google, or email and password), the sign-in service's identifiers for you, when the account was created and last signed in, and which version of these documents you were shown.
  • Your password, if you use one, is held only by Amazon Cognito, the sign-in service, as a salted hash. Offerin never receives it. If you sign in with Google, Cognito also keeps the link to your Google account.
  • Your invitation, while Offerin is invite-only: the invited address (for an invitation by code, no part of the code is kept), a note by the person who invited you, who invited you, when it was made, until when it works, and which account used it and when. If a sign-up is refused (no invite, or sign-up paused), Offerin makes no account, but Cognito keeps the sign-in you created there (your address and password hash, or your Google link), so that you can sign in once you may.
  • Your record, as you enter it or accept it: your profile, work authorization and immigration status, goals, experience, education, projects, evidence, skills and their sources.
  • The roles you track: postings, requirements, eligibility notes, application events and dates, and the contacts and outreach you record. Contacts are other people's names and details that you choose to add.
  • What Offerin makes for you: resume drafts and their exports, daily check-ins with their replies and summaries, lessons, the news briefing and your feedback on it, suggestions, and proposals waiting for your review.
  • Access tokens you create for your own agents: their names, access, first characters and when they were last used. A token itself is kept only as a one-way hash.
  • Your browser sessions: an identifier, when each started and was last used, and your account's identifier.
  • Daily usage counts per account (model calls with their size, posting links read, data exports), which keep the cost of the service within fixed limits.
  • Server logs: IP addresses, browser user agents, the addresses requested and account identifiers, for security and operations. Logs do not hold the text of your record or your check-ins, email addresses or tokens.
  • Usage and error reports, kept in Offerin's own database and never sent to another company: which pages of the app you open and when (the page's address without any identifiers in it), and when something breaks, the error's message and where in the code it happened, with email addresses, identifiers and long numbers removed. They tell the team how the app is used and what to fix, and they are not linked to the content of your record.

3. Where it is kept

On Amazon Web Services in its us-east-1 region (Northern Virginia, United States): the server and its database, the backups, the logs and the sign-in service. If you use Offerin from another country, your data is transferred to and stored in the United States.

4. Who processes your data for Offerin

  • Amazon Web Services: hosting, the sign-in service (Amazon Cognito), email to you, backups and logs.
  • Google: only if you sign in with Google.
  • Anthropic: the model behind some features, which receives the text those features need (section 5).
  • Cloudflare: the registrar and DNS of offerin.app. It sees DNS lookups, not your traffic.

5. What the model receives

Text goes to the model only when you use one of these features, and only this text:

  • A check-in reply: your messages of the day and the earlier replies, with the parts of your record the reply refers to: your headline and summary, your projects (names and descriptions), your experience (titles, organizations and summaries), your latest evidence statements, your skills, and the summaries of your last ten days of check-ins.
  • The wrap-up of a check-in: your messages of the day, the summary you confirmed, and the names of your projects and the titles and organizations of your experience, so it can propose evidence under them for your review.
  • The daily lesson: its topic (a skill or an interview stage), the title of your primary goal, and for an interview lesson the job title of that role. Never a company name or a posting's text.
  • Reading a job posting you paste or open in Jobs: the posting's text.
  • Reading a resume you paste: the whole text you pasted, with email addresses and phone numbers removed first. Anything else in it, such as a postal address or a visa status, is sent as you wrote it.
  • Checking a resume draft, when you ask for it: the role it is for (its title and company) and that role's recorded requirements; each line on the page with the heading of the entry it sits under (a job, a school or a project), the evidence from your Library behind it and that evidence's skills; and other evidence from your Library under the same entries that is not on the page yet. Not the name or contact details in the resume's header.
  • Practice feedback: the topic and the answer you typed.

The work authorization and contacts you keep in Offerin, and your account's email address, are never sent to the model; a resume you paste is sent as described above. Tagging the news uses public news items only. Features that need the model have daily limits, and when a limit is reached they say so and send nothing.

6. Job posting links

When you paste a job posting link, Offerin's server fetches that page, and the employer's public job board where there is one, from its own address and without your cookies. The posting's public details are kept in a shared store of postings that records no account.

That store files a posting under its job board's own posting identifier, or, for any other link, under a one-way fingerprint of the link, and keeps beside it only the link's address up to its path: whatever follows a “?” or a “#” in the link is never stored there, since some links carry a private token. The link as you pasted it is saved only on the role you track, and is deleted with your account.

7. Agents you connect

If you create an access token for your own AI agent, that agent can read your record and propose additions with the access you gave the token, until it expires or you revoke it in Settings. What your agent and its provider then do with that data is outside Offerin and governed by their terms.

8. Cookies and browser storage

Offerin sets two cookies, both strictly necessary: a session cookie that keeps you signed in, and a security cookie that lets Offerin check that a change really comes from its own pages. The sign-in pages at auth.offerin.app, run by Amazon Cognito, set their own (cognito, XSRF-TOKEN, csrf-state, lang and page-data); its sign-in cookie lasts one hour.

There are no analytics, advertising or tracking cookies. Your browser also keeps a few settings in its own storage, and they are never sent to Offerin. The theme and the layout of the sidebar and panels belong to the browser and stay for whoever uses it next. The settings of your account, such as Saved filters with the status you chose, pinned roles and reminder times, are kept under your account and removed when you sign out, when your session ends and when you delete your account.

9. Why, and what Offerin never does

Your data is used to run Offerin for you: to sign you in, keep your record, work out matches, gaps and eligibility, and write what you ask for. Offerin does not sell your data, shows no advertising and does not train models on your data.

10. How long data is kept

  • Your account and everything in it: until you delete your account.
  • An invitation: when it was used, until the account it made is deleted; when it was never used, until Offerin's operator deletes it, which they do once it is of no more use.
  • Sessions: until you sign out, after 7 days without use, or 30 days after you signed in, whichever comes first. Sessions are never copied into backups.
  • Backups: copies of the database in Amazon S3 are deleted after about 15 days (nightly copies) or about 42 days (Sunday copies); the server keeps its two newest copies, and daily snapshots of its disk are kept for 7 days.
  • Logs: 14 days in the cloud log service; log files on the server for up to 9 weeks.
  • Usage reports: 400 days. Error reports: 90 days. Both are deleted with your account.

11. Seeing, exporting, correcting and deleting your data

Export: in Settings, Data and privacy, “Export JSON” downloads everything Offerin's database holds for your account as one JSON file, table by table, a limited number of times a day. It leaves out only what would be unsafe or is available elsewhere: your tokens' hashes, your session identifiers, the PDF files of resume exports, which you download from the resume itself, and the invitation your account was made with, which is the operator's record (with their note); your address is in the export's account.

Correction: you can change your record in Offerin at any time. To change the email address of an email-and-password account, write to privacy@offerin.app or, when signed in, use Help and feedback.

Deletion: in Settings, Data and privacy, “Delete account” asks you to type your email address and, if you signed in more than 10 minutes ago, to sign in again. It then removes your account and everything it holds from the live database in one step, and deletes your sign-in account at Amazon Cognito within minutes. It cannot be undone. The settings the browser you delete from kept for your account are removed with it; another browser where you were signed in removes them the next time Offerin is opened there. Copies in backups expire within about 42 days and log lines within 9 weeks (section 10). Nothing else is kept: no record of your email address and no trace of the account beyond those expiring copies.

For anything you cannot do in Settings, write to privacy@offerin.app or, when signed in, use Help and feedback from your account's address.

12. Security

Offerin's pages and API are served over HTTPS. Sign-in happens at Amazon Cognito, so your password never reaches Offerin; your session cookie cannot be read by the page's scripts; deleting your account or creating an access token needs a recent sign-in; and every request is limited to your own data.

13. Eligibility information is not advice

What Offerin shows about work authorization, sponsorship, OPT, STEM OPT or E-Verify is information to help you decide, not legal or immigration advice. Confirm what matters with the employer or a qualified advisor.

14. Age

Offerin is not meant for anyone under 16.

15. Changes

Each version of this policy carries a date, and your account records the version you were shown when you signed up. The rules for using Offerin are in the terms of use.