Accounts and business records
Configured Apple/Google sign-in is used to establish an application identity. The service stores account/session records, business membership and roles, client contact information, consultations, notes, look mappings and recorded consent. Reviewed contact-file import is a professional action; it does not establish media or marketing consent.
Purposes and access
Records support consultations, client continuity, authorized media actions, recovery and account security. Access is limited by business membership, care-team authorization and purpose-specific consent. Stored suggestions/choices require their separate authorization; local preview alone does not store a recommendation record.
Photos and preview processing
Selected-photo preview analyzes images in local memory. Captures begin locally; keeping, synchronizing or exporting them is an explicit action. Native/web camera and selected-file permissions are controlled by the device. Previews are estimates and are not identity recognition or diagnosis.
Server media and retention
Authorized originals, previews, comparisons and recordings can be synchronized to the configured service. The current implementation encrypts media using authenticated encryption and applies business/client access controls. Its default media retention is 90 days: expired media is denied and request-driven cleanup records deletion receipts. A scheduled purge and complete production backup-expiration process remain release work; the default is not a promise that every backup disappears at day 90.
Encrypted device recovery
The optional recovery vault encrypts saved client records, consent snapshots, media and queued notes with a passphrase-derived key. The passphrase is not stored. Losing it can make the vault unreadable; browser storage can also be evicted. Offline consent is a bounded snapshot and cannot learn an immediate revocation while disconnected.
Sign-in and service providers
Configured identity providers receive the information needed for sign-in under their own policies. The application API and database receive the records you authorize for the workspace. Local fallback suggestions do not call an external AI service. These pages do not enable a future AI provider, payment service or marketplace.
Consent withdrawal and deletion
Revoking consent can block future access or synchronization; it is not the same as deleting existing server ciphertext. Available client-deletion actions remove associated records. Synchronized device copies reconcile when online; previously exported files, offline devices and backups cannot be recalled instantly. Account/session sign-out revokes access, not client records.
Account requests and professional responsibilities
Complete self-service account deletion/recovery remains unfinished in current beta development. Contact support for an account/data request; ownership, business records and any retention obligations must be checked. Professionals must obtain appropriate permission before entering client information or using photographs, including any required guardian permission.
These public pages and support email
These static product pages add no advertising, analytics scripts, account sign-in, tracking cookies or embedded third-party fonts. The website host still receives ordinary connection/request information needed to serve and protect the site. If you email support, your address, message and any attachments are processed by the mailbox/email services to respond and handle the request; provide only what is necessary.
Your choices and requests
Use available app controls, device permissions and the separate data-deletion page for product-specific choices. You may contact support to ask about access, correction, deletion or other privacy rights available to you. Identity and authority must be verified before records are disclosed or changed. No response deadline or outcome is guaranteed by sending an email.
Security and policy changes
No device, hosting service or software system can guarantee absolute security. Protect your device and credentials. Material changes to data practices require an updated policy and appropriate notice before the changed behavior is distributed.
Contact and responsible developer
Developer: Anthony LaVear · Product: LUXVUE
Email: support@anthonylavear.com
Product support · Data & account deletion