Responsible entity
Responsible entity: Michael Korta, c/o flexdienst – #21385, Kurt-Schumacher-Straße 74, D-67663 Kaiserslautern, Germany. Contact for data protection enquiries: dsb@tijah.me. Support and questions about the app: support@tijah.me.
Privacy
Updated: 4 November 2026. This privacy policy covers the public website tijah.me and the Tijah app for closed Google Play testing. Outdoor information applies to Android test builds in which the relevant feature is enabled; Outdoor is not yet generally released.
Responsible entity: Michael Korta, c/o flexdienst – #21385, Kurt-Schumacher-Straße 74, D-67663 Kaiserslautern, Germany. Contact for data protection enquiries: dsb@tijah.me. Support and questions about the app: support@tijah.me.
This page applies to tijah.me, the Tijah Android app with package name me.tijah.app, and the backend services used for the app, authentication, support, analysis, payment, and the Google Play closed test. Internal tester lists, credentials, server secrets, and private review notes are not published.
When you use the contact form, we process your email address, message and optional name to respond by email. The form is delivered through STRATO’s email service to our support@tijah.me mailbox hosted by STRATO. STRATO processes sender, recipient and reply-to addresses, message content and technical delivery information for this purpose. A data processing agreement with STRATO covers the email service. Enquiries are not additionally stored in a form database. All incoming messages to our configured tijah.me mailboxes and their aliases are forwarded by STRATO to the operator’s business Gmail mailbox under Google Workspace Business Starter and stored there to handle correspondence. This includes messages to info@tijah.me, support@tijah.me and dsb@tijah.me, including contact form enquiries, as well as the associated technical contact addresses. Google processes sender, recipient and reply-to addresses, message content, any attachments and technical delivery information. The provider is Google Cloud EMEA Limited, 70 Sir John Rogerson’s Quay, Dublin 2, Ireland. For this business email processing, Google acts as a processor under Article 28 GDPR pursuant to the agreed Workspace terms, including the Data Processing Addendum (business.safety.google/processorterms/). Google may also process data outside the European Economic Area, particularly in the United States. The EU-US Data Privacy Framework applies to transfers to appropriately certified Google entities in the United States; where no applicable adequacy mechanism is available, the data processing terms provide for EU Standard Contractual Clauses. The terms contain the applicable safeguards; further information about transfer mechanisms is available at policies.google.com/privacy/frameworks. Technical IP-based rate limiting and a spam check field protect the form against misuse. The legal basis is Article 6(1)(b) GDPR for contract-related enquiries, otherwise Article 6(1)(f) GDPR based on our interest in responding to enquiries and protecting the contact channel. Correspondence is deleted after the enquiry is fully resolved, unless statutory retention duties or necessary retention for legal claims apply. Please do not send health information, passwords or payment details. For the online withdrawal function, we process and store your name, acknowledgment email address, identification of the contract or part of contract, withdrawal declaration, language, case reference and the date and time of receipt in our application database. The existing mail outbox additionally stores recipients, delivery status and technical retry information; it sends the acknowledgment to the address you provide and a separate notice to support. The email providers described above are also involved. Entering details in the form does not automatically match or delete your account. The legal bases are Article 6(1)(b) GDPR for handling the contract, Article 6(1)(c) GDPR for the acknowledgment under section 356a BGB where legally required and, where necessary, Article 6(1)(f) GDPR for evidence and the defense of legal claims. These records are also deleted after final processing, unless statutory retention duties or necessary retention for legal claims apply. The withdrawal function uses time-limited IP- and recipient-based rate limiting and a spam check field; no health information is required.
We process the account data required for registration, sign-in, account management and agreed test access under Article 6(1)(b) GDPR. Before the first entry, we request explicit consent under Article 6(1)(a) and Article 9(2)(a) GDPR for personal body, weight, nutrition, activity and training data, including health information inferred from them. This also applies to manual entries. Without this consent, personal tracking features remain blocked; the account, basic settings, help, contact and legal information remain accessible. External AI processing, website analytics and app analytics each require their own voluntary consent. Where necessary, we process technical operational and security data under Article 6(1)(f) GDPR: our legitimate interests are keeping the service secure and available, preventing abuse and investigating technical errors. This basis does not permit additional processing of health data without an exception under Article 9(2) GDPR. Where specific statutory retention or evidence duties apply, the necessary processing is based on Article 6(1)(c) GDPR. Consent records serve, in particular, the duties under Article 5(2) and Article 7(1) GDPR. We record health-data decisions with the account, purpose, text version, language and server timestamp. For external AI, we record granted consent with the account, text version, language and acceptance time, together with a subsequent withdrawal time. Refusal, withdrawal and technical errors are not treated as consent. Device permissions and acceptance of terms do not replace consent under data protection law.
For registration, sign-in, email verification and test access, Tijah processes the email address, first and last name, display name, birth date to check the minimum age of 18, Keycloak user ID, roles, verification and lock status, creation, update and last-login timestamps, and technical session data. The registration form also asks for a salutation with a “Prefer not to say” option and a password. Sign-in is handled by the Keycloak authentication system we operate. To join the closed Google Play test, the verified Google account email address is entered in Google Play Console after approval. A test account cannot be created without the required registration details. Tester approval uses a protected list. Optional analytics consent is not a condition of having an account.
For profile, goals, and calculations, Tijah processes data such as gender, birth date, height, current and target weight, activity level, fitness goal, training frequency, fitness level, preferred workout duration, weekly goal, excluded disciplines, calorie target, macro targets, water target, glass size, and time zone.
Depending on use, Tijah stores meals, foods, nutrition values, portion data, barcodes, weight entries, water entries, daily recap data, training goals, training plans, training times, completed sessions, sets, repetitions, duration, estimated calories burned, streaks, achievements, and favourites.
After a deliberate start, the Android app processes precise GPS positions for recording, including when switching apps or locking the screen. Raw points and recovery state are stored locally with Android Keystore encryption; the raw journal is not uploaded. Saved results synchronize duration, distance, suitable measured pace or speed, quality information, estimated calories, and any route reference with the account. Only a deliberate choice also uploads a reduced private track. Deliberately saved own or GPX-imported route templates also contain location geometry and remain account-bound. The server can decrypt authorized geometry requests; this is not end-to-end encryption. The R1 route display uses your own geometry without map matching, turn-by-turn or voice navigation. GPS and route values are not sent to AI providers, analytics, crash, or support systems.
The enabled R1 TEST integration uses Stadia Maps, Inc. for online maps. Deliberately opening a map sends the device IP address and requested map resources to Stadia Maps, revealing the requested map area. Your own geometry is displayed locally; the raw recording journal and Tijah account or session identifiers are not sent to the map provider. R1 import and route viewing request no place search, planning, GPX map matching, or automatic recalculation. Map requests use the EU endpoint tiles-eu.stadiamaps.com. This technical choice does not guarantee that all processing by the provider and its subprocessors occurs exclusively within the EU. Further information: stadiamaps.com/privacy/privacy-policy/, stadiamaps.com/legal/data-processing-addendum/, and stadiamaps.com/legal/subprocessors/. New online maps require a connection and confirmed map access. Your local geometry remains available without access; complete offline map packages are outside R1.
Before the first external AI use you explicitly request, the app separately asks for your optional AI consent. Health-data consent alone does not enable external AI. Without confirmed AI consent, the requested AI analysis is not started; manual features remain available while health-data consent is active.
The app contacts its Tijah app backend. That backend sends the contents required for explicitly chosen AI features to the Tijah-operated AI service hosted by STRATO in the EU, which forwards them to Cortecs GmbH, Althanstraße 4, 1090 Vienna, Austria, and the approved cloud path for GPT-6 Luna or Claude Haiku 5.5. The app and browser do not call Cortecs or the AI service directly. Depending on the feature, processing includes meal descriptions, ingredients, meal photos, nutrition and recipe details, sport and activity descriptions and the required profile, fitness and training context. This may include health data such as weight, personal goals, exertion or limitations. A pseudonymous account association is used between the app backend and the Tijah-operated AI service for requests and protection checks. Pseudonymous context and a Tijah-operated service do not anonymise contents; required contents may still identify people. The AI service forms part of the operation for which Tijah is responsible. Cortecs routes processing through approved Microsoft Azure, Amazon Web Services or Google Cloud paths. The Cortecs DPA names Microsoft Ireland Operations Limited and Google Cloud EMEA Limited (Ireland), and Amazon Web Services EMEA SARL (Luxembourg), with EEA processing locations. Cortecs uses OVH SA in France to host its router. This does not exclude third-country access, particularly from the US; the DPA lists the EU-US Data Privacy Framework as the transfer basis for those cloud processors. Zero Data Retention (ZDR) is required for request and response contents. Under its DPA, Cortecs processes routing contents in volatile memory and may retain operational metadata for up to twelve months. Technical schema/grammar caches and Tijah’s own retention must be distinguished from ZDR. The normalised schemas used by Tijah contain static structures rather than user or health values. The AI service does not add permanent prompt or photo copies or unredacted body logs. Briefly retained result records support reliable request processing and follow the described erasure rules. Necessary request and result records follow the retention and erasure rules described in this privacy notice. Please do not submit names, contact details, medical records or images of other people. The new explicit and optional Cortecs consent remains separate from health-data and analytics decisions; an earlier Venice consent does not replace it. Declining or withdrawing consent prevents new optional AI calls; manual core features remain available. Requests already started may still complete. Withdrawal does not reverse previous transfers or automatically erase stored data. The backend stores analysis events, model/status information, request/response data, results, image hashes and image artifacts for photo analyses. Internal diagnostic retention is configurable. The default periods for scheduled cleanup are 30 days for request/response content (redaction), 7 days for image files (deletion), and a configurable retention window of no more than 30 days for client traces. These periods control regular cleanup runs; backups are addressed in the “Retention, reset and deletion” section. The request and image retention periods relevant to your AI consent are shown in the app dialog. These internal periods are not a guarantee about external providers' retention. Barcode lookups send the entered or scanned EAN to the backend and to OpenFoodFacts to retrieve product information; product responses may be cached briefly on the server. For technical error investigation, the app also sends diagnostic events to Tijah’s own backend. These include the account association, operation and event identifiers, timestamps, elapsed times, error and HTTP status, network type, app version and platform. Separately enabled workout diagnostics also include technical planning and execution progress. These diagnostics are not anonymous statistics and are not controlled by optional Firebase consent. The client-trace periods above apply to their scheduled cleanup.
You can withdraw AI consent under Settings → External AI using “Withdraw AI consent”. New AI requests remain blocked on this device while withdrawal is not fully confirmed. When offline, the account-bound pending request is sent again when the connection returns or the app resumes; after an app restart, signing in again may be required. If a lost or incomplete response leaves it unclear whether an acceptance was saved, the app does not enable AI use. Choosing “Decline” then withdraws any consent that may already have been saved. Requests already started may still complete; transmissions already made cannot be reversed. Withdrawing only AI consent does not automatically erase stored content or withdraw health-data consent. You can request data erasure separately.
When premium or subscription features are used, Google Play Billing is the only purchase and subscription path for Play-distributed Android builds. Tijah processes the Google Play data required for server-side verification, including purchase tokens as hashes and encrypted values, product, base plan, offer, purchase and subscription status, runtime, expiry, renewal and entitlement status, acknowledgement status, technical synchronization and error data, and support or order references where needed for traceability and support. Payment instruments such as card, account, or bank data are processed by Google Play; Tijah does not store them and does not offer an external web checkout for digital Premium features.
The app uses local storage for offline features, synchronization, reminders, settings, caches and technical state. This includes SQLite, Capacitor Preferences, LocalStorage, SessionStorage and file system access for video caches. On this device, we store the status of unresolved health-data and AI decisions and withdrawals against the relevant account, so restrictions and pending transmissions can be restored after an app restart. This storage does not grant additional consent. Where storage or access is strictly necessary to provide a feature you explicitly request, we rely on Section 25(2)(2) TDDDG; optional analytics access requires separate consent under Section 25(1) TDDDG. Subsequent processing of personal data also requires the GDPR legal basis described in the relevant section. We use the camera, photo library, location and notifications only within the selected features and the required device permissions. An Android permission is a technical permission and does not replace health-data, AI or analytics consent. Manual entries remain available without camera permission; the corresponding reminders are not shown without notification permission.
You can choose to watch a YouTube video on the home page. For users in the European Economic Area, the provider is Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. We load the player in privacy-enhanced mode via youtube-nocookie.com only when you select a video start button. Before that, neither the player nor a preview image is loaded from YouTube. On activation, Google receives data including your IP address, browser and device information, the referring website, and information about the video and its playback. Privacy-enhanced mode does not mean that no personal data is processed. Activation is based on your consent under Article 6(1)(a) GDPR and, where information is stored on or read from your device, section 25(1) TDDDG. It is independent of your Google Analytics choice. The rest of the website remains available without activating the video.
Google may also process data in the United States and other countries. Google explains the transfer mechanisms it uses, including the EU-US Data Privacy Framework and standard contractual clauses, in its data transfer information. See Google's privacy policy for information about recipients and processing by YouTube.
We do not save permanent video consent or automatically activate the player on a new page visit. Selecting “Stop video” removes the player and stops further connections through this embed. It does not retrospectively delete data already transmitted. Google's retention depends on the type of data, processing purpose and your Google settings; Google's privacy policy explains the details and deletion options.
Google Analytics 4 is used on the public website only with optional consent (section 25(1) TDDDG and Article 6(1)(a) GDPR). Its purpose is statistical evaluation of page views and interactions such as language selection. Data includes visited pages, page titles, referral source, timestamps, browser/device information, approximate region and pseudonymous cookie identifiers. Google technically receives your IP address when a connection is established. The provider is Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland; accepted data processing terms are in place.
GA4 uses _ga cookies to distinguish browsers and _ga_<identifier> cookies for session state. Our tag limits their lifetime to 180 days without extending it on every page view; browsers may enforce shorter periods. Advertising storage, advertising user data, ad personalization and Google Signals are not enabled for the website tag.
In the verified property, event data is retained for 2 months and user data for 14 months. New user activity restarts the user-data retention period. These periods concern user/event records and do not automatically apply to aggregated standard reports.
Google may use affiliates and subprocessors, including Google LLC in the United States. For transfers to Google LLC covered by its certification, the EU-US Data Privacy Framework and its adequacy decision under Article 45 GDPR provide the transfer basis. Google’s data processing terms also provide standard contractual clauses.
Without consent, no Google Analytics script, analytics measurements or consent pings are loaded. Your choice is saved on this device for 180 days with its timestamp and information version, without an additional user identifier. We ask again after expiry, a new information version or deletion of the choice. You can reject or withdraw just as easily at any time through “Cookie settings” in the footer; this stops future measurements in other open website tabs as well. Processing before withdrawal remains unaffected. You can use the website without analytics.
In Android builds in which the integration is enabled, Tijah uses Google Analytics for Firebase only after your own optional opt-in in app settings. This integration is disabled in TEST and debug builds. Its purpose is statistical analysis of app usage and technical processes; the legal bases are Article 6(1)(a) GDPR and Section 25(1) TDDDG. Once enabled, the SDK also processes automatically collected usage events, such as app starts and sessions, a pseudonymous app-instance identifier, and technical app and device information. Google receives the IP address when a connection is established and may derive an approximate location from it. Events added by Tijah are limited to technical consent and debug events; they contain no Tijah account or user identifiers, email addresses, meals, photos, weight, calorie, health, GPS or route values. These limits on custom events do not mean the SDK operates without identifiers. Advertising ID collection, advertising storage and ad personalization are not enabled. Without app consent, collection remains disabled. Withdrawal in app settings disables it again and resets local analytics data; this does not automatically erase all data already stored by Google. Website and app choices apply separately. The Android and website data streams belong to the same Google Analytics property. In this property, checked on 2 November 2026, event data is retained for 2 months and user data for 14 months. “Reset on new user activity” is enabled: new activity restarts the user-data retention period. Google removes expired user and event data through its regular deletion process. These periods do not automatically apply to aggregated standard reports. Technical diagnostics sent to Tijah’s own backend for error investigation are described in “AI analysis, photos and barcodes” and are not controlled by the Firebase switch. The provider is Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. The information about Google recipients and international transfers in “Website analytics and cookies” also applies to this analytics service.
For hosting the website and server services, we use STRATO GmbH, Otto-Ostrowski-Straße 7, 10249 Berlin, Germany. This includes the app, database and Keycloak authentication services we operate; Keycloak is the software used, not an additional external sign-in provider. STRATO also hosts the info@tijah.me and support@tijah.me mailboxes and is used to send verification and support messages. Incoming messages to our configured tijah.me mailboxes and their aliases are forwarded to our business mailbox under Google Workspace Business Starter. Google processes this correspondence as a processor; this also includes contact form enquiries addressed to support@tijah.me. Details are provided in “Contact enquiries”. Other recipients are Google Play for payments, store listing, test access, installation and updates, Cortecs GmbH and the subprocessors identified for the specifically approved model path for explicitly enabled AI features, and OpenFoodFacts for product and barcode lookups. Stadia Maps is integrated only for the enabled Outdoor map features described above. Google Analytics on the website and Google Analytics for Firebase in enabled Android builds are used only after the respective separate analytics consent. The relevant sections describe the data transferred and the choices available. Personal data is not sold. Phase 1 and Closed Testing do not include Ad-SDKs, ad networks, advertising placements, sponsorship, affiliate placements or cross-promotion placements. The Tijah-operated AI service hosted by STRATO in the EU forms part of Tijah’s operation; a Tijah-operated service does not anonymise contents or replace information about external AI recipients.
Data is stored as long as it is required for the account, app features, security, billing, legal obligations, or traceability. The app includes reset functions for selected data areas such as profile, training, or workout data. A full account or data deletion request can be submitted through https://tijah.me/delete-account or support@tijah.me. Deletion requests are reviewed; assignable app data is deleted or anonymized unless legal retention duties or security and billing records require continued storage. Outdoor raw points are removed after the result and any requested private track have been saved durably, or after deliberate discard; running or recoverable recordings remain protected. Results awaiting synchronization are not discarded after 24 hours. Activities, tracks, and route templates have separate deletion actions; deleting an activity removes its track, while deleting a template does not remove every saved activity copy. Provider data remains available only within its usage period. Failed file transfers are cleaned up immediately; other temporary GPX/PNG exports are checked for deletion once they are 24 hours old during the next permitted background execution or app start. System deferral can delay actual deletion. Copies in receiving apps remain outside Tijah’s control. Signing out clears local Outdoor data but preserves server history. Deletion from active server storage does not immediately remove every offline-device or backup copy; no effective binding maximum retention period has yet been verified for all server copies. You can withdraw health-data consent in the Health data section of the app settings using “Withdraw consent”. The app blocks the affected features, stops running recordings and discards pending transfers. When offline, withdrawal remains pending locally and is retried with the server. Server confirmation of health-data withdrawal also revokes any existing AI consent. After server confirmation, erasure of the affected active health data, including associated analysis content and result snapshots, is processed; these features remain blocked until cleanup is confirmed. Unconfirmed steps and errors remain visible. Giving consent again does not restore erased data. Withdrawal does not affect the lawfulness of earlier processing. Necessary consent evidence and required security, billing and separately submitted support records may be retained on another valid legal basis. Account deletion remains a separate option. Backups and data already transferred to external recipients follow their separate erasure and retention procedures; immediate erasure of every copy is not promised.
Tijah and participation in the alpha/closed test are intended exclusively for adults aged 18 or over. We check the supplied date of birth during registration. People under 18 may not newly register for test access. An app store content rating is separate from this participation and target audience policy.
Tijah is prepared as a fitness and calorie app. The information does not replace medical advice, diagnosis, or treatment and does not guarantee weight, calorie, or training outcomes. Users should discuss health questions with qualified professionals.
Subject to the legal requirements, you may request access and a copy of your personal data, correction, erasure, restriction of processing and data portability. Where we rely on Article 6(1)(f) GDPR, you may object under Article 21 GDPR on grounds relating to your particular situation. You may withdraw consent at any time for the future; this does not affect earlier lawful processing. App settings provide direct controls for health data, external AI and app analytics; website analytics can be managed through “Cookie settings” in the footer. For other requests, contact support@tijah.me. You also have the right to lodge a complaint with a data protection authority, particularly where you habitually live, work or believe an infringement occurred. The authority responsible for our place of establishment is the State Commissioner for Data Protection of Lower Saxony, Prinzenstraße 5, 30159 Hannover, Germany; information and complaint form: https://www.lfd.niedersachsen.de/beschwerde. You do not have to contact us first to exercise this right.