Plain answers about your data.
What we store, where it lives, who can see it, and who helps us run the service. Security questions and reports go to security@proofsource.co, and a person replies.
The five questions we get most.
Where is my data stored?
In the United States, on Amazon Web Services.
Is it encrypted?
Yes, in transit and at rest. Credentials for tools you connect are encrypted again before they are stored.
Can other customers see it?
No. Each organization's data is kept separate in the database, and only members of your workspace can see it.
Do you change anything in my accounts?
Not without you. Google connections are read-only. A fix is published to WordPress only after you preview and confirm it.
Do you hold SOC 2 or ISO 27001?
Not today. We would rather say so than imply it. Ask us anything a questionnaire would.
How the service handles data.
What we store
What we store
Encryption and isolation
Encryption and isolation
Read-only connections
Read-only connections
Signing in
Signing in
This website
This website
Availability
Availability
Export and deletion
Export and deletion
Site connections.
What happens when you connect your website so Proofsource can publish the fixes you approve.
| How is my site login stored? | Your WordPress application password and your Webflow or Shopify key are encrypted with AES-256-GCM before they are written to our database. The encryption key lives in AWS Secrets Manager, not in the database. |
|---|---|
| Can Proofsource publish without me? | No. You see a preview of each post and approve it first. We publish only the version you approved; if anything changed since your preview, we ask you to look again. |
| Can I undo a post? | Yes. Rolling back moves a WordPress post to the WordPress trash, unpublishes a Webflow item, or hides a Shopify article. Each stays on your site, so you can restore it. |
| How do I take access away? | Disconnect the site in Proofsource and we delete the stored password or key; posts already published stay on your site. You can also revoke access on your side at any time: in WordPress under Users, then Profile, or in your Webflow or Shopify app settings. |
| Do Search Console and Cloudflare change anything? | No. Both connect read-only. If you later approve a change on your Cloudflare zone, Cloudflare asks you for write access then, on a separate consent screen. |
Who helps us run the service.
Each provider gets only what its job needs. We do not sell personal data or share it with advertisers.
| Provider | What it does for us | Where |
|---|---|---|
| Amazon Web Services | Runs the app and its database, keeps backups, and runs some AI models through Amazon Bedrock. | United States (us-east-1). Amazon Bedrock may process an AI request in another AWS region through cross-region inference. |
| Cloudflare | Carries all traffic to the app and its API, and serves this website. | Worldwide edge network. |
| OpenAI | Answers your tracked prompts as ChatGPT, runs the assistant and content drafts, and transcribes cited videos. | United States. |
| Anthropic | Answers your tracked prompts as Claude, and is a backup for our analysis models. | United States. |
| Perplexity | Answers your tracked prompts as Perplexity. | United States. |
| Google Gemini | Answers your tracked prompts as Gemini, only on plans that add it. | Google data centers, worldwide. |
| Google Maps Platform | Reads your Google Maps listing when you start from a Google Maps link, and draws the maps in the app. | Google data centers, worldwide. |
| YouTube | Reads your YouTube channel when you start from a YouTube link, and finds channels you are compared with. | Google data centers, worldwide. |
| xAI | Answers your tracked prompts as Grok, only on plans that add it. | United States. |
| TypeSafe | Grades captured answers with its Jev model: intent, claim accuracy and stance. | United States. |
| DataForSEO | Fetches Google AI Overviews, logged-out ChatGPT answers, search results and keyword volumes, and, when you start from an app or Google Maps link, app store listings and Google business listings for you and your competitors. | Estonia (EU) and Ukraine. |
| Firecrawl | Reads public web pages our own crawler cannot (cited pages, your site, competitor pages), takes screenshots of cited pages and your homepage, searches the web for new pages about your category, and watches competitor pages for changes. When an agency searches for new leads, it looks up companies, the people at them and their work emails through its data providers. | United States. |
| TinyFish | Reads public web pages and Google AI Overviews in a real browser. | United States. |
| Xpoz | Searches public Reddit posts and comments that name your brand. | Not published by Xpoz. Its terms follow Israeli law. |
| Fast Mail Tracker | Sends an agency member's pitch emails from their own connected mailbox and tells us when a prospect replies. | United States. |
| Resend | Sends our emails: sign-in codes, results, alerts, and service and billing notices. | United States. |
| Knock | Delivers in-app notifications, and Slack notifications you set up. | United States. |
| Slack | Our own team's workspace: service alerts, and messages sent through our contact, demo and support forms. | United States. |
| Pagerless | Alerts our own team when the app, its API or a scheduled job fails. | Cloudflare's worldwide network. Pagerless publishes no single processing location. |
| Stripe | Merchant of record through its Link service ("Sold through Link"): bills you and handles sales tax. Card and bank details go to Stripe, not to us. | United States. |
| Dodo Payments | Standby merchant of record: bills you and handles sales tax. Card and bank details go to Dodo Payments, not to us. | United States and other countries. |
| PostHog | Website analytics, including approximate visitor location, and anonymous quality counts from the app. | United States. |
| Meta | Measures which of our ads lead to sign-ups, free trials and first payments. Nothing is sent for visitors who decline cookies or send a Global Privacy Control or Do Not Track signal. | United States. |
The data each one receives is on the subprocessors page. Tools you connect, such as Google or your own Slack, receive data because you asked us to send it. Questions about this list go to privacy@proofsource.co.
Found a vulnerability? Tell us first.
Email security@proofsource.co with the steps to reproduce. Please do not access other customers' data, run denial-of-service tests or send us personal data you found. We reply, fix, and tell you when it is fixed.
- Security reports and questions
- security@proofsource.co
- Privacy and data requests
- privacy@proofsource.co