Privacy

What happens to a file

The upload is read in the request that receives it. For a text PDF, the server counts pages, extracts the selectable text, and builds the .paprikarecipes download in memory. The bytes are then dropped. They are not written to storage. A photo is refused before any conversion and is not saved either.

Training

Uploads are not used to train models. They are not added to a dataset, and they are not sent to a model provider.

How long a file can exist

The target is to delete a file when the request finishes. If a later version has to queue work, that copy will be deleted within 24 hours, and sooner when the conversion completes. There is no queue and no stored upload.

Cookies

The session cookie p2p_session holds a random id. It does not hold your password or your credit balance. The password is stored only as a hash on the account, next to the email. Credits and Pro are stored with that email. A second cookie, p2p_usage, counts guest and free conversions for the current UTC day. Spending a credit does not increase that count. Guest usage is also tied to a hash of the client IP.

Your data rights

For an account on this site, you can ask us to:

• Access — tell you what personal data we hold for your account (for example your email, credit balance, and Pro status).
• Correct — fix inaccurate account details we store.
• Delete / close your account — remove your account and the personal data tied to it (password hash, session, credits, Pro flag, and related usage keys). Recipe uploads are not kept after conversion, as described above.

Email hello@pdf2paprika.com from the address on the account (or include that address in the message). We aim to respond within 30 days. Payment records may also be held by our payment provider under their own retention rules.

Contact

Questions about a file or this policy: hello@pdf2paprika.com.