Privacy Policy

Who we are

Offerroom is operated by Ritwik Agrawal ("we", "us"). We are the controller of the personal data described here. For any privacy question, or to exercise any right, contact us at hello@offerroom.io. We are a small team, so requests are read and acted on by a person, not a queue.

What we collect, and where it comes from

Almost everything we hold about you, you gave us. The exception is the Network feature, which is covered in its own section below, and which is the only place we obtain information about people from somewhere other than themselves.

• Account identity. Your email address, display name, and the account identifier from Clerk, our sign-in provider. If you chose a persona at onboarding (candidate, student, recruiter, agency, career center), we store that choice.
• Your career material. Your resume, including its contact block: work history, education, achievements, and any document you upload as a source, such as a work sample, a transcript, or a note about your life. We also store the text we split those documents into, and a numeric representation of each piece, so the product can find the relevant part of your history when it writes.
• What you tell Ada. Your own words, including anything you choose to write about salary, circumstances, or why you are leaving. We keep it because the product writes in your voice and cannot do that from a resume alone.
• What you are pursuing. The jobs you track, the job descriptions you paste, the research we generate about a role and company, your notes on each job, and anything you put on your schedule such as an interview or a prep block.
• Contacts you enter. If you add a person to a job you are tracking, we store the name, title, company, email address and LinkedIn address you typed. That is information about another person, which you are choosing to give us.
• Everything the product generates for you. Tailored resumes, cover letters, interview prep, summaries of your career, and the record of which source document each generated claim came from.
• Operational records. A log of the processing steps a generation ran through, a record of each time your material is disclosed to an organization (see below), and a counter used to rate-limit requests. These carry identifiers and outcomes, not your resume text. The disclosure record also stores a scrambled, one-way form of the reader's IP address and browser, which we cannot turn back into either.
• Your acceptance of these documents. When you accept the Terms of Service and this policy, we record which version of each you accepted and when, the network your request came from (the first three parts of an IPv4 address, or the first three groups of an IPv6 address, never the full address) and your browser's description of itself. It is kept for the life of your account as the record of what you agreed to, and it is included when you export your data.

What we do not collect. We take no payment details, because there is no billing in the product yet. We do not ask for, and have no field for, your race, health, religion, politics, union membership, sexual orientation, biometrics or government identifiers. If you write something of that kind into a document or a message, it is stored as part of that document, so please only tell us what you want us to hold.

Why we use it, and our legal basis

• To generate and tailor your application material, and to run your search. Basis: performance of our contract with you (UK and EU GDPR Art. 6(1)(b)). This processing is the service; without it there is no product.
• To find warm introductions, through the Network feature. Basis for your own data: our contract with you. Basis for information about other people: our legitimate interests, and yours, in a real introduction rather than a cold message (Art. 6(1)(f)). We carried out a balancing test and will provide it on request.
• To keep the service working and secure: rate limiting, error reporting, and the step log we use to see why a generation failed. Basis: our legitimate interest in a service that runs and can be debugged.
• To keep records we are required to keep, such as an employer's record of a job requisition. Basis: compliance with a legal obligation (Art. 6(1)(c)).

We do not use your career material to advertise to you, we do not sell it, and we do not use it to train our own models. We have no advertising or cross-context behavioral advertising of any kind.

Automated decisions and profiling

We make no automated decision that produces a legal or similarly significant effect on you. The product drafts text: you read it, change it, and decide whether to send it. Nothing in Offerroom scores, ranks, screens or rejects a candidate, and no employer using Offerroom can ask it to. If that ever changes, this section changes first and we will tell you before it applies to you.

Cookies and analytics, including while you are signed in

The measurement described here runs on every page of Offerroom, including the ones you see after signing in, not only on our marketing pages. We are saying so explicitly because it would be easy to read the rest of this policy as though analytics stopped at the sign-in page. It does not.

Google Analytics sets cookies and creates an identifier for your browser, so we ask first. Until you choose "Accept" on the banner, Google's script is never fetched, no analytics cookie is set, and no identifier for you exists. Choose "Decline", or ignore the banner, and that stays true. We do not use the common setup that loads Google's script for everyone and suppresses only the cookie, because that still tells Google you visited. When you do accept, Google Analytics runs with its advertising signals permanently denied: no remarketing, no advertising cookies, no cross-site tracking.

