Privacy Policy

1. Information we collect

Account information includes the sign-in identifiers you use, verification status, optional profile details and records of agreement. Passwords and verification secrets are stored as protected hashes, not plain text. Store accounts also provide store name, licensee number and membership or claim information.

When you use the advisor, we store questions, replies and conversation context. We also record scans, browser identifiers, limited device descriptions, timestamps, usage and security metadata, support permissions and audit events. Approximate network identifiers may be hashed for abuse prevention.

For basic site traffic statistics, we record the public page path, visit time, a hashed IP identifier and an internal or external traffic label. We determine that label using the signed-in account, a previously identified browser or an internal network hash; the page-view record does not store an account ID or browser identifier. Older visits can only be classified approximately by network hash. Page-view records are normally removed after about 90 days and are not used for advertising. You can stop future page-view recording below; an earlier choice to decline remains effective.

2. How we use information

We use this information to authenticate accounts, deliver verification and essential account notices, generate replies, save signed-in conversation history, resolve scans, provide store services and aggregated activity reports, prevent abuse and investigate problems. We do not automatically subscribe you to marketing when you register.

Guests may browse and use the advisor without an account. Guest conversations stay associated with the browser and are not automatically imported into an account on sign-in. Conversations already saved to an account remain available there. A new conversation started while signed in is saved to that account.

3. Service providers and cross-border processing

Hosting and infrastructure providers process information to operate the site. AI model providers process necessary inputs and context to generate replies. Email or SMS providers deliver the account messages you request. If you choose Google or WeChat sign-in, that provider processes authentication information under its own privacy terms. Features and providers depend on those enabled for this service.

Suppliers may process information outside Canada. Foreign legal access rules may apply, and protection may differ from that in your location. Contact us for details about currently enabled providers, processing locations and applicable retention arrangements.

4. AI and support access

Advinture does not use your conversations to train AI models or provide conversation exports for training. This does not prevent the processing needed to generate a reply. Supplier processing and retention are governed by the relevant service terms and configuration; do not submit sensitive secrets in chat.

Staff tools cannot read conversation content by default. From Account → Help & feedback, you can grant read-only support access to one conversation for seven days and revoke it at any time. Support access attempts are audit-logged.

5. Cookies and browser storage

The wa_user_session cookie keeps you signed in for up to 30 days. The wa_device browser identifier supports guest conversations, scan resolution, attribution and abuse prevention; its cookie lasts up to 400 days and may be renewed. The advinture_language cookie remembers language for up to one year. We also use browser storage for language and conversation continuity, and temporary cookies for sign-in authorization.

Browser settings let you clear or block cookies and local storage; this may affect sign-in, guest continuity and scanning. Cookie expiry does not itself delete server-side records. New non-essential tracking uses require appropriate notice and choices before activation.

If you stop page-view statistics, the wa_analytics cookie remembers that choice for up to 180 days. You can change it using the control above.

6. Access and account controls

Account settings let you change an existing password and close your account. You can delete individual account conversations and manage support grants. Sign-in recovery and additional connections are available under Help & feedback; at least one sign-in method must remain.

To request access to or a copy of your personal information, contact us using the privacy contact below. We may verify your identity, will respond within the timelines required by applicable law, and will provide information in an understandable form, subject to applicable legal limits. You may also request information about its use and disclosure, correction or applicable deletion without closing your account. If access is restricted, we will explain the reason and available recourse.

7. Retention and account closure

Account and conversation records support ongoing use until deleted. Closing an account removes its account, authentication, conversation, permission, membership and associated scan and usage records from the primary database. Legacy guest records are removed only where the old device association is exclusive to that account; shared-device records and other users' data are not deleted as that account's records. Audit events are retained without the removed account identifiers and details.

Infrastructure logs, supplier-held records and any backups are separate from the primary database and are not erased by an immediate account action. Their handling depends on operational and supplier retention arrangements and applicable legal obligations. Contact us to request information or applicable deletion; we will explain records that must be retained and the reason. Closing an account does not delete the shared wine catalog or store's business records.

8. Security, age and changes

We use access controls, hashed credentials, session revocation, rate limits and audit records. No system is completely secure. We assess privacy incidents and provide notifications where applicable law requires. This service is intended for people of legal drinking age in their location.

We update the version and effective date when this policy changes. Material changes to data uses will be highlighted before they take effect and appropriate fresh consent will be sought where required.