Short version: PixelAuth does not collect, store, or transmit any personal data. Everything stays on your device.
Introduction
PixelAuth ("the App") is an iOS application developed to help users authenticate their photos and media files through invisible digital watermarking and RFC 3161 timestamping.
This Privacy Policy explains what information the App accesses, how it is used, and what rights you have. We are committed to protecting your privacy and processing only what is strictly necessary for the App to function.
Data We Do Not Collect
PixelAuth does not collect, transmit, or store any of the following:
- Personal identification information (name, email, phone number)
- Location data
- Device identifiers or advertising IDs
- Usage analytics or behavioral data
- Photos, videos, or any media content
- Crash reports or diagnostic data sent to a third-party server
Data Processed Locally on Your Device
All processing in PixelAuth happens entirely on your device. The following data is created and stored locally in the App's private sandbox:
- Signed media metadata — file name, signature date, watermark mode, and DCT confidence score
- Timestamp data — RFC 3161 token received from your chosen TSA provider
- App settings — your selected TSA provider URL, stored via UserDefaults
- Onboarding state — whether you have completed the introduction screen
None of this data leaves your device unless you explicitly choose to export a certificate or share a file.
Camera and Photo Library Access
PixelAuth requests access to your camera and photo library solely to allow you to select or capture media for signing. The App does not store, upload, or share any of your photos or videos.
- Camera — used only for the "Signed Capture" feature to take a photo and sign it immediately on-device
- Photo Library (read) — used to select an existing image for signing or analysis
- Photo Library (write) — used to save the signed image back to your library upon your explicit request
These permissions can be revoked at any time in iOS Settings > PixelAuth.
Network Requests — TSA Timestamping
When you sign a media file, the App may contact a Time Stamping Authority (TSA) server to obtain an RFC 3161 timestamp. This request contains only a cryptographic hash of your media file — never the file itself.
- Default provider: FreeTSA (freetsa.org) — a free, public RFC 3161 service
- Custom provider: you may configure any RFC 3161-compatible TSA server URL of your choice
PixelAuth has no control over the data practices of third-party TSA providers. We recommend reviewing the privacy policy of your chosen TSA provider.
If no network connection is available, the DCT watermark is still applied locally and timestamping is simply skipped.
Data Retention and Deletion
All data stored by PixelAuth (signed media records, settings) resides in the App's private container on your device. You can delete all App data at any time by uninstalling PixelAuth from your device. No data is retained on any server controlled by us.
Children's Privacy
PixelAuth is not directed at children under the age of 13. We do not knowingly collect any information from children. If you believe a child has used the App and you have concerns, please contact us at the address below.
Changes to This Policy
We may update this Privacy Policy from time to time. When we do, we will update the "Last updated" date at the top of this page. We encourage you to review this policy periodically.
Contact
If you have any questions about this Privacy Policy or how PixelAuth handles your data, please contact us:
PixelAuth
Email: contact@pixelauthapp.com