Security
Your accounts stay yours.
Every protection on this page is enforced by the code, not just promised.
Your connected accounts
No platform password reaches us
You connect each platform through its own official sign-in. We can post for you, and nothing more.
Encrypted keys
The keys to your connected accounts are encrypted before they’re stored, and the encryption key is kept apart from the database.
Keys never come back out
No page or API returns a stored key. A test fails the build if one ever does.
Safe by default
If the encryption key is ever missing, Dripost refuses to store or read any account key rather than use a weaker one.
Keys we can replace
We can replace the encryption key at any time without disconnecting you: stored keys move to the new one in the background.
Your sign-in
Two-factor sign-in and passkeys
Add an authenticator app or a passkey in Settings.
See every session
Settings lists where you’re signed in. End any session, or all the others, in one click.
New sign-in alerts
If your account is used from a new browser, device or country, we email you straight away.
Confirm it’s you
Changing a password or recovery address, exporting your data or deleting your account asks for a fresh emailed code first.
Guess-proof codes
Sign-in codes expire quickly and work once; repeated wrong tries are slowed and locked out.
What goes out
Nothing unapproved
With approvals on, an unapproved post can’t go out. It’s checked on the server, not just hidden on screen.
Five roles that restrict
Owner, admin, editor, approver and viewer, checked on the server for every change.
Each post goes out once
When we can’t tell whether a post landed, we ask you instead of sending it again.
Pause everything
Stop one scheduled post, or pause your whole workspace. When you switch it back on, we ask about anything that came due instead of sending a backlog.
An audit log
Owners and admins see sensitive workspace actions, with who and when.
Apps and AI assistants
Drafts only, unless you say
A new API key or connected app can only write drafts. Scheduling and publishing are a separate choice you tick.
Posting now needs a person
An app can ask to publish this minute, but a person approves it on Dripost first.
A 10-minute hold
Anything an app writes or changes waits at least 10 minutes before it can go out, so you can cancel it.
Keys that expire
API keys last 30 to 365 days (90 by default) and connected apps 90 days. We email you a week before.
Limited on the first sign of trouble
If an app behaves unlike itself or writes text that looks like an attack, it drops to drafts only at once, what it scheduled goes back to drafts, and the owner gets an email.
Undo what an app did
Undo everything a key or app did since a time you pick. Live posts on Facebook can be removed too; for other platforms we give you the link.
One switch for all of them
The workspace owner can revoke every API key and connected app in one step.
Your data
Walled off
Every request for a post, file or delivery is checked against your workspace. Asking for someone else’s returns “not found”.
Private files, short-lived links
Media sits in private storage. A platform fetches it through a link that works for one file, for 15 minutes.
An emergency switch
If something goes wrong, we can stop all publishing, or make the product read-only, in seconds. Nothing scheduled is lost.
Leave with everything
Download your data or delete your account in Settings, any time.
Questions
Where does Dripost run?
On Cloudflare, with the database on Cloudflare D1 and files in private Cloudflare R2 storage.
How do I report a security problem?
Email us with “security” in the subject. The security policy says what we ask, and what we do in return.
Is Dripost certified, for example SOC 2 or ISO 27001?
No. Dripost hasn’t had an independent audit. This page lists what the code enforces today.