Principle: local-first
YEAH! follows data minimization by architecture, not just by policy. When a tool can function locally, no data is transmitted. This means:
- Percentage Calculator — all calculation is local. No data sent.
- Unit Converter — all conversion is local. No data sent.
- Days Between Dates — all calculation is local. No data sent.
- Word Counter — your text is processed locally. It is never sent to a server or stored.
Data we do process
What Is My IP — your public IP is fetched via api.ipify.org, a third-party API. YEAH! does not persist your IP for analytics. Browser metadata (browser, OS, screen) is detected locally and never transmitted.
Analytics
Analytics events are consent-based. We track tool usage events (tool_view, tool_completed) but never include the values you type into tools. Your text, calculations, dates and IP are never sent to analytics.
Accounts, profiles and subscriptions
Registered users can maintain a personal ALTER profile containing optional identity and preference fields such as display name, role, organization, response style and a short bio. These fields are used for personalization only when the user enables it. Subscription state and usage counters are stored separately from profile content. Payment card details are handled by the configured payment provider and are not stored in the Yeah.technology profile record.
Conversation data
The ALTERMORPHOS chat interface currently keeps conversation history in session memory by default. The personal profile is persistent, but chat content is not automatically promoted into permanent profile memory. Usage metering stores aggregate counters needed to enforce plan limits, not the full text of the conversation.
Your rights (GDPR)
You have the right to access, correct, export and delete personal data, to object to or restrict certain processing, and to withdraw consent where consent is the legal basis. Product-level self-service controls cover profile editing and personalization preferences; formal data-subject workflows still depend on the final production data-controller configuration.
Data controller
DATA CONTROLLER NOT YET CONFIGURED — This is a launch blocker. The legal entity profile must be completed before production deployment.