Where your data lives and who can see it
A plain account of how Digital Arrow stores and protects the data you put into it: hosting, the providers that process it, how access is limited, and the tools you have to keep or delete it.
Sub-processors, reviewed 2026-11-11
| Provider | What it does for Digital Arrow | Data it receives |
|---|---|---|
| Railway | Hosting in the EU for the application, the database, background job queues and file storage. | All workspace data, including candidate and employee records and uploaded files. |
| Stripe | Payments, subscriptions and billing for Digital Arrow plans. | Billing contact, plan and payment details. Card data goes to Stripe directly. |
| OpenAI | AI features: CV parsing, CV review, match scoring refinement and question generation.Only when an AI feature is used. | The text each AI feature processes, such as CV text, job details or onboarding material. |
| SendGrid (Twilio) | Transactional email such as sign-up confirmation, password reset, invitations and job emails. | Recipient name and email address and the message content. |
| Sentry | Error monitoring for the website and the application. | Technical error reports, which can include request details such as the IP address of the user who hit the error. |
| Google (Calendar) | Reading busy times and creating interview events.Only for users who connect a Google calendar. | Busy/free times and the interview events Digital Arrow creates. |
| Microsoft (Outlook calendar) | Reading busy times and creating interview events.Only for users who connect an Outlook calendar. | Busy/free times and the interview events Digital Arrow creates. |
If you connect your own mailbox (SMTP and IMAP), candidate email is sent and received through your mail provider, not ours.
How it works today
Hosted in the EU
The application, its PostgreSQL database and uploaded files (CVs, documents, videos) are hosted on Railway in the EU. Files are kept in S3-compatible object storage that runs on Railway alongside the application.
Encrypted in transit
The website and the API are served over HTTPS only, with HTTP Strict Transport Security turned on.
Secrets encrypted at rest
Calendar tokens, connected mailbox passwords, webhook signing secrets and MCP server credentials are encrypted with AES-256-GCM before they are saved.
Keys stored as hashes
API keys and MCP tokens are shown once when you create them. We keep only a hash, so a lost key can't be read back, only revoked.
One company, one workspace
Every job, applicant, contract, timesheet and invoice belongs to one company. Requests are checked against the company you are signed in to, and a company's talent pool is visible only to its own managers.
Roles and permissions
Managers have full company access. Employees see only their own timesheet and time-off tools. API keys carry only the scopes you tick, and MCP tokens act with your own role.
Retention, consent and erasure
Each workspace can set retention policies, preview which candidate records a policy would remove, and run it. Retention is measured from a candidate's last activity, not from when they first applied. Consent given on the application form is stored with the record and can be revoked. You can export everything held about a candidate, or erase them; each erasure leaves a record, so you can later confirm that a named person's data was removed without keeping that data.
History you can check
Moves between pipeline stages are recorded with the stage name and time. Contracts show each signer's status and when they signed. Webhook deliveries are logged with each attempt, so you can see what was sent and whether it arrived.
Payments
Card details are entered on Stripe's checkout page and go to Stripe directly. Digital Arrow never sees or stores full card numbers.
What we don't offer yet
No single sign-on (SSO) or SAML. No custom permission sets beyond the Manager and Employee roles. We don't publish third-party security certifications.
Frequently asked questions
Where is my data stored?
The application, its PostgreSQL database and uploaded files (CVs, documents, videos) are hosted on Railway in the EU. Files are kept in S3-compatible object storage that runs on Railway alongside the application. Payments are handled by Stripe, and AI features send the text they process to OpenAI.
Do you support SSO or SAML?
Not yet. Members sign in with their own Digital Arrow account.
Can I get a data processing agreement?
Yes. Email support@digital-arrow.agency and we will send one.
How do I report a security issue?
Email support@digital-arrow.agency with the details. Please don't share the issue publicly until we have replied.
Related
Read the privacy policy
Questions about security or data handling? Email support@digital-arrow.agency.