Security & data privacy at Dapols
We keep your data safe and help you avoid sending the wrong data to AI tools. Here's how.
Encrypted authentication
User accounts are managed through Supabase Auth with hashed credentials and OAuth (Google). We never store plaintext passwords.
Row-level security
Every database table that holds user data is protected by Supabase Row-Level Security policies — a user can only read and write their own rows.
Minimal data collection
We collect only what's needed to deliver your plan, process your payment, and keep plans fresh. No selling of personal data.
Guidance on what not to send to AI
Our plans flag which data types (client secrets, regulated PII, health records) should not be sent to consumer AI tools — important for law, accounting, and healthcare.
Connecting your own AI
Personal tokens are shown once and only a one-way fingerprint is stored. Connected apps can read your plan and make a few safe edits inside Dapols. They cannot send, post, publish, spend money, or change billing or your website.
Documents
Uploads go to a private bucket through short-lived signed links. We check what each file really is before reading it, and we limit its size.
A note on regulated industries
If you operate in law, accounting, healthcare, or another regulated field, your obligations for client data may exceed what consumer AI tools safely support. Our templates call this out where relevant, and a custom engagement (quoted and invoiced separately) can scope a setup that keeps sensitive data out of consumer AI. For specific compliance questions, consult a professional in your jurisdiction.