Privacy in the preview

The current beta

GETBAUS is a preview project. The proposed GETBAUS OÜ company has not yet been incorporated and is not presented as an existing data controller. The people operating the project remain responsible for any processing they actually determine. The project privacy contact is [email protected]. The site is under development. The current operator’s formal legal identification remains unresolved; this notice is not a claim that all transparency requirements have been satisfied.

Do not upload personal data

Do not submit photographs, facial reports, health information, identity documents or another person’s information. Photo analysis, camera capture, report imports and gallery intake are disabled in this public beta. Please do not email photographs or reports. If you believe data was submitted accidentally, contact us with a short description without resending it.

Data generated when you browse

The site is delivered through Cloudflare. Requests necessarily expose technical information such as IP address, requested resource, time and browser/network details to hosting infrastructure. This can be processed to deliver pages, investigate faults and protect against abuse. Where applicable, the legal basis is legitimate interests in operating and securing the preview, balanced against visitors’ rights; processing required by law relies on the relevant legal obligation. A no-upload beta is not a promise of zero technical data collection.

Browser storage

Optional routines, completion ticks and notes can be saved in your browser. Do not enter personal or sensitive information into notes during the preview. These features do not sync to a user account. Use Clear saved data on the Plan page to remove its saved records, or clear this site’s data in your browser. Landing-page variant assignments and earlier preference records may also remain in browser storage until cleared. Clearing this browser does not delete copies elsewhere or data held by hosting providers.

Session replay on marketing pages (planned with Clarity)

If you accept analytics on a marketing landing page, Microsoft Clarity (project "GetBaus") may record interaction data on those pages only: clicks, scrolling and mouse movement, for understanding where visitors expect to be able to click. Clarity runs with Strict masking (all text masked; form input contents are always masked by the vendor) and never loads on the app, photo capture, analysis, results, account or admin pages - no recording code is present on those routes at all. No user identifiers, email addresses, photos, measurements or report contents are sent. Declining or revoking analytics stops Clarity: the consent signal is denied, its cookies are deleted and the page reloads so no further data is collected. Clarity enforces a denied-by-default state for EEA/UK/CH visitors. Advertising storage stays off.

Analytics and cookies

Optional Google Analytics 4 is active only after an explicit analytics accept in the on-site choice. It starts denied by default (Consent Mode v2), IP addresses are anonymized, advertising signals stay off, and declining keeps analytics off. The event set excludes photos, measurements, email addresses and report contents. The source contains an analytics integration, but configuration is not the same as collection. Essential hosting or security mechanisms may process technical data independently of analytics. Previously set cookies can be removed through browser settings.

Analytics preferences

Contact and privacy requests

If you contact [email protected], the project and its email provider receive your address, message and any information you include. We use necessary details to respond, resolve issues and meet legal duties. Where applicable, this relies on legitimate interests in handling enquiries, or a legal obligation for rights requests. Do not send attachments containing facial or health data. Only proportionate information needed to verify a request should be requested; do not send identity documents unless a specific, justified verification method is agreed.

Planned queue and storage (not yet active)

When personal analysis opens, submitting a photo will store the photo and your verified email address on Supabase infrastructure in Ireland (AWS eu-west-1), solely to process your analysis and email you when the result is ready. Submissions enter an automatic queue; site-wide capacity is limited to 5 verified users and up to 6 photos each per hour, with additional per-connection anti-abuse limits. Blocked or over-capacity activity is recorded in an abuse log using hashed identifiers (never raw IP addresses or email addresses), and the operator is alerted when limits are exceeded. Pending photos are deleted after processing; results are planned to be deleted 30 days after the result email, and abandoned submissions after 7 days. Submitting requires you to confirm you are at least 18 and legally an adult under the rules that apply to you, and to accept the current versions of the terms and this notice; we record those confirmations as self-declarations with document versions. You can withdraw: a deletion request removes your photo, report, queue entry, email record and attestation records. These behaviors are planned, not active today; this notice will be updated before the feature opens.

Future analysis is server-side

Personal analysis is not open in this beta. The prepared architecture sends a selected photo to an authenticated backend for facial landmark extraction and measurement. It does not measure faces on your device. If enabled after review, the analysis application is designed to process images in memory without writing photos or reports to application file storage or a database. This design is not a promise of secure erasure from every memory buffer, host log or backup. Deployment-specific providers, retention, access controls and any required consent will be disclosed before uploads are enabled.

Earlier data and gallery copies

If you used an earlier version, browser records or files you downloaded may still exist. Gallery storage and publication are separate from the planned analysis service. Withdrawal can stop new authorised publication requests, but cannot recall files someone already downloaded or immediately invalidate every previously issued link or infrastructure copy. Contact the project about an existing record; do not assume that closing this beta deleted earlier records.

Recipients and international access

Cloudflare handles web delivery, and an email provider handles messages you choose to send. Existing gallery records, if any, may be held in Supabase infrastructure. Providers may use sub-processors and infrastructure outside your country. Specific locations, contractual safeguards and retention settings must be verified before new personal-data features open. We do not claim EU-only processing or a completed transfer assessment. Information may also be disclosed where required by law or necessary to address a lawful claim, subject to applicable protections.

Retention and deletion

Retention depends on purpose: contact details are needed while resolving an enquiry and for any applicable legal or dispute requirements; security records depend on provider configuration and incident needs; browser records remain until cleared or removed by the browser. We do not state an unverified fixed deletion period. Deletion requests are assessed under applicable law, including necessary retention exceptions. Restricted backup copies may remain until the provider’s backup cycle expires. Removing active data is not a guarantee that all copies instantly disappear.

Your rights

Depending on the applicable law and circumstances, you may request access, correction, erasure, restriction, portability or object to processing based on legitimate interests. Where processing relies on consent, withdrawal does not affect prior lawful processing. Send requests to [email protected]. We will respond within the applicable statutory period and explain any lawful extension or refusal. You may complain to your competent data-protection authority, including the Estonian Data Protection Inspectorate where relevant.

Security and limitations

Access controls, upload gates and bounded processing reduce risk; they do not make a website risk-free. No promise of perfect security, anonymity or irreversible erasure is made. Avoid sending unnecessary information. We do not use the preview to identify people or make decisions with legal or similarly significant effects. There is no current model-training pipeline using visitor submissions.

Updates

This notice describes the preview, not approval to open personal-data processing. We will update it as the operator, features and verified infrastructure arrangements change. Material changes must be made visible before the affected feature is opened. See the Beta Terms of Service for permitted use.

Local development testing

A developer may explicitly enable uploads on a loopback test server. This is separate from the public preview. Use only authorised test images and follow the testing documentation. Photos are sent to that local Python backend for processing; face measurements do not run in the browser. This does not enable uploads on the live website.