Review everything
Each piece waits for your approval.
Security, privacy and control
Your business. Your accounts. Your rules.
Joplin is built to take on more of your marketing over time — without ever quietly taking more control than you gave it.
Control by design
Approval is a visible policy, not a hidden product decision.
You choose the mode, and you can see it at all times:
Approve the plan
Joplin produces inside the direction you approved.
Run within rules
Your limits, your off-limits topics, and your escalation rules decide what moves.
And wherever a connected account doesn't support or permit an action, Joplin prepares the work as a draft or a handoff. It doesn't find a workaround.
What Joplin can touch
Only what you connect. Only what you permit.
No connection, no access. A connected account with sending disabled means exactly that — Joplin preps the work and waits.
Your money: External spending is blocked by default until you set a limit yourself.
Your pause control: One control stops the weekly marketing workflow and authorized automation for the workspace.
Your record: Approvals, exceptions, and interventions are kept in a durable history — you can always see what happened and who said yes.
Your boundaries: Prohibited-topic controls and escalation rules, set by you.
Your data, technically: Authenticated access through Supabase Auth; business data scoped to its owner with row-level security and server-side ownership checks; integration tokens encrypted server-side with AES-256-GCM; provider-side revocation attempted when you unlink an account where that provider supports it and a revocation endpoint is configured.
When Joplin uses AI
The business context relevant to a task, and the task itself, may be sent to the AI provider configured for that action. Usage is recorded so cost and model activity can be monitored. Practical advice we'd give anyone: don't enter information the marketing task doesn't need.
What we won't claim
We will not claim safeguards or certifications we haven't completed.
Joplin is not currently SOC 2 certified, and it doesn't claim compliance with specialized regulatory regimes unless confirmed separately in writing. As hosting, retention, deletion, and incident-response details are verified, they'll be published here — not before.
Have a question this page didn't answer?
Security questions deserve a person, not a chatbot loop.