Trust
Security
You're trusting Paperplane with your clients' ad accounts. Here's how we protect that access.
- Nothing reaches Meta until you review it and press Post.
- Meta access tokens are encrypted, and only our background workers ever use them.
- Every workspace is isolated at the database level.
- Our staff can never sign in as you.
1. Connecting to Meta
- We connect only through Meta’s official Marketing API and Facebook Login for Business. We don’t scrape, use browser extensions or ask for passwords.
- You choose which business assets to authorize, and you can revoke access from Meta or Paperplane at any time.
- We request only the permissions the features you use need.
2. Token protection
- Meta access tokens are envelope-encrypted with AES-256-GCM. The keys that protect them are held in a managed key-management service, separate from the database.
- Tokens are stored in an isolated vault that isn’t exposed through our web API. Only our background job workers decrypt them, in memory, while a sync or publish runs.
- Tokens are never sent to a browser, written to logs or included in error reports.
3. Workspace isolation & access control
- Each customer’s data lives in its own workspace, and row-level security in the database enforces that boundary on every query.
- Roles (owner, admin, manager, buyer, viewer, billing) and per-account grants control who can view, edit or publish.
- Optional authenticator-app two-factor authentication, and a sign-in history owners and admins can review.
4. Safe changes
- Edits stay drafts until someone with publishing rights reviews the full set of changes and posts it.
- Every published change is recorded in an append-only audit log, by person and time. Nobody can edit or erase it, including us.
- Publishing respects Meta’s rate limits and backs off automatically.
5. Staff access
There is no way for Paperplane staff to act as a customer. When support needs to see what you see, they open a read-only, time-limited support view. It can’t publish, see your credentials or touch your tokens, and every one is recorded in your workspace’s audit log.
6. Infrastructure & operations
- Data is encrypted in transit (TLS) and at rest by our hosting and database providers.
- Error monitoring scrubs tokens, secrets and personal data before any report leaves our systems.
- We use a small set of vetted service providers, listed in our Privacy Policy.
- Every change is checked in continuous integration before it ships: type checks, automated tests and database access-policy tests.
7. Report a vulnerability
If you think you’ve found a security issue, please email phueledmedia@gmail.com with the details and steps to reproduce. We’ll acknowledge it promptly, keep you updated, and won’t take legal action against good-faith research that avoids privacy violations, data destruction and service disruption. Please give us reasonable time to fix the issue before telling anyone else.
8. Incident response
If a security incident affects your data, we’ll notify affected customers and, where required, regulators and Meta, without undue delay. We’ll tell you what happened, what data was involved and what we’re doing about it.