Legal

Privacy Policy

Last updated September 15, 2026. This policy explains what Proofika collects, why, and what we do not do.

The short version — editing happens in your browser, and PNG and GIF exports are normally produced on your own device. SVG export — and PNG export in some cases — is rendered on our server: the card's text and brand settings travel to us for that render and are then discarded, not stored. If you sign in and save a project, we keep it so you can come back to it. We do not fingerprint your device, we run no advertising trackers, we do not sell personal data, and we never see your card details — payments are taken by Waffo Pancake.

1.Who we are

Proofika is operated by Zhang Wei, China. For the GDPR and similar laws we are the data controller for the processing described here. Questions: proofika@163.com.

2.What we collect

Account data. If you sign in with Google: your email address, name and profile picture. If you register with an email address and password: your email address and a salted hash of your password — we never store the password itself.
Content you choose to save. Projects and brand settings you save while signed in, and images you upload (avatars and logos). These are stored on our servers so you can return to them.
Content sent for rendering. When you export an SVG, and for some PNG exports, the card's text and brand settings are sent to our server to be rendered. They are used for that render and then discarded — see section 4.
Technical data, collected automatically. When a page loads we record its path, a hash of your IP address and your browser's user agent, so that we can count page views and returning visitors. When you sign in we record the time, the method you used, and the address and user agent you signed in from. Both are our own records — we run no third-party analytics.
Transactional email. If you ask us to reset your password, your email address is passed to our email provider, Resend, which delivers the message.
Payment data. Pro is a monthly subscription; the recurring payments are handled entirely by Waffo Pancake as merchant of record. We receive only the status of each transaction, the amount, the currency and an order reference — never your card number. Waffo sends you the receipt for each renewal; we do not store a copy of your payment method.

What we do not do:

we do not fingerprint your device or browser;
we run no advertising or cross-site tracking technology;
we do not sell or rent personal data.

3.Why we use it, and our legal bases

Running the Service and producing the exports you ask for — contract.
Keeping the Service available and enforcing limits against abuse — legitimate interest in protecting the integrity of the Service.
Measuring how the site is used — page view and visitor counts built from a hashed IP address — legitimate interest in understanding and improving the Service. You can object to this; see section 9.
Answering support requests — contract or legitimate interest.
Meeting legal obligations — legal obligation.

4.What happens to a card when you export it

Editing a card happens in your browser. Exporting as PNG or GIF is produced in your browser in the normal case, from what is already on your device. Exporting as SVG — and PNG in some cases — is rendered by our server instead, because that gives a true vector file, or a sharper image, than a browser capture can. For those exports the card's text and brand settings are transmitted to us, held in memory for the render, and discarded when the response is sent. We do not write them to a database or a log, and the endpoint is rate-limited.

The practical difference: content you put in a card is only ever sent to us to be rendered, never to be stored — unless you sign in and save a project, which is the one case where we keep it.

5.Cookies and local storage

refresh_token — a first-party HttpOnly cookie, unreadable by scripts, that keeps you signed in: 30 days if you chose "remember me", 1 day otherwise. It holds a signed token identifying your account and session, it is replaced each time it is used, and we can revoke it on the server.
oauth_state, oauth_remember, oauth_next — short-lived HttpOnly cookies used only while signing in with Google, to protect against request forgery and to return you to the page you started from.
Two localStorage entries on your device: one that tells other open tabs that you signed in or out, and one that remembers where to send you after logging in.
Your access token is kept in memory only and is never written to storage, so closing the tab discards it.
No third-party advertising cookies. Google sets its own cookies under Google's policy, and only if you choose to sign in with Google.

6.How long we keep things

Data	Retention
Account data (email, name, avatar)	Until you delete your account
Saved projects, brand settings and uploaded images	Until you delete them, or your account — and never sooner than 30 days after a subscription ends, so a lapsed payment cannot cost you your work
Card data sent for server-side rendering	Not stored — held in memory for the render, then discarded
Security and rate-limit logs (IP address, timestamps)	Only for as long as the rolling window that enforces the limit
Page view statistics (path, hashed IP address, user agent)	No fixed period — see the note below
Login records (time, method, address, user agent)	No fixed period — see the note below
Support correspondence	No fixed period — see the note below
Payment records	Held by Waffo Pancake under its own policy

Where we give no fixed period, the test is the purpose the data was collected for: we keep it only while it still serves that purpose, and no longer. Page view records are not linked to your account in any way; login records are, and they are kept for the security of that account.

You can ask us to delete your account and everything saved in it at any time by writing to proofika@163.com.

7.Who we share it with

We share personal data only with: Waffo Pancake, which takes payments and acts as merchant of record; Resend, which delivers transactional email such as password resets; our hosting and infrastructure providers, in the United States, under confidentiality obligations; and public authorities where the law requires it. We have no advertising partners and we do not sell personal data.

8.International transfers

Data is hosted in the United States. If you are in the EEA or the UK, that means data about you is transferred outside your region. For those transfers we rely on the European Commission's Standard Contractual Clauses — and, for transfers from the UK, on the International Data Transfer Agreement or the UK Addendum — together with our own assessment of the laws of the destination country. You can ask us for a copy of the clauses we rely on at proofika@163.com.

9.Your rights

Depending on where you live — including the EEA, the UK and California — you may have the right to access, correct, delete, restrict or export your personal data, and to object to processing based on legitimate interest. Write to proofika@163.com and we will respond within 30 days. You may also complain to your local supervisory authority.

10.Children

The Service is not directed at children under 16 and we do not knowingly collect their data. If you believe a child has given us personal data, contact us and we will delete it.

11.Security

We use reasonable technical and organisational measures: traffic is encrypted in transit, passwords are stored only as salted hashes, sign-in tokens are HttpOnly and short-lived, and we keep the data we hold to the minimum the Service needs. A small number of administrators can reach stored data in order to run the Service and to answer support requests, and what they do there is written to an audit log. No method of transmission or storage is completely secure.

12.Changes

We will post any update here with a new "last updated" date, and announce material changes in the Service or by email where that is practical.

13.Contact

Privacy questions and requests, or anything else about the Service: proofika@163.com.