Where is my data stored, and who does PostSnag work with?

Your PostSnag data lives in PostSnag's own systems: your account and captured post details in PostSnag's own database on a hosting provider called Contabo, and your captured media, including the real video file for any video or reel you capture, in PostSnag's Cloudflare R2 storage. A short, named list of outside providers each handle one specific part of running the service, like billing or email. PostSnag does not sell your data, and it does not hand it off to some unnamed list of "partners."

Here is exactly where things live, who is involved, and what each one actually touches.

Where your account and captured data actually live

Your PostSnag account record (your email, plus either a hashed password or a Google account identifier if you signed in with Google) and the details of everything you have captured, your Profiles library, Bookmarks, and Folders, are stored in a MongoDB database. That database runs on servers PostSnag operates through Contabo, a server hosting company.

That is the core of it: PostSnag's own database for your account and captured post details, plus PostSnag's own Cloudflare R2 storage for captured media, both under PostSnag's control, not your data scattered across a pile of third parties. MongoDB itself is not a separate outside company you hand data to; it is the database technology PostSnag's own systems run, sitting on Contabo's servers.

Facebook data you capture, the caption, post type, and engagement numbers, lands in that database once you click Export To Dashboard. Captured media works a little differently. Photos, and for videos and reels the real video file plus a cover image, are stored in PostSnag's Cloudflare R2 storage rather than in the MongoDB database itself. Nothing you capture while scrolling reaches PostSnag's servers before that; it stays in your browser's local storage until you export it. See How do I send my captured posts to the dashboard? (Export To Dashboard) for that part of the process.

The providers PostSnag works with, and what each one touches

A few specific, named providers each handle one part of running PostSnag. None of them gets more than what its specific job requires:

• Lemon Squeezy handles payments and billing. If you subscribe to Pro or buy Lifetime, Lemon Squeezy processes the charge and stores your payment details directly. PostSnag never sees or stores your full card number.
• Google handles sign-in, but only if you choose Continue with Google instead of email and password. Google confirms your identity to PostSnag; PostSnag never sees or stores your Google password.
• Resend sends transactional email on PostSnag's behalf: receipts, password resets, and account notices.
• Cloudflare stores your captured media, photos and, for videos and reels, the real video file plus a cover image, in Cloudflare R2 storage, and delivers those assets quickly and reliably wherever you are.
• Contabo hosts the servers PostSnag's database and backend run on, as described above.
• MongoDB is the database technology that stores your account and captured post details on those Contabo servers.
• New Relic monitors performance and errors, so problems get caught and fixed before they affect you.

These are the providers PostSnag works with to run the service today. PostSnag does not sell your data to anyone, and each provider above only receives what it needs to do its specific job, nothing more.

Cookies

PostSnag uses cookies to keep you signed in between visits, remember your preferences, and understand aggregate usage of the dashboard.

How your data is protected

PostSnag uses encrypted connections between your browser and its servers, and stores passwords hashed, never as plain, readable text. Access to the underlying systems is limited by access controls, not open to anyone by default.

Like any online service, PostSnag cannot promise perfect, unbreakable security. No service honestly can. What it can promise is the same baseline practices any serious service should have in place: encryption in transit, hashed passwords, and controlled access, not a guarantee that nothing can ever go wrong.

Common questions

Is my password stored in plain text?

No. Passwords are hashed, not stored as readable text, so PostSnag itself never has your actual password to expose, even internally.

Does PostSnag store my data outside its own systems?

Your account and captured post details are stored in PostSnag's own database on Contabo, and your captured media is stored in PostSnag's own Cloudflare R2 storage. Specific providers like Lemon Squeezy and Google only receive what they need for their own part of the service, like processing a payment or confirming your identity at sign-in.

Can PostSnag guarantee my data will never be exposed?

No service can honestly promise perfect security. PostSnag uses encrypted connections, hashed passwords, and access controls: industry-standard practices, not a guarantee of the impossible.

Who can see my captured posts?

Only you, inside your own dashboard. PostSnag stores what you capture so it appears in your Profiles library, Posts view, and Discovery, all scoped to your account. See Does Discovery share my captured data with other PostSnag users? for how Discovery specifically uses what you've captured.

Does PostSnag share my data with advertisers?

No. The providers listed above each handle one specific operational job, like billing or email delivery. None of them are advertisers, and PostSnag does not sell or share your data for advertising purposes.

Related articles

• How long does PostSnag keep my data?
• Does PostSnag sell my data?
• What data does PostSnag collect about me?
• Does Discovery share my captured data with other PostSnag users?
• Why does PostSnag ask for the permissions it does?

PostSnag is not affiliated with, endorsed by, or sponsored by Meta Platforms, Inc.