Data & privacy

Where I stand
on your data.

I'm not an agency, and security is the part of this I actually care about getting right. Here's exactly where I land. The Privacy Policy has the formal version.

Numbers, not faces

Creatorstaq is a data product, not a contact book. We compute spend, segments and revenue. We never collect or display fan photographs, government identifiers, phone numbers, or personal email addresses. There's no contact list to leak, because one is never built.

Encrypted to the hilt

Security isn't a box I ticked at the end. It's the part of this I actually enjoy. Connected-account credentials are encrypted (AES) at rest and never shown back to anyone. Everything moves over HTTPS. Your synced data is isolated to your own agency scope, behind role-based access. Payments run through Stripe; full card numbers never touch our servers.

Compliant, and then stricter

We're GDPR-compliant, and wherever I get a choice I lean tighter than the baseline, not looser. Less data kept, fewer people with access, shorter retention. When in doubt, the default is restraint.

Delete means delete

This is the part I mean it on. Close your account and your data doesn't drop into a 30-day limbo or a “soft delete” we could quietly restore. It's destroyed immediately and irreversibly. Not archived, not anonymised-but-kept, not sitting in a drawer marked just in case. Once it's gone, even I can't bring it back. No takeback. That's the entire point.

On authorization. Agencies use Creatorstaq to manage accounts on behalf of the creators they work with. For that connected data, the agency is the controller and Creatorstaq is the processor, acting on the agency's instructions. Every data pull is an authorized business operation: not scraping, not piracy. If you're a creator with a request, reach out to the agency that connected your account and I'll help them honour it.

Want the binding version? Read the Privacy Policy and Terms of Service. Got a pointed question? Ask me directly.