Security
A one-page answer for the agency checklist: where your data and your clients' data live, how they are protected, and what is not in place yet. The data processing agreement holds the full list of measures.
Where data is hosted
The database and file storage run on Supabase in AWS eu-west-1, Ireland.
The worker that builds dashboards runs on Railway in Google Cloud europe-west4, the Netherlands.
The web app's server functions run on Vercel in dub1, Ireland.
Encryption
Data is encrypted in transit with TLS 1.2 or higher, and at rest with AES-256.
Google and Meta access tokens are sealed again with AES-256-GCM before they are stored.
Password-protected share links and report links use signed or hashed tokens. A lost report link cannot be re-issued, only replaced.
Who can reach your data
Row-level security in the database limits every signed-in user to their own records.
Credentials that bypass those rules are held only by server-side components and never reach a browser.
Production access is limited to the founder, and every provider account uses multi-factor authentication.
Google access is limited to the files you pick and to read-only Analytics and Search Console. Nothing in your Google or ad accounts is ever changed.
What the AI sees
OpenAI designs layouts from a description of your columns with a few example labels. Rows from your file are never sent.
AI summaries are written from the totals shown on one page, and every number in them is checked against those totals.
You can switch AI summaries off, and templates lay out a dashboard without AI.
Backups
The database is not backed up automatically yet. We will say so here, and in the data processing agreement, when that changes.
Each dashboard's source file is kept in separate storage, so a dashboard can be rebuilt from its file.
Monitoring
Scheduled jobs and dashboard generation are monitored, and a stopped job raises an alert.
Uptime and incidents are published on our status page.
Found a security issue? Write to support@easydash.app with the details, and please give us a chance to fix it before you publish.