Security
Account access
Production tool routes require a Supabase session created with Google or an email and password. Email passwords must contain at least 12 characters in PeachSoft's interface. Session tokens are stored by the Supabase browser client and refreshed through the account service. The account gate measures ordinary platform use; because PeachSoft is a static web application, it is not a server-side paywall and does not make public JavaScript assets confidential.
Redaction, not whiteout
Use Redaction to remove sensitive content. Redacted exports are new, image-based PDF pages without the original selectable text. OCR and pattern detection can miss content, so check coverage before exporting. Studio whiteout and text replacement are visual edits, not secure redaction.
Encrypted packages
Encryption creates a .peach package, not a password-protected PDF. Version 2 packages use AES-GCM with a 256-bit key, PBKDF2-SHA-256 with 600,000 iterations, a 16-byte random salt and a 12-byte random IV. The JSON envelope records its version, algorithm, KDF parameters, filename, salt, IV and base64 ciphertext. PeachSoft can still decrypt legacy version 1 packages. Open the package in PeachSoft to recover its original bytes. Keep the password: there is no recovery service.
Build verification
The hosted release publishes a machine-readable build manifest containing the content-derived build ID and SHA-256 hash of every shipped file. Third-party licence notices are available in Licences.
Local signing requests
Drawn, typed and uploaded signatures are visual marks. Portable .peachsign files can assign fields to several recipients, enforce a local signing order and retain a hash-linked activity record. They are exchanged manually and do not verify identity, prove email delivery, create a neutral third-party audit trail or produce certificate-backed digital signatures. Completed PDFs state this boundary explicitly.
Keep your originals
Exports are separate copies. Some exports flatten form fields, links and signatures. Store the original PDF and optional Project JSON backup separately from the edited copy.