MyHeadshot
Privacy policy — The Mate Club
Last updated: 2026-10-20
About this policy
The Mate Club is operated by Totem Studio International Technologies S.L. in Spain. The Mate Club provides MyFoodMate, MyChefMate, MyBodyMate, MyHeadshot and MyScanner. This notice describes the shared account features in our updated apps. Features available in older versions or without a shared account may differ. Contact the operator of The Mate Club in Spain at hola@themateclub.app for privacy questions.
Your account and optional Totem connection
Firebase Authentication processes your account identifier, email, sign-in provider and, when supplied, display name. Email/password, Apple and Google are supported. A shared account identifies you across our apps and supported platforms. Your provider handles its own sign-in process.
Connecting Totem is optional. That connection exchanges a verified account identifier and current paid-access status to check whether membership is included. It does not import your Totem workspace, conversations or files. Totem remains a separate service.
Shared profile and synchronization
When you choose shared synchronization, we store the profile fields you supply, nutrition targets, food records and body-weight entries in your Mate Club account. These can include date of birth, height, weight, sex, activity and dietary preferences. Compatible Mate Club apps on your devices can read the relevant shared records. Planned meals remain separate from meals confirmed as eaten.
The account database is hosted in Google Firestore in Europe. Our existing Firebase file-storage bucket is in the United States. A European database does not mean every service or uploaded file stays in Europe. Local and offline copies also remain on your devices.
MyHeadshot photos and facial information
Photos and generation settings you select are sent to Replicate to create the requested portrait. We store owned inputs and generated results in Firebase file storage so the shared gallery can recover across devices; account/job records track processing and credits. We do not create a face-recognition identity database or use your portraits for advertising. Portrait photos can contain sensitive information: upload only images you have permission to process. Gallery deletion requests remove owned files through the processing/deletion workflow; minimal transaction and request records can remain to prevent duplicate debits.
AI assistants and analysis
Supported devices can use an on-device assistant. Before cloud chat is used, the app asks permission to send the displayed conversation context. Cloud chat goes through our n8n service in Spain to the OpenAI API using GPT-6-Luna. Ordinary shared chat sends recent messages; it does not automatically attach your health profile.
MyChefMate can additionally send the cooking and shared-profile context shown in its consent screen, including body measurements and nutrition targets, selected images, diet/allergen preferences, and a limited selection of saved recipe titles and ingredients. Food or recipe analysis sends the image, text or web address you choose for that feature. Do not submit information about someone else without permission.
Our n8n workflow is configured not to save execution payloads. OpenAI requests disable response storage; this does not eliminate the provider’s separate security and abuse-monitoring retention. Chat history is saved in your account-specific device storage. The server saves request identifiers, states, content hashes and completed replies to recover interrupted work without generating a second paid response.
Purchases and membership
Apple, Google Play and RevenueCat process purchase identifiers, account identifiers, product and transaction information, entitlement status and refunds. We do not receive your full payment-card details. A suite membership can unlock compatible apps on both platforms; existing individual-app purchases remain separate. Optional Totem access and direct store access are verified independently. Deleting an account does not cancel a store or Totem subscription: manage it with the provider that bills you.
Diagnostics and analytics
Firebase Crashlytics receives crash traces, installation identifiers, device/app versions and technical diagnostics. Google Analytics for Firebase receives app-usage events and installation/device information when collection is enabled. Our operational events exclude chat text, photos, nutrition records and body measurements. You can change the separate analytics and crash-reporting settings in the app. These services are not anonymous in the absolute sense: installation identifiers can distinguish an installation.
Existing device, iCloud and original-app data
Original versions may keep data locally, in iCloud or in an app-specific service. Signing in to a shared account does not silently assign all existing history to that account. Where offered, review the explicit import or original-account connection. Unlinked original accounts, private iCloud data, Health data and device exports can require separate deletion in their original location. Signing out keeps the histories of different shared accounts isolated on the device.
Retention and deletion
Shared records and files remain until you delete them or request account deletion, subject to pending processing and records needed to reconcile purchases, prevent duplicate charges and meet legal obligations. Minimal request markers are kept separately from chat replies; automatic thirty-day reply deletion is not currently promised. Account deletion locks the account first and then removes its owned database records, files, connections and authentication account. It cannot erase copies you exported or data held in an unlinked original service.
Our providers have their own deletion schedules. OpenAI documents default API abuse-monitoring retention of up to thirty days, with exceptions. Replicate documents automatic deletion of API prediction inputs, outputs and logs after one hour by default. Firebase documents ninety days for Crashlytics traces and associated identifiers before removal begins. These schedules do not delete copies we store to provide your account or gallery. Contact us for help with access, export, correction or deletion.
Your choices and rights
We process information to provide the features you request, protect the service, administer purchases and comply with applicable obligations. Where consent is required, you can decline or withdraw it for future processing in the relevant feature or settings. Health-related information is not used for advertising or eligibility decisions. We do not sell your personal information.
Depending on your location, you may request access, correction, export, deletion, restriction or objection, and complain to your data-protection authority, including the Spanish AEPD. Contact hola@themateclub.app; we may need to verify account ownership. Necessary security and purchase records may be retained when required. The apps are not directed at children under thirteen.
Security and international processing
We use encrypted network transport, account-based access controls and app-attestation checks. Cloud synchronization is not end-to-end encrypted with a key held only by you. Google/Firebase, OpenAI, RevenueCat, Apple, Google Play and, for portraits, Replicate may process information outside your country. Their service terms and applicable transfer safeguards govern that processing. No system can guarantee absolute security.
Updates and contact
We will update the date of this notice when our practices change and provide additional notice or permission requests where needed. Privacy contact: hola@themateclub.app. Provider details: firebase.google.com/support/privacy; developers.openai.com/api/docs/guides/your-data; replicate.com/docs/topics/predictions/data-retention; revenuecat.com/privacy.