How we look after your work.
What AdForThat keeps, how it’s protected, and what we haven’t done yet. Plainly.
Your account
Your email, your name and how you sign in. Passwords are stored only as hashes, never as you typed them.
Signing in
A password, a code by email that works for 5 minutes and stops after 5 wrong tries, or Google, Apple, Facebook or Microsoft. Your session is kept in a cookie and lasts up to 30 days.
Your projects
Kept in your browser, and in your account when you’re signed in, so they’re there on any device. Only your account can open them.
Your Meta connection
We ask Meta only for what making and managing your ads needs. The access Meta gives us is encrypted before it’s stored, and you can disconnect at any time. Ads are always made paused.
What you upload
Photos and logos are stored under long random names and used only to make your ads.
Payments
Payments go through Stripe, through its Link checkout. Your card details go to Stripe and never reach our servers.
Who helps us run it.
Every service that handles personal data for us, and what it does, is on the subprocessors page.
Audits and certifications
We have none yet. AdForThat is new, and we’d rather say so than suggest otherwise. When an independent review happens, its summary goes here.
Report a security issue
Found a weakness? Tell us before anyone else: write to support@adforthat.com with “Security” in the subject, what you found and how to reproduce it. Test only on your own account, and don’t access other people’s data or slow the service down. We’ll keep you posted while we fix it, and credit you if you’d like.