Review everything · Early Access
Each piece waits for your approval. Approval does not publish it.
Security, privacy and control
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
Early Access keeps drafts under your review. Broader autonomy remains a future direction:
Each piece waits for your approval. Approval does not publish it.
Where enabled for your account, Joplin prepares drafts inside the direction you approved.
Broader autonomous execution requires verified provider capabilities and your explicit permission.
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
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.
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.
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.
Security questions deserve a person, not a chatbot loop.