Privacy Policy

Information collected

• Account registration and authentication data, such as email address and account identifiers.
• Profile details you submit, such as name, phone number, and contact address.
• Simulated evaluation settings, test-checkout activity, and account history.
• Technical data needed for service functionality and security, such as request metadata. Actual analytics, cookies, and log retention must be audited before publication.

Why information is used

Information is used to authenticate users, provide requested account features, record demo evaluations, troubleshoot technical issues, and protect the service from misuse. Actual purposes and applicable legal bases must be verified against the deployed product.

Service providers

The current application uses Supabase for authentication and application data. Hosting, email delivery, analytics, monitoring, and future payment providers must be accurately identified based on the production setup. Do not assume that a future payment processor is already connected.

Sharing and retention

Access to account information should be limited to authorized staff and processors providing the service. Retention periods, deletion workflows, backup policies, and cross-border processing details must be determined from actual deployment practices before this document is finalized.

Your privacy choices

Users should be able to request access, correction, or deletion when applicable. The actual request channel, verification procedure, timelines, and jurisdiction-specific rights must be added before launch.

Security and minors

No online service can guarantee absolute security. Margin should use appropriate authentication, access controls, and encryption. A verified minimum-age policy and any required protections for minors must be implemented prior to public availability.

Privacy contact

A verified privacy contact email, legal entity details, and effective date must be supplied before launch. No unverified support mailbox is presented here.