Updated October 2, 2026
Security & data handling
This page describes implemented controls and their limitations. It is not a security certification, an audit report, or a claim of Shopify approval.
Access and encryption
Fortune uses authenticated account identifiers and server-side ownership checks for saved account records. Shopify and Meta authorization credentials are encrypted by the backend. Provider integrations use HTTPS. Cloudflare documents encryption at rest and transport protections for D1 and R2. Those infrastructure controls do not certify every browser cache, log, backup, export or third-party copy.
Testing, logging & recovery
Automated tests use isolated in-memory databases, synthetic fixtures and mocked provider responses. This does not establish that every staging or manual workflow is isolated from production. Fortune records authenticated application API access attempts and outcomes with the account identifier, an allowlisted route category, HTTP method and timestamps. Request bodies, URL query strings and credentials are excluded. If the initial audit entry cannot be stored, the authenticated API request is blocked. An unavailable final outcome remains visibly unknown. These logs do not cover direct database, hosting-console or independent provider access.
A complete backup inventory, encrypted export procedure, recovery exercise and organization-wide data-loss prevention program have not been verified for this release. Infrastructure encryption alone should not be treated as evidence that every backup is encrypted or that lost data can always be recovered.
Privacy request handling
The Shopify integration validates webhook signatures and contains specific uninstall and redaction handling. Validated customer privacy requests enter an encrypted, deduplicated queue with due dates. Owner-only operations provide paginated evidence exports, resumable scoped redaction and a separately confirmed completion record. Exports identify coverage gaps; receipt or download alone does not mean fulfillment. Requests can also be raised directly through the privacy contact route; completion requires verification and handling of the relevant records.
Report a security concern
Email admin@fortuze.com with the affected feature, approximate time and a description. Do not include passwords, tokens, full payment details or unnecessary customer information. We may ask for a safer way to exchange additional evidence.
This contact channel does not imply a continuously staffed security team, guaranteed response time, or completed incident-response program. Where an incident affects personal data, assessment and any required notices must follow the applicable obligations.