Privacy Policy
Effective 21 November 2026
The short version
- Signing in with Google gives us your name, email address and profile picture. That is all sign-in asks for.
- We ask for one Gmail permission: permission to send email as you. We cannot read your inbox.
- Nothing is sent until you approve a draft and press send.
- We never use Google user data to train AI models, and we never sell it or use it for advertising.
- You can export or delete everything, including the Gmail connection, from Profile at any time.
This policy explains what Inroad ("Inroad", "we", "us") collects when you use the service, why we collect it, who else processes it, and how long we keep it. It covers the website and the application at this domain.
1. Who we are and how to contact us
Inroad is operated by Shrutakirti Chakraborty (founding engineer at Inroad), Kolkata, India, and is the controller of the personal data described here. For any privacy question, request or complaint, email hello@inroadapp.live. We answer requests about access, correction, export and deletion within 30 days.
2. What we collect
Account and sign-in. When you sign in with Google we receive your Google account identifier, email address, name, profile picture URL and whether the address is verified. We store the identifier, your email, name and picture, plus a session so you stay signed in.
Profile and résumé. What you enter or import: name, role, target titles, headline, location, seniority, years of experience, links (GitHub, LinkedIn, X), a writing sample, your signature, tone preference, compensation and work-authorisation preferences, skills, experience, projects and impact stories.
Documents. A résumé or LinkedIn PDF you upload, up to 10 MB. The file is stored in a private bucket and the text is extracted so the product can use it.
Outreach. The companies and funding events we find for you, the people we identify at those companies (name, title, LinkedIn URL, business email), research dossiers, the drafts we generate, the emails we send on your behalf (subject, body, recipient, timestamps, Gmail message and thread IDs), replies you paste into the app, statuses and reminders. If you connect Apollo, we store your Apollo API key encrypted and the usage counters that come back from Apollo.
Usage and diagnostics. Runs, progress events, activity history, token and cost counters, and error records. Server logs contain request metadata (time, route, status) and rotate automatically.
Cookies. We use first-party cookies only, and no advertising or cross-site tracking cookies:
| Cookie | Purpose | Lifetime |
|---|---|---|
| inroad_session | Keeps you signed in. HttpOnly, Secure, SameSite=Lax; the server stores only a hash of its value. | 30 days |
| inroad_csrf | Double-submit token that protects state-changing requests. Readable by the app, not by other sites. | 30 days |
| inroad_oauth_state | Binds the Google sign-in redirect to the browser that started it (login-CSRF defence). HttpOnly. | 10 minutes |
3. Google user data
We request the minimum Google scopes the product needs: three that identify you and one that lets us send mail. We do not request any scope that can read, search, label, delete or modify your mailbox.
| Scope | What it gives us | What we actually do with it |
|---|---|---|
| openid | A stable identifier for your Google account | Match your Google account to your Inroad account so sign-in works |
| Your email address and whether it is verified | Identify your account, show it to you, and use it as the From address when sending | |
| profile | Your name and profile picture | Show your name and avatar in the interface |
| .../auth/gmail.send | Permission to send email as you — nothing else | Send only the messages you have approved, one message at a time |
What we do with Gmail data. When you connect Gmail we store an encrypted refresh token and the address you connected. To send a message we exchange that token for a short-lived access token, submit the message you approved to Gmail's send endpoint, and store the resulting message and thread identifiers so follow-ups you approve are sent in the same Gmail thread. We never read replies; if you want help with one, you paste it into Inroad yourself.
We do not read your mail. The only Gmail permission we hold is permission to send, so we cannot read your inbox, your sent mail or your drafts; we cannot see your labels, contacts or calendar; we do not scan message contents for advertising or profiling; we do not sell or transfer Google user data to anyone for their own purposes; and we do not use Google user data to train, fine-tune or evaluate AI models.
Who can see it. Messages are machine-processed and stored for your account. Inroad staff do not read your email. The administrative view of the product shows usage counts, costs and source configuration, not the contents of messages or documents. If you contact support and choose to paste a message or attach a screenshot, we see only what you send us.
Protection. The Gmail refresh token is encrypted with AES-256-GCM using envelope encryption: each row has its own data key, wrapped by a master key held only in the server environment (never in the database). Access tokens exist in memory only. All traffic is TLS.
Disconnecting. Choose Profile → Disconnect Gmail. We call Google's revocation endpoint, then delete the stored token. You can also revoke access independently at myaccount.google.com/permissions. Deleting your Inroad account revokes the token and deletes it as part of the deletion.
Limited Use. Inroad's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
A scope-by-scope disclosure, written for the Google verification review, is at Google API data disclosure.
4. How we use your information
- Create and secure your account, and keep you signed in.
- Build your profile from what you enter or upload, so the product knows what you are looking for.
- Find companies and people that match your targets, research them, and draft emails in your voice.
- Send the emails you approve, track the outreach state, and prepare follow-ups.
- Enforce plan limits, rate limits and the opt-out list, and prevent abuse.
- Show you your history, usage and costs, and diagnose errors.
- Answer your support requests and meet legal obligations.
Where the GDPR or UK GDPR applies, our legal bases are: performance of our contract with you (the features above), legitimate interests (securing the service, preventing abuse, improving reliability), consent (the Gmail permission, which you can withdraw at any time), and legal obligation.
5. AI processing
Research, drafting and matching use large language models and embeddings through our model providers (listed below). To do that, the relevant text is sent to the provider: excerpts of your profile and résumé, facts about the company and person being researched, your instructions, and the draft being written or revised.
We never use Google user data to train AI models, and we do not permit our model providers to train models on the content we send them. Secrets — your Google refresh token, your Apollo API key and session tokens — are never included in a model request.
6. Who we share it with
We do not sell personal data, do not share it with advertisers or data brokers, and do not use it for cross-context behavioural advertising. We use the following processors, each only for the purpose shown:
| Provider | Service | What it receives |
|---|---|---|
| Neon | Managed PostgreSQL | Account, profile, outreach, draft, message and usage records |
| Upstash | Managed Redis | Job identifiers and rate-limit counters |
| Supabase | Object storage (private bucket) | Uploaded résumé and LinkedIn PDFs, and your data exports |
| Amazon Web Services | Backend compute (EC2) | Processes all API and worker traffic |
| Vercel | Frontend hosting and API proxy | Web requests, including your session cookie |
| Sign-in and Gmail API | Your Google identity, and the messages we send on your behalf | |
| Groq | Language-model inference | Prompt text: profile and résumé excerpts, company facts, draft text |
| NVIDIA (NIM) | Language-model inference and embeddings | The same prompt text, plus text being embedded |
| Tavily | Web search | Search queries about companies and founders |
| Apollo.io | Company and contact data, using your own API key | Company domains and the search filters needed to look up people |
When you connect Apollo with your own key, Apollo processes that data as an independent service under its own terms. We send only the company and role filters needed for the lookup.
We may also disclose information if the law requires it, to respond to a valid legal request, to protect the rights and safety of people, or as part of a merger or acquisition (in which case we will tell you before your data becomes subject to a different policy).
7. Where your data is stored
Our database, queue and file storage are hosted by the providers above in the region chosen when the deployment was created, and our application servers run in the same region where possible. If you use the service from another country, your data may be processed in these locations. Where data leaves the EEA or the UK, transfers rely on the European Commission's Standard Contractual Clauses or an equivalent safeguard offered by the provider.
8. Security
- TLS for all traffic; the session cookie is HttpOnly, Secure and SameSite=Lax.
- State-changing requests carry a CSRF token; session tokens are stored as hashes.
- Google refresh tokens and Apollo keys are encrypted with AES-256-GCM envelope encryption; the master key lives in the server environment, not in the database.
- Uploaded files sit in a private bucket; the API is not reachable directly from the browser.
- Access to production is limited to the operators of the service, and administrative endpoints are restricted to allow-listed accounts.
No system is perfect. If a breach affects your personal data, we will notify you and the relevant authority where the law requires it.
9. How long we keep it
| Data | Retention |
|---|---|
| Account, profile, outreach, drafts, messages and activity | While your account exists. Deleted when you delete your account. |
| Uploaded résumé and LinkedIn PDFs | Until you delete the document or your account. |
| Gmail refresh token | Until you disconnect Gmail or delete your account; revoked at Google either way. |
| Apollo API key | Until you remove it or delete your account. |
| Server logs | Short-lived; container logs rotate at 30 MB each on the backend. |
| Hashed opt-out list | Kept indefinitely, as a hash only, so that people who asked not to be contacted are not contacted again. |
| Backups | Deleted data may remain in a provider's encrypted backups for a short period until those backups are overwritten. |
10. Your choices and rights
- Export. Profile → Export my data produces a ZIP with your records as JSON and your outreach as CSV.
- Delete. Profile → Delete account deletes your records, uploaded files and exports, and revokes the Gmail token. This cannot be undone.
- Disconnect Gmail. Profile → Disconnect Gmail, or revoke at myaccount.google.com/permissions.
- Correct. Most fields are editable in Profile or Resume; anything else can be corrected by emailing us.
- Object or restrict. Email us and we will stop processing the data in question unless we have a legal obligation to keep it.
- Complain. You can complain to your local data-protection authority. We would appreciate the chance to fix it first.
11. Information about the people you contact
Inroad processes business contact information about the founders and operators you choose to reach: names, titles, company domains, LinkedIn URLs and business email addresses. This information comes from Apollo (using your key) and from public sources such as company websites, funding announcements, GitHub and press coverage. Some addresses are inferred from the company's domain pattern rather than verified, and the app tells you when that is the case.
You are responsible for having a lawful basis to contact those people, and for honouring their requests. If someone asks not to be contacted, we add a hash of their address to a do-not-contact list that applies across the product, and we will not send to that address again.
12. Children
Inroad is a professional tool and is not directed at anyone under 18. We do not knowingly collect data from children; if you believe a child has created an account, contact us and we will delete it.
13. Changes to this policy
We will update this page when the product or the law changes, and change the effective date at the top. If a change materially affects how we use Google user data or your personal data, we will tell you in the app or by email before it takes effect.
14. Contact
Privacy questions, access requests and complaints: hello@inroadapp.live. For anything else about the product, see the contact page.