Google Fonts is a separate request your analytics choice does not control. Our pages load their typefaces from Google, so your browser asks Google for those files whatever you chose above, and Google therefore sees your IP address and the page you are on. Google states it does not use Fonts requests to build advertising profiles, and it sets no cookie doing this. We mention it here, next to the choice, rather than in a footnote, because the paragraph above would otherwise read as though declining stopped every request to Google.

Vercel Web Analytics and Speed Insights run without asking, on every page, because they set no cookie, keep no identifier, store no IP address and build no profile of you. Declining analytics does not turn these off, and we would rather say that than let the paragraph above imply otherwise.

What the events say. They describe actions, not people: which call-to-action opened the waitlist form and the role and country bracket a signup chose, that a signup completed, that an invite code was redeemed, which onboarding step was reached, and that a document was generated, of which kind and how long it took. That last one is the measurement that runs while you are signed in, and it is the whole of it: we record that a resume or a letter was produced, never a word of what it said. We never send your name, your email address, your resume, your documents, or anything you write to Ada to any analytics provider. Nothing in your career material is measured.

To change your mind later, clear this site's data in your browser and the banner will ask again.

Who we share it with

We do not sell your personal information and we do not share it for cross-context behavioral advertising. We use service providers who process data on our behalf, under contract and on our instructions:

• Clerk, our sign-in provider: your email address, account id and session. No resume or job-description content.
• Supabase, our database host, which holds everything the product stores. Your data is stored in Japan (Tokyo region).
• Vercel, which hosts the application, and Modal, which runs the background worker that generates your documents. Every request passes through them, so resume and job-description text transits both.
• OpenRouter, which routes each generation to a language-model provider. This is the heaviest flow: prompts carry your resume text, the job description, your career memory and your own words. OpenRouter forwards each call to the upstream model provider we select, so those providers receive it too.
• Village, our relationship provider, only if you use Network and only what that section describes.
• Google, as our website-analytics provider, and only if you accept analytics cookies. It receives the page you are on, your IP address and a cookie identifier for your browser. It never receives your name, your email address, your resume, or anything you write to Offerroom. Google processes this in the United States under the Standard Contractual Clauses and the EU-US Data Privacy Framework. Our pages also load their typefaces from Google Fonts, which happens whatever you choose about analytics, and means Google sees your IP address and the page you are on.
• Vercel Web Analytics and Speed Insights, which count page views and measure loading speed. They set no cookie, store no IP address and build no profile, so they identify nobody and run without asking you.
• Sentry, our error reporter, and only when an error occurs. We strip request bodies, cookies, authorization headers and local variables before sending, so an error report carries the failure and the identifiers, not your documents.

We may also disclose information if the law requires it, or to protect our rights, safety or property. We will say so in this policy before we add a provider that receives a new category of your data.

Being straight about contracts. Data protection law expects a signed processor agreement with each of these providers. We are working through them and not all are signed yet. We would rather tell you that than imply a paperwork position we do not hold.

People in your network who are not Offerroom users

This section is also our notice to those people, under Art. 14 of the UK and EU GDPR. We hold no way of contacting them, so we publish it here instead, which Art. 14(5)(b) allows.

If you use Get introduced, you can connect your LinkedIn, email and calendar accounts. We pass that connection to our relationship provider, Village, which works out who in your network can reach a company or a person you are pursuing, and how strong that route is. Doing this necessarily involves information about other people, including people who do not have an Offerroom account.

What we hold about them. For a person on a route to a company or person you added, we store their name, job title, employer, public professional headline, profile photo and LinkedIn profile URL, along with the provider's explanation of why the route is a real one (for example "you both worked at Acme"). That is all. We do not store their email address, their phone number, the contents or subjects of your messages with them, your calendar entries, or how often or how recently you were in touch. We do not build a profile of them, we do not score them as a person, and we make no automated decisions about them.

Who is included. Only people on a route to a company or a person you chose to pursue. Connecting your accounts does not create an Offerroom copy of your address book.

How long. We stop using it after 30 days, and we delete it. After 30 days we do not show it to you or act on it, and a scheduled pass deletes it once a day whether or not you come back; if you use the feature again before that pass runs, the request itself deletes it and looks it up again. If you disconnect your network, we delete all of it immediately.

