Last updated: June 23, 2026
Core commitment
PDF417 Studio values privacy and data security. The service is built around ephemeral generation rather than content retention.
No payload storage
- Barcodes are generated in memory and returned directly to the browser or API client.
- Submitted payloads are not stored, archived, or written to application databases by default.
- Payload contents are not included in operational logs.
Technical logs and diagnostics
- Rate limiting uses client IP metadata in memory to control abuse and is not persisted by the app.
- Operational logs may record timestamp, endpoint, response status, and coarse client metadata needed to run the service.
- Unhandled-error logging excludes request bodies and barcode payload contents.
- Lightweight analytics record page and action events without payload data or personal profile fields.
Waitlist and launch-interest forms
- If you submit an email address through a launch-notification form, the app stores that email and the selected plan interest so launch notices can be sent later.
- Waitlist submissions are separate from barcode payload generation and are not mixed into barcode request logs.
- Waitlist data is used for launch communication and product planning, not for sale to third parties.
Retention
Because the product does not store generated barcode payloads by default, it does not maintain a long-term content history for generated symbols.