This policy covers two different relationships, because InkMePlz plays two different roles depending on whose data it is.
1. Your studio account (we are the controller)
When you sign up as a studio, we collect your email address, name, studio details, and -- via Stripe -- payment information to bill your subscription. We're the data controller for this information: we decide why it's collected (running your account, billing you) and how long it's kept.
2. Your clients' data (we are the processor)
When you take bookings, you collect your own clients' names, contact details, and reference images through InkMePlz. That data belongs to you and your clients -- you are the data controller for it, and we are the data processor, acting only on your instructions to run the booking service. See our Data Processing Addendum for the full terms of that relationship.
3. Sub-processors
We use the following third parties to run the service. None of them can use your data for their own purposes.
• Neon -- Database hosting (Postgres) -- stores all account and booking data.
• Cloudflare R2 -- Object storage for uploaded images (banners, portfolios, reference photos).
• Resend -- Sends transactional email (booking confirmations, reminders, password resets).
• Stripe -- Processes subscription payments and, for studios using it, client deposits.
4. Retention
Account and booking data is kept for as long as your account is active, plus a reasonable period afterward for legal/accounting purposes. Signed consent forms follow their own retention policy (shown at the point of signing) and are automatically purged once it expires. You can ask us to delete your account and its data at any time (see below).
5. Your rights
Under UK/EU GDPR (and equivalent rights for California residents under CalOPPA/CCPA), you can ask to access, correct, or delete your personal data, or ask what we hold on you. Email
[email protected] and we'll respond within a reasonable time. If InkMePlz is processing your data as a studio's client (not a studio account holder yourself), start with that studio -- they're the controller for your data and the right first point of contact.
6. Cookies
See our separate Cookie Policy -- short version: we don't use any.