RCHIVE Privacy Notice

Release-candidate notice · 20 August 2026

Local files stay local

RCHIVE catalogs files on the computers and sources you choose. The paid license service does not need file names, file contents, recipes, previews, or catalog contents to issue or validate a license.

Purchase and account data

Polar processes checkout, payment, tax, billing, and receipt data as merchant of record. RCHIVE receives order identifiers, product/price/status facts, and account contact data needed for fulfillment. Email addresses are normalized, hashed for lookup, and encrypted when recoverable delivery is required. Names are optional and encrypted when retained.

License and device data

RCHIVE stores a license identifier, entitlement/status, support reference, signed artifact metadata, and audit events. Online activation stores a one-way device hash, platform, customer-supplied device label, activation status, and activation/last-seen times. It does not store a raw hardware identifier. Account sessions, one-time codes, and download tokens are stored as hashes and expire or are revoked.

Delivery and operations

ZeptoMail processes transactional delivery. Monitoring uses dedicated test identities and bounded receipt metadata. Security, support, and audit records may retain pseudonymous identifiers needed to prevent abuse, investigate incidents, honor refunds, and prove license actions.

Choices and requests

You can use an exported license file offline, deactivate devices, log out of the account, and contact support@rchive.computer for access, correction, deletion, or contact-change requests. Some financial, fraud-prevention, audit, and entitlement records must be retained where law or legitimate operational needs require it.

Security and transfers

RCHIVE minimizes public responses, encrypts recoverable contact and license artifacts, and avoids placing license or payment secrets in browser-visible configuration. Providers may process data in other jurisdictions under their own terms and safeguards.