Our lawful basis. Legitimate interest (Art. 6(1)(f)): our interest, and yours, in finding a real introduction rather than sending a cold message to a stranger. Our balancing test considers that this information is professional and largely published by the person themselves, that we hold no way of contacting them, and that nobody is contacted by us: no message is sent to anyone without you approving its exact wording first. We can provide the assessment on request.

If you are one of those people. You can ask us what we hold about you, ask us to correct it, object to it being held, or ask us to delete it, by emailing hello@offerroom.io. We will act on an objection or deletion request and we do not need you to hold an account to do so. We handle these by hand today, so tell us the name and, if you can, the LinkedIn profile you are asking about, and expect us to come back to you inside the time the law allows rather than instantly. Because the underlying relationship graph is built and held by Village rather than by us, a request to delete it at source should also go to Village; tell us and we will point you at their process.

Sending anything. We draft introduction requests for you, but we never send one. Nothing leaves Offerroom until you have read the exact message and approved it, and no message is ever sent by us on your behalf without that step.

If your school, employer or agency uses Offerroom

Offerroom keeps organizations and individuals apart on purpose. Your career material lives in a workspace of your own, and a university, employer or agency workspace is a separate one. A school or a company does not get your resume because you share an institution with them.

An organization workspace holds its own records: who its members are and their role, for a school which students are affiliated with it, for an employer its job requisitions and who is staffed on them, and for an agency which clients it works for.

Nothing of yours reaches an organization unless you grant it, and today nothing in the product creates such a grant at all. The mechanism is built into our database, not yet into any screen: there is no button anywhere in Offerroom that shares your material with a school, an employer or an agency, and none that revokes one, because nothing can be shared yet. We are describing the design because it is what will govern sharing when it arrives, and because you should be able to read it before it does.

When it does arrive, a grant will be to one named organization, for one named scope, with an expiry, and revocable. A revoked or expired grant stops working immediately: the database itself stops returning your rows, rather than a screen hiding them. The design allows a grant to cover your profile or a snapshot of your resume and nothing else: your uploaded documents, your notes, your messages to Ada and your job list are outside it entirely. The record of a grant is kept after you revoke it, so that both of us can see what was agreed and when.

We keep a record of every time your material is disclosed. Who read it, whose it was, what they read, when, and the grant that allowed it. The record cannot be edited or deleted by the person who made the disclosure, and it is not destroyed if an account is erased: the people are detached from it instead, so the history survives. This is the FERPA 34 CFR 99.32 record for students and our accountability record for everyone else.

Asking what that record says is still an email, not a screen. The record is kept and it is yours to see, but the page that would show it to you is not built yet. Until it is, email hello@offerroom.io and we will tell you what it holds about you.

US students. If your school uses Offerroom, FERPA (20 U.S.C. 1232g, 34 CFR Part 99) applies to student records that reach it. Identified information about you reaches your school only through a grant you made, as above, and every such disclosure goes in the record described above. As it stands no part of the product performs that kind of read at all: the permission exists, the audit trail is in place ahead of it, and no screen yet asks for another person's material.

Employers. An employer using Offerroom is the controller of its own hiring records and we are its processor for them. A job requisition carries a retention clock of one or two years from the date it closes, because US equal-employment recordkeeping rules (29 CFR 1602.14) require the record to be kept. Because that record must be kept, an employer cannot delete a requisition in the product.

Where your data is stored, and international transfers

Your data is stored in Japan, in our database host's Tokyo region. If you are in the European Economic Area or the United Kingdom, Japan is recognized by the European Commission as providing an adequate level of data protection, so a transfer there is permitted on that basis.

Several of the other providers listed above process data in the United States, in particular our sign-in provider, our error reporter, and the language-model providers that generate your documents. Where personal data leaves the UK or the European Economic Area for them, we rely on the Standard Contractual Clauses or on an adequacy decision. We are still confirming the exact processing region with several of them, and we will name each one here once it is confirmed rather than state one we have not verified. If that matters to you before you upload anything, email hello@offerroom.io and we will tell you where the position stands.

How long we keep it

The short version: we keep your career material for as long as your account exists, because that is what it is for, and we delete it when you ask. The detailed schedule, table by table, is a document we maintain alongside the code.

• Your resume, documents, memory, letters and job history: for the life of your account. You can delete an individual document, job or calendar item in the product at any time, and it is removed.
• Third-party contact data from Network: 30 days, as described above.
• Employer job requisitions: one or two years from closing, as the law requires, then deleted by the same daily pass; longer if the employer has placed a legal hold on it.
• A sharing grant: it stops working when it expires or you revoke it, and the record that you made it is kept, as the evidence of what you agreed to.
• The processing step log: kept, because it is how we can show what happened, including that a notice was acknowledged before anything was ingested.
• The record of disclosures to an organization: kept, and deliberately not deleted when an account is. Erasing someone removes them from the record rather than removing the record, because a log of who looked at your material is worth nothing if it can be made to disappear.
• Rate-limiting counters: deleted by the same daily pass once they are more than an hour old.

Deleting your account. You can delete your whole account yourself in Settings. The request is recorded at once, you are signed out, and the deletion runs within 24 hours; you can also ask at hello@offerroom.io. The clocks above that run on a schedule, the 30-day Network window, the requisition clock and the rate-limit counters, all run once a day from a single pass; everything else in this section is either kept deliberately or deleted when you delete it.

Your rights

Depending on where you live, you have some or all of these rights over your personal data:

• access a copy of what we hold, and be told how we use it;
• be told who your material has been disclosed to, and when;
• correct information that is wrong or out of date;
• delete your information;
• restrict or object to certain uses, including our legitimate-interest uses;
• receive your information in a portable, machine-readable format;
• withdraw consent where we relied on it;
• and not be treated differently for exercising any of these.

How to exercise them, honestly. Inside the product you can edit and delete individual items yourself: an uploaded document, a job you are tracking, a calendar entry, a career-timeline entry, and a Network target, and you can disconnect Network entirely, which erases everything it holds. In Settings you can export a full copy of your data and delete your whole account. Everything else, including correction of something you cannot edit, and any objection or restriction, is done by emailing hello@offerroom.io, because we have not yet built the endpoints that would do it automatically. A request by email is just as valid, and we act on it within the time the law allows: one month under the GDPR, 45 days under the CCPA. We will tell you when it is done.

California. Under the CCPA as amended by the CPRA you have the rights to know, to delete, to correct, to know what is disclosed, and to opt out of the "sale" or "sharing" of your personal information and of profiling for it. We do not sell or share your personal information and we do not profile you for advertising, so there is nothing to opt out of and we have no "Do Not Sell or Share My Personal Information" mechanism to offer. We do not use or disclose sensitive personal information for any purpose beyond providing the service, so the right to limit its use does not arise. We will not discriminate against you for exercising a right, and you may use an authorized agent.

UK and EEA. Where we rely on legitimate interests, you can object, and we will stop unless we can show compelling grounds that override your interests. You can also complain to your data-protection authority, and to the ICO if you are in the UK.

India. The Digital Personal Data Protection Act, 2023 gives you rights to access, correct and erase your data, to nominate someone to exercise your rights, and to grievance redressal. Email hello@offerroom.io to exercise them.

Children

Offerroom is for adults and is not directed to children. We do not knowingly collect information from anyone under 16. If you believe a child has given us their information, contact us and we will delete it.

How we protect your information

Your data is separated at the database level: every table holding your material carries a row-level policy so that a workspace can only read its own rows, enforced by the database rather than by application code remembering to filter, and the application runs under a restricted role that is granted nothing on the account tables. Data is encrypted in transit. Error reports are stripped of request bodies, cookies and credentials before they leave. No method of storage or transmission is completely secure, so we cannot guarantee absolute security, and if a breach affects you we will tell you and the relevant authority as the law requires.

Changes to this policy

When we change this policy we change the version at the top. A change that affects how we use your data will be told to you before it takes effect, not slipped into a version bump. This policy is maintained in the same place as the code it describes, and a sentence here that stops being true of the software is treated as a bug.

Contact and complaints

Questions, requests, or complaints: hello@offerroom.io. If you are in the EEA or the UK, you also have the right to complain to your local data-protection authority. If you are in California, you may contact the California Privacy Protection Agency or the California Attorney General. If you are in India, you may raise a complaint with the Data Protection Board of India.