VAYEN / PRIVACY

Your trust matters.

A clear place to explain how VAYEN handles information, why it may be needed, and how you can reach us with privacy questions.

1. Overview

This page is a draft privacy-policy template for VAYEN. It must be reviewed and updated to match the actual website, analytics, login provider, payment provider, hosting, and data handling before public launch.

2. Information we may collect

Depending on which features are enabled, information may include an email address, account details, product selections, order references, and support messages. The website may also use technical information needed for basic operation and security.

Do not treat this list as confirmation that every feature is currently active.

3. How information may be used

  • To provide account access and help customers use purchased products.
  • To process and confirm orders once a real payment system is connected.
  • To respond to support requests and investigate checkout problems.
  • To maintain website performance, security, and reliability.

4. Payments and third-party services

When real payments are enabled, the payment provider will process payment information under its own terms and privacy policy. VAYEN should not collect or store full card details in frontend code.

Third-party services used for hosting, authentication, analytics, or email delivery must be listed here once selected.

5. Local browser storage

During development, parts of the VAYEN demo may use browser local storage to remember temporary settings or demo data. Browser storage is not a substitute for secure authentication, verified payments, or a production database.

6. Retention, security, and your choices

Before launch, VAYEN must specify how long personal information is kept, how it is protected, and how people can request access, correction, or deletion where applicable.

Privacy requests should be directed to the contact details on our Contact page.

7. Policy updates

We may update this policy as website features and services change. A publication or effective date should be added when the final policy is approved.

DRAFT — NOT A FINAL LEGAL POLICY. Review actual data flows, relevant laws, third-party providers, and the operator’s legal details before publishing.