Privacy Policy

Effective 13 October 2026 · Version 2026-10-13

1. Who we are
2. What we collect
3. Your recipients' data
4. How we use data and our legal bases
5. Who we share data with
6. International transfers
7. How long we keep data
8. Cookies and local storage
9. Security
10. Your rights
11. US state privacy rights
12. Children
13. Changes
14. Contact

1. Who we are

Piksio is operated by Baloka, 572 Saw Mill Brook Parkway, Newton, MA 02459, USA ("we", "us"). This policy explains how we handle personal data when you visit piksio.com, join our waitlist, or use the Piksio app. For the personal data of account holders and website visitors, we are the controller.

For the personal data our customers put into personalized images, the customer is the controller and we are their processor. Our Data Processing Addendum governs that processing, and section 3 explains what happens to it.

2. What we collect

You give us

• Account data: your email address and password (stored only as a secure hash by our authentication provider), and the date you accepted our Terms.
• Waitlist and referral data: your email address and referral code if you join the waitlist.
• Blog subscriptions and comments: your email and optional first name when you subscribe; your name, email, comment text and notification preferences when you comment. Approved comments and the name you enter are public; your email address is not shown with the comment.
• Content: templates, images, logos, fonts, brand details, prompts, and the website addresses you ask us to scan.
• Billing data: purchase history and credit balance. Stripe collects your card details directly. We never see or store full card numbers.
• Communications: messages you send us, including through our contact form: your name, email address, company or website, email platform, approximate sending volume and your message.
• Connected accounts: if you use social publishing, the identifiers and tokens our posting partner needs to post for you.

Collected automatically

• Usage and cost records: renders, AI generations, credits used, and errors (including a snapshot of the design that failed, to help us fix it).
• Technical data: IP address, browser type and request logs, which our hosting provider processes to deliver and secure the Service.

3. Your recipients' data

A personalized image URL carries data that you choose, such as ?first_name=Sarah. When an email client requests the image:

• we use the URL values to draw the image, then store the rendered image so repeat opens are fast;
• our view records hold a one-way hash of those values, not the values themselves, plus a coarse client type (for example "Gmail proxy" or "browser");
• we turn the requester's IP address into a salted hash for rate limiting. We don't store the IP address itself, the full user agent or precise location; and
• if a render fails, we log the error against the same hash, again without the URL values.

Our customers are responsible for their own lawful basis and notices to recipients. If you received an email containing a Piksio image and have a question about your data, please contact the sender first. We'll help them respond.

4. How we use data and our legal bases

We don't sell personal data. We don't use it for targeted advertising, and we don't use your content or your recipients' data to train AI models. We don't make decisions about you based solely on automated processing that produce legal or similarly significant effects.

5. Who we share data with

We share data with the service providers ("sub-processors") that help us run Piksio, and only for that purpose:

We may also disclose data if the law requires it, to protect rights, safety or the Service, or to a successor in a merger or acquisition, who will remain bound by this policy.

6. International transfers

Some providers process data outside the EEA, the UK or Switzerland, including in the USA. Where they do, we rely on adequacy decisions such as the EU–US Data Privacy Framework, where the provider is certified, or on the European Commission's Standard Contractual Clauses and the UK Addendum, with additional safeguards where appropriate.

7. How long we keep data

• Account data and content: while your account is active. After you delete your account, we delete it within 30 days, and it leaves our backups within a further 30 days.
• Rendered images: until you delete the template or your account. They are then removed on the schedule above.
• View records and rate-limit hashes: view records are kept while your account is active so we can show usage and bill accurately. Rate-limit hashes are short-lived.
• Error logs: up to 90 days.
• Billing and consent records: as long as tax and accounting law requires, typically up to 7 years.
• Waitlist data: until you unsubscribe or ask us to delete it. To give you the credits the waitlist promised, the app keeps a one-way hash of your email and the credit amount, never the address itself.
• Contact-form requests: up to 24 months after our last exchange, unless you become a customer. The hashed network address we use to limit spam is deleted within a day.

8. Cookies and local storage

We don't use advertising or analytics cookies. The app stores your login session and a few interface preferences in your browser's local storage, because it can't work without them. Our websites use no tracking cookies.

After you confirm a blog comment, a secure, HttpOnly cookie remembers that this browser has verified your commenter identity for up to one year. It contains a signed identifier, not your email address. You can clear it in your browser. Comment forms do not save your name or email in local storage. Newsletter unsubscribe links stop newsletter delivery; comment emails have separate links to stop notifications for one post or all posts.

9. Security

We encrypt data in transit (HTTPS) and at rest with our providers. We limit staff access, hash personalization values and IP addresses in our records, and keep user data separate with access controls. No system is perfectly secure. If a breach affects your data, we'll notify you and the regulator as the law requires.

10. Your rights

Depending on where you live, you may have the right to access your personal data, correct it, delete it, export it, restrict or object to our processing, and withdraw consent. To use these rights, email hello@piksio.com from your account email. We'll reply within one month. You can also complain to your local data protection authority. In the EU, that is the authority in your country. In the UK, it is the ICO.

11. US state privacy rights

If you live in California or another US state with a consumer privacy law, you may have the right to know what personal information we collect, to delete or correct it, and to opt out of its "sale" or "sharing". We don't sell or share personal information as those laws define it, and we won't discriminate against you for using your rights. The categories we collect are listed in section 2, and their uses in section 4.

12. Children

Piksio is a business tool. It isn't directed at children, and we don't knowingly collect data from anyone under 16.

13. Changes

We'll post updates here and change the version date. If we make material changes, we'll notify account holders by email or in the app before the changes take effect.

14. Contact

Baloka · 572 Saw Mill Brook Parkway, Newton, MA 02459, USA · hello@piksio.com