Security and data handling
LinkRobin holds two sensitive things: the keys to your data providers and access to the mailbox you send from. This page explains how both are handled.
The short version
Provider keys and mailbox tokens are stored server side and are never sent to your browser. Every row of workspace data is protected by row level security, so one workspace cannot read another's sites, prospects, messages or reports.
Credentials and tokens
- Provider keys you add in Settings are written server side and used only inside server requests.
- Mailbox access uses OAuth with Gmail or Outlook. LinkRobin stores the tokens server side and never exposes them to the client.
- Keys and tokens are never written into logs, reports or exports.
- You can disconnect a mailbox or remove a provider key at any time from Settings.
Access control
Data is scoped to a workspace. Membership decides access, and only existing owners and admins can add members. Public share links for reports and link proof are read only, unguessable, and expose just the campaign or placement they were created for.
What we send on your behalf
Outreach is sent from your own connected mailbox, after you approve the message. Daily sending limits are set by you. LinkRobin does not send from shared infrastructure, so your sender reputation stays yours.
Transport and hosting
- All traffic is served over HTTPS.
- Application data is stored in a managed Postgres database with row level security enabled on every table.
- Server side logic runs in a managed serverless runtime; secrets are injected at request time rather than bundled.
Reporting a vulnerability
Write to security@linkrobin.app with steps to reproduce. We will confirm receipt, keep you updated while we investigate, and credit you if you would like that. Please do not test against other people's workspaces or data.