←

Privacy Policy

Last updated: June 2026

Our Commitment to Privacy

RedoSan Authenticity is designed to be 100% private by default. The application runs entirely client-side — in your browser or via the Node.js CLI. No files, metadata, personal information, or analytics data are ever collected, stored, or transmitted to any server. Every watermark, fingerprint, timestamp, and certificate is generated locally on your machine.

Data Collection

We collect nothing. RedoSan Authenticity has no backend server, no database, no user accounts, no tracking cookies, no analytics service, and no telemetry. The application is hosted statically on GitHub Pages and all processing occurs in your browser's JavaScript runtime or the Node.js CLI environment.

  • No uploads: Files you process are never sent over the network
  • No cookies: The application does not set or read any tracking or analytics cookies
  • No localStorage: User preferences (theme, language) are stored in your browser's localStorage for convenience only and never transmitted
  • No accounts: There is no registration, authentication, or user profiling

How It Works

When you upload a file to any tool in RedoSan Authenticity, the file is read into your browser's memory using the HTML5 File API. All subsequent processing — hashing, watermark embedding, pixel manipulation, metadata extraction, timestamp creation, certificate generation — happens entirely within the JavaScript runtime of your browser. The processed result is offered as a downloadable file or displayed on screen. No data is written to any disk on the server, nor is any data transmitted over the network (with the explicit exception of OpenTimestamps, described below).

Network Requests

The application makes the following network requests, all of which are necessary for functionality:

  • CDN library loading: JavaScript libraries (jsPDF, JSZip, PDF-lib, QRious, LameJS, FFmpeg.wasm) are loaded from cdnjs and jsdelivr CDNs. All loaded scripts use Subresource Integrity (SRI) hashes to ensure they have not been tampered with. These CDNs may log standard HTTP request metadata (IP address, User-Agent, requested file) in accordance with their own privacy policies. No data from your files is included in these requests.
  • OpenTimestamps: When creating a timestamp, the SHA-256 hash of your file (not the file itself) is sent to OpenTimestamps calendar servers to be anchored in the Bitcoin blockchain. The original file content cannot be reconstructed from this hash. Verification and upgrade requests similarly send only hash data.
  • Service Worker: The application registers a Service Worker for offline caching and security enforcement. The SW operates entirely within your browser and does not communicate with any external server beyond the initial page load.
  • GitHub Pages hosting: The application is hosted on GitHub Pages. GitHub may collect standard server logs in accordance with their Privacy Statement.

Third-Party Code

The following third-party libraries are loaded and executed client-side:

  • jsPDF — PDF generation for certificates and reports
  • JSZip — DOCX file creation and extraction
  • PDF-lib — PDF manipulation for document watermarking
  • QRious — QR code generation for certificates
  • LameJS — MP3 encoding for audio processing
  • FFmpeg.wasm — File format conversion
  • OpenTimestamps.js — Timestamp creation and verification

All libraries are loaded with SRI integrity hashes. No library has access to your files beyond what is explicitly passed to it by the application code. All libraries execute in your browser's sandboxed JavaScript environment.

Security

  • Content Security Policy: The application enforces a strict CSP that restricts script sources, prevents inline script execution, and blocks connections to untrusted origins.
  • Subresource Integrity: All CDN-loaded scripts and stylesheets are verified against SHA-384 integrity hashes before execution.
  • Service Worker: The SW acts as a security layer, blocking 68+ dangerous file extensions, enforcing a JavaScript file whitelist, and detecting embedded URLs at multiple encoding levels.
  • Domain origin check: All JavaScript files verify they are executing on the expected domain (redo-san.github.io, localhost, or 127.0.0.1) and silently refuse to run on untrusted domains.
  • File validation: Uploaded files are validated against a 6-layer security pipeline including extension blocklist, magic byte verification, content scanning, and document threat detection.

Children's Privacy

RedoSan Authenticity does not knowingly collect any personal information from children. The application is not directed at children under the age of 13. As no data is collected from any user at any age, there is no risk of inadvertent data collection from minors.

Changes to This Policy

This privacy policy may be updated occasionally to reflect changes in the application or legal requirements. The date of the last update will always be displayed at the top of this page. Continued use of the tool after any changes constitutes acceptance of the updated policy.

Contact

If you have questions about this privacy policy or the privacy practices of RedoSan Authenticity, please open an issue on GitHub or start a discussion in the Discussions section.

RedoSan
💬
🤖 RedoSan Assistant