Privacy Policy

Data controller

What we process

• Account data: authentication identity, email, role and service state.
• Private profile: optional display name, role, organization, sector, headline, locale, timezone, response preference and bio.
• Service telemetry: bounded usage counters, security events and operational records needed to run and protect the service.
• Billing metadata: subscription status and provider identifiers. Full payment-card data is handled by the payment provider.
• Consent records: choices required to demonstrate and respect analytics/marketing preferences.
• Health data: optional owner-scoped symptoms, bowel observations, habits, vitals, laboratory metadata and related notes are processed only after explicit health-module consent.

Local-first processing

Where a function can run entirely in the browser, YEAH.technology keeps working input local. Some network-oriented tools necessarily contact a third-party or YEAH endpoint; each such boundary is documented in the relevant methodology.

Purposes and legal bases

Data is processed as necessary to provide requested services and account functionality, to meet legal obligations, to protect the service and users through proportionate security measures, and—where required—on the basis of explicit consent for optional analytics, marketing or aggregate use.

Profile privacy

UserProfile records are owner-scoped through row-level authorization. Profile visibility is forced to private. Personalization can be disabled independently and does not automatically turn conversation transcripts into permanent profile memory.

Health data

YEAH Health treats health observations as sensitive personal data. The module is private, authenticated and owner-scoped, requires explicit consent before observations are stored, and provides export, deletion and consent revocation controls. Device ingestion is not represented as live unless a real source is connected and verified. Health outputs are observational decision support, not an automatic diagnosis or a substitute for qualified medical care.

Before production use with third parties, the controller must verify the applicable GDPR legal basis and Article 9 condition, retention policy, processor agreements, transfer safeguards, DPIA requirements and any medical-device or AI regulatory classification triggered by future clinical functionality.

Retention

Account and profile information is retained while the account is active and as needed to provide the service. Billing, legal, consent and security records may be retained for the periods required by applicable obligations or legitimate security/accountability needs. YEAH.technology avoids claiming a fixed retention period where the production processor or legal requirement has not yet been formally configured.

Recipients and processors

Data may be handled by infrastructure, authentication, billing and AI service providers only to the extent required for the relevant function and under the applicable contractual/privacy framework. The production register of processors and transfer safeguards must match the actual vendors enabled in the deployed environment.

Your rights

You may request access, correction, deletion, restriction, portability where applicable, objection to certain processing, and withdrawal of consent without affecting prior lawful processing. You may also lodge a complaint with the competent data-protection authority.

Contact

Privacy contact is a production launch blocker until the verified legal identity is configured.