1. Scope

This Privacy Policy covers the public AVRE Labs website, future My AVRE customer accounts, software licensing/download services, support interactions and the AVRE Originals subscriber service. AVRE Companion is designed with a separate local/private data domain for private conversations, private media and Companion profile information. This policy explains when information is processed online and why.

AVRE does not treat the existence of a website account as permission to upload a customer's private Companion history. Where a feature is local by design, the goal is for its data to remain on the customer's device unless the user deliberately invokes a feature that requires transmission.

2. Information you provide

Online services may process information you enter directly, including name, email address, support requests, account-security information, billing/subscription identifiers, complaint/removal requests and messages sent through AVRE Originals. When paid services launch, transaction information necessary to identify the purchase and entitlement will be stored, while raw payment-card data should be handled by the selected payment processor rather than intentionally stored by AVRE.

3. Technical information

The website and production APIs may process security and operational logs such as IP address, request time, browser/user-agent information, authentication events, rate-limit events and error diagnostics. These logs are used for security, abuse prevention, service reliability and troubleshooting. Production retention periods will be limited according to operational, contractual and legal requirements rather than keeping all logs indefinitely.

4. Local Companion data

Private Companion conversations, local profile/preferences and private Companion media are intended to stay in the local application domain by default. The website account does not require those contents merely to verify a software license. If AVRE later introduces an optional cloud-sync or remote-processing feature, that feature must be disclosed separately and should not silently change the default privacy model.

5. AVRE Originals subscriber data

The Originals service requires online data because it is an online membership. AVRE may process account status, subscription entitlement, content-access events, saved/favourite state, direct messages, customer-support records and moderation/compliance records needed to operate the service. Subscriber messages are not the same as private Companion chats and should not be represented as such.

6. Payments

CCBill is the planned processor to contact. When integration is approved, the checkout will direct customers into the appropriate processor payment flow. AVRE will receive transaction/subscription identifiers and status information required to grant or revoke access, handle support and maintain accounting records. The final live policy will name the actual processor and link to its applicable privacy information.

7. Cookies and local storage

The public site should use only necessary storage until analytics or other optional services are deliberately added. The current 18+ acknowledgement and browser Test Mode use local browser storage/IndexedDB. Production authentication will require security cookies or equivalent session mechanisms. Any non-essential analytics or advertising cookies introduced later will be documented and consent-managed where required.

8. Sharing

AVRE may share information with service providers that are necessary to operate the service, such as hosting, email delivery, payment processing, fraud/security services, object storage/CDN and professional advisers. AVRE does not sell customer personal data to advertisers. Data may also be disclosed where required by law or necessary to protect users, performers, AVRE or the public from fraud, abuse or unlawful activity.

9. Retention

Different records require different retention periods. Active account data is retained while the account/service is needed. Financial and transaction records may be retained for accounting, tax, dispute and legal obligations. Security logs are retained for an operationally justified period. Complaints and performer/content compliance records may require longer retention. Local Companion data follows the local application's storage/deletion controls rather than the website account lifecycle.

10. Security

AVRE uses HTTPS for the public site and plans authenticated production APIs, least-privilege administrative access, encrypted secrets, secure password/passkey practices, rate limiting, audit logging and backups. No security control makes a service risk-free. Customers should protect account credentials and local-device access.

11. Your choices and rights

Depending on applicable law, users may have rights to access, correct, delete, restrict or object to processing, and to obtain certain data in portable form. Requests can be sent to support. Some records cannot be deleted immediately where retention is required for legal, accounting, fraud or dispute purposes.

12. Adults-only services

AVRE Originals is intended only for adults of legal age. The service is not directed to minors. Age-verification controls may vary by jurisdiction and processor requirements.

13. Contact

Privacy requests: support@avrelabs.com. The legal operator and physical address will be added before commercial payment activation.

Launch item: AVRE Labs will insert the exact legal operator name, registered/business address, final prices, billing descriptor and processor-specific information before paid checkout is activated. Those facts are intentionally not invented in this build.