Security
Your support inbox holds your most sensitive customer data.
Identity documents, payment disputes, account recovery: it all passes through support first. This page says exactly how that data is handled, including the parts most vendors leave vague.
- TLS in transit
- AES-256-GCM for secrets
- bcrypt cost 12
- Two-factor sign-in
- Per-workspace isolation
- Encrypted backups
Protection
Protection built in, none of it optional.
In transit
All traffic to theagacrm.com runs over TLS 1.2 or newer, and so do our connections to the providers we use. Connections to your own mailbox are encrypted whenever your mail server supports it.
At rest
Mailbox passwords and tokens, payment keys and two-factor keys are sealed with AES-256-GCM before they reach the database. Passwords are bcrypt-hashed at cost 12 and never stored in a form anyone can reverse, us included. Backups are encrypted before they leave the server, with the key kept offline.
In the application
Every query is scoped to a single workspace, so one tenant’s data is unreachable from another’s session. Sign-in, sign-up and other sensitive forms are protected by a bot check and limits on repeated attempts.
Files and email
Every uploaded file and email attachment is scanned for viruses before anyone can open it, and dangerous files are blocked or quarantined. Incoming email is shown as plain text, so scripts hidden in an email cannot run.
Backups
Encrypted backups every hour, held in three places for 30 days. Restoring from them has been tested end to end.
Monitoring
Systems are watched around the clock for outages, errors and signs of intrusion, with alerts to on-call staff at any hour. Administrator access to the servers uses key-based sign-in only.
Access
Who can do what, decided by you.
Support teams are not flat. The people who can read a KYC document are rarely the people who should be able to export the customer list.
- A permission matrix, not fixed tiers
- 8 roles across 7 actions (view, edit, assign, escalate, close, export and manage), edited as a grid per workspace. A Finance specialist can see the tickets they need without being able to export your customer base.
- The owner role cannot be edited away
- Workspace Admin permissions are fixed at the full set, so a misconfigured matrix can never lock every administrator out of the workspace.
- Two-factor authentication
- Time-based codes from any authenticator app, with one-time recovery codes. Required for every workspace owner; each owner decides whether the rest of the team must use it.
- Sessions you can end
- Idle sign-out after 30 minutes by default, with a 60-second warning first. Active sessions are listed per user and can be revoked individually. Useful the day a laptop goes missing.
- Password rules you set
- A minimum length of 10 characters by default, raised as high as your policy requires.
Accountability
Nothing happens without a record.
Every change is written to an audit log with who did it, what changed, and when, ticket edits, assignments, logins, exports and uploads. Managers can filter it, and it is there for your auditors without anyone having to reconstruct a story afterwards.
Sign-ins, permission changes and any view of a customer’s contact details are kept for 365 days and cannot be shortened, even by an administrator. Ordinary activity follows a retention window your workspace sets, and high-volume automated entries a shorter one, so the trail that matters survives while the machine chatter does not.
It records the decisions the system makes on its own, too. When triage judges an incoming email not to be a support request, that message stays in your inbox and the reason is logged, so “why didn’t this become a ticket?” always has an answer.
Third parties
Everyone who ever touches your data.
The complete list, what each one is in law for the data it gets, and the condition under which it sees anything at all. Most never activate unless you turn the matching feature on. Not all of them are our subprocessors: a payment provider is its own controller for fraud and regulatory checks, and a mailbox or channel you connect stays your own provider — so the table says which is which rather than flattening all three into one word.
| Service | Role | Entity | What it handles | When it applies | Where |
|---|---|---|---|---|---|
| Hostinger | Our processor | Hostinger International Ltd (Lithuania) | Runs the application and stores the database, the attachment files and the backups. Also relays the platform’s own transactional email — sign-in, billing and system notices. | Always. This is where AGA CRM lives. | Servers in the United Kingdom. |
| Cloudflare | Our processor | Cloudflare, Inc. (United States) | Runs the bot check (Turnstile) on sign-in, sign-up, contact and other sensitive forms, which sees the visitor’s IP address and browser details. Also stores the encrypted backups, which it cannot read. | Always: forms are checked for every visitor, and backups are copied every hour. | Global network; backups held in Cloudflare R2 storage. |
| Google (Gmail API) | Your providerThe mailbox is yours and so is the Google agreement covering it. We read and send through it on your instruction. | Google Ireland Ltd / Google LLC | Reads incoming support mail and sends the replies your agents write. | Only when a Gmail or Google Workspace mailbox is connected. | EU and United States. |
| Your own mail host | Your provider | Whichever provider you choose | The same job over IMAP and SMTP for Hostinger, Outlook, Zoho or any other host. | Only when you connect a non-Google mailbox. You pick this one, and it stays your contract, not ours. | Wherever your provider operates. |
| Anthropic (Claude) | Our processor | Anthropic PBC (United States) | Receives ticket conversations to suggest a summary, a reply, a category and sentiment (new messages are analysed automatically while AI is on), and website chat messages for the chat assistant. Names, ticket subjects and orders from your records are held back unless you share them. Nothing is used to train a model, and Anthropic deletes API data within 30 days. | Only while AI is switched on, which is off until a workspace owner turns it on. It can be switched off at any time. | United States. |
| Twilio | Our processorOur processor for carrying the call. Like any carrier it also has its own regulatory records of connecting it, which are not ours to instruct. | Twilio Inc. (United States) / Twilio Ireland Ltd | Carries inbound and outbound calls. Call recording and transcription are currently switched off for all workspaces. | Only when your team places or receives a call through the CRM. | EU and United States. |
| Meta | Your providerYou connect the account, under Meta’s terms with you. Meta is its own controller for what it does with platform data, which no term of ours reaches. | Meta Platforms Ireland Ltd | Delivers WhatsApp, Messenger and Instagram conversations into tickets, and sends your replies back. | Only when one of those channels is connected to your workspace. | EU and United States. |
| Telegram | Your providerYour bot, under Telegram’s terms with you; Telegram is its own controller. | Telegram Messenger Inc. | Delivers Telegram conversations into tickets and sends your replies back. | Only when a Telegram bot is connected to your workspace. | Outside the EEA and the UK. |
| Stripe | Independent controllerOur processor for taking the payment, and its own controller for fraud screening, anti-money-laundering checks and the records its regulators require. We cannot instruct it out of those, and its own privacy notice governs them. | Stripe Payments Europe Ltd / Stripe Inc. | Takes the subscription payment and stores the card. It receives the billing contact and the amount — never a ticket, a customer record or an attachment. | Only on the billing path, when you pay by card. | EU and United States. |
| Flutterwave | Independent controllerThe same split as Stripe: our processor for the payment, its own controller for fraud, AML and regulatory records. | Flutterwave Inc. / Flutterwave Technology Solutions Ltd (Nigeria) | The alternative payment route, for the same purpose and the same fields as Stripe. | Only on the billing path, and only if you choose it at checkout. | Nigeria and United States. |
This same list is annexed to our Data Processing Agreement, which binds each of these parties to terms no weaker than our own and commits us to 30 days’ notice before a new one starts processing. AGA CRM’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is never used for advertising and never sold.
Your controls
Switches that are actually yours to flip.
Turn AI off
AI is off until an owner turns it on, and one switch turns it off again. Details from your records are not shared with the AI unless you choose to, and nothing is sent to a customer without an agent.
Revoke mailbox access
Disconnect from the CRM, or from your Google account directly. Either one stops the sync immediately.
Export everything
Export a customer’s full record, your customer list, tickets and reports at any time, including when the workspace is read-only.
Delete it yourself
Erase a single customer completely, or delete the whole workspace from Settings: it closes at once and is removed permanently after 7 days.
Running a security review on us?
Send the questionnaire. We answer it ourselves, and we say so when the answer is no. Found a security problem? Email info@theagacrm.com.
