This Privacy Policy describes the processing of personal data implemented by Timkelo across the mobile application and the timkelo.com website, in compliance with the General Data Protection Regulation (GDPR) and applicable data protection legislation.
1. Data controller
The data controller for personal data is:
Keroan MICHEL, sole proprietor, trading as Timkelo
Legal status: Sole proprietorship (micro-entrepreneur under French law)
Professional address: 8 rue Fernand Pelloutier, 92110 Clichy, France
Registration: SIREN 911 178 457 (RCS Nanterre)
Official website: https://timkelo.com
General and privacy contact: legal@timkelo.com
The operator is not subject to a statutory requirement to appoint a Data Protection Officer (DPO). For any enquiry regarding personal data or to exercise your rights, you can contact the operator directly at legal@timkelo.com.
2. Data, purposes and legal bases
Account and authentication
Data: email, internal ID, username, profile details, verification status, sign-in dates and Terms acceptance. Passwords are handled in protected form by Supabase Auth. Apple or Google sign-in transmits the identifiers and tokens required for authentication.
For Apple, a short-lived authorization code is exchanged server-side. The refresh token strictly needed for revocation is encrypted in Supabase Vault and removed after revocation or account deletion.
Purpose/basis: account creation, security and operation: performance of the contract; abuse and fraud prevention: legitimate interests.
Profile, social network and moderation
Data: avatar, username, display name where provided, bio, visibility settings, friends, requests, blocks, reports, posts, comments, mentions, likes, saves and notifications.
No personal activity is posted automatically. A post or share results from an action by the user.
Purpose/basis: social features and user choices: contract; moderation, security and legal defence: legitimate interests and applicable legal duties.
Public creators directory (Timkelo Creators)
Data: public name or pseudonym, professional country where publicly declared, language, positioning, specialties, links to public profiles, original factual description, covered parks and universes. An unclaimed profile is clearly flagged and is never an official partnership.
No photo, protected biography, video or private statistic is imported automatically. The owner can claim the profile; anyone can request a correction, an objection or a removal through the form provided on the profile. The contact email is never published.
Purpose/basis: public presentation of specialised content creators: legitimate interests.
Ambassadors programme
Data: identity and contact details, professional information (company name, legal form, SIRET, VAT number where applicable), country of establishment, account status, referral code, aggregated clicks and eligible purchases observed server-side.
Bank details: the IBAN and account holder are not requested during the application. They are collected only when a payment is due, kept with restricted access (administrator only) and never published.
Purpose/basis: running the referral programme and performing the contract; accounting and tax duties; fraud prevention: contract, legal obligations and legitimate interests. No payment is released without a compliant invoice.
Map, parks, attractions and memories
Data: saved parks and attractions, completion status, dates supplied by the user, ratings, comments, photos and recaps created voluntarily.
Device location is never publicly exposed. Foreground location may be requested on a one-off basis (never in the background), with your prior explicit permission, to suggest nearby places or verify a ride completion on site. Refusing location permission never blocks recording a ride log (which falls back to declared status). Precise GPS coordinates are never stored in the database: only the verification outcome and timestamp are recorded on the server.
Purpose/basis: personal map and log: contract; optional location and motion data: prior consent via device permissions.
Messaging
Data: participants, text messages and read dates. Timkelo does not permit photos, video, audio or files in conversations. Accepted friends can message directly. A request and mutual acceptance are required for non-friends where a connection context is offered.
Purpose/basis: requested communications: contract; blocking, reporting and abuse prevention: legitimate interests.
Subscriptions and Premium purchases
Data: pseudonymised user ID, subscription status (monthly or lifetime), rights history synchronised by RevenueCat. Financial transactions are processed exclusively by Apple (App Store) or Google (Google Play Store); Timkelo never receives or stores full payment card numbers.
Purpose/basis: delivering and maintaining Premium features: performance of the contract; accounting records and tax compliance: legal obligation.
Contacts and friend discovery
Timkelo does not request access to your address book and does not upload contacts.
Purpose/basis: finding acquaintances: consent, withdrawable in device and Timkelo settings.
Website, waitlist and contact
Data: email and language for the waitlist; email, optional name, subject and message for contact; local language preference; technical logs, IP address and request information processed by hosting providers.
Purpose/basis: requested updates: consent; responding to enquiries : pre-contractual steps or legitimate interests; security and availability: legitimate interests.
3. Planned visits and meetups
A planned visit records at least a park and date. It is a statement of intent and does not prove actual presence or disclose real-time location.
Subject to visibility rules and eligibility (strictly reserved for adults aged 18 and older), Timkelo may display participant counts and permitted profiles (friends or, for Premium members, other adult members planning a visit on the same date). Timkelo does not provide any collective group discussions or chat rooms. Planning a visit and requesting a 1-on-1 private connection are two distinct steps. A private conversation with a non-friend requires a contextual request and affirmative acceptance. User blocks always take precedence.
Official “Timkelo Visits” are shown only in areas where they are actually available.
Purpose/basis: planned visits and chosen interactions: performance of the contract; individual contact requests: affirmative user action.
4. Media, storage and visibility
Avatars, post images, memories and certain editorial media are stored in Cloudflare R2 with a server inventory row in the media table. Ready R2 objects are currently delivered through public URLs; do not upload confidential material there.
Historical messaging attachments, if any, may remain in a private Supabase Storage bucket and server inventory. No new upload is permitted and the application no longer requests access URLs for these files. Historical data remains until deletion or a validated retention policy applies.
On account deletion, the server inventories objects attributed to the user, attempts physical deletion and does not report complete erasure if an R2 purge fails. R2 keys missing from the server inventory are never deleted solely on client input.
5. Providers and recipients
Data is available to other members only as permitted by the relevant feature and visibility rules, to authorised publisher personnel, and to necessary providers:
- Supabase (Supabase, Inc., United States): database, authentication, realtime, Edge server functions, Vault secret storage and files;
- Cloudflare (Cloudflare, Inc., United States): website hosting, CDN, network protection and R2 image storage;
- Apple and Google (Apple Distribution International Ltd., Ireland and Google Commerce Limited, Ireland): authentication, app distribution and platform payments;
- RevenueCat (RevenueCat, Inc., United States): offerings, synchronising Premium entitlements with the Supabase identifier, purchase state, restoration and subscription lifecycle;
- Google AdMob and Google AdSense (Google Ireland Limited, Ireland): consent collection via certified IAB TCF v2.2 CMP, ad serving, measurement, and fraud prevention (AdMob in the free mobile app, AdSense on editorial website articles);
- Google Fonts (Google Ireland Limited, Ireland): delivery of website fonts, which transmits technical connection data;
- Expo (650 California St, San Francisco, United States) and Google Firebase FCM (Google Ireland Limited, Ireland): push-notification infrastructure and push tokens where enabled;
- OpenFreeMap: open map tile requests and associated connection data;
- judicial or administrative authorities or legal advisers where required by law, an enforceable order or legal defence.
Timkelo does not sell personal data. In the free app, AdMob is initialised only when configuration and, where required, UMP consent permit ad requests. Premium members do not receive ads under the current implementation. Advertising choices can be reopened from settings when required by Google.
Purchases are contracted with Apple or Google. RevenueCat synchronises Premium rights with the Supabase identifier; Timkelo does not receive the full payment-card number.
7. Retention periods
Personal data is retained only for as long as strictly necessary to fulfill the purposes for which it was collected, in compliance with applicable statutory obligations:
- Account data, profile, and active content: Account information (profile, posts, photos, memories, ride log history, planned visits, friendships, and direct messaging) is retained throughout the active life of the account. Upon account deletion requested by the user, active database rows and media objects stored in Cloudflare R2 are deleted immediately. Encrypted technical database backups are maintained by infrastructure providers (notably Supabase) on a rolling cycle estimated at 30 days for disaster recovery purposes only, before being permanently and cyclically overwritten.
- Technical logs and IP addresses: Network and API traffic data (IP addresses, HTTP requests, timestamps) are processed for operational security, fraud prevention, and DDoS mitigation, for an indicative rolling period not exceeding 30 days at the infrastructure provider level. Where a statutory obligation to retain connection identification elements applies or upon formal judicial requisition issued by a competent authority, only strictly required data is preserved or communicated within the framework required by law, without generalized automatic archiving of raw activity logs.
- Contact form requests: Messages submitted via the website contact form are retained for the time necessary to handle the request, and archived for a proposed indicative period of up to 3 years from the date of last contact (in line with French CNIL prospect and contact management recommendations).
- Content reports and moderation records: Reports of content or profiles and associated moderation decisions are retained for the processing duration of the measure and up to 1 year following the decision, to ensure appeal follow-up and fulfill accountability obligations under the EU Digital Services Act (DSA).
- Age and country compliance audit records: Compliance audit logs and age/country correction requests (
profile_compliance_auditandcompliance_change_requests) are subject to a technically enforced automated purge after 2 years from creation, to document compliance with statutory child protection obligations. - Contextual Visit connection requests: Pending contact requests between participants planning the same Visit expire technically and automatically 24 hours after the planned visit date if unaccepted, and are purged upon account deletion.
- Launch waitlist: Email addresses collected during pre-launch registration are retained during the pre-launch phase until the official launch notification email is sent, or until immediate unsubscription by the user via their individual unsubscribe link (and no later than 3 years from collection).
- Subscriptions and financial records (RevenueCat, Apple, Google): Timkelo never stores payment card numbers. Purchase records and subscription entitlements synchronised via RevenueCat are maintained for the active subscription period plus applicable statutory accounting and tax limitation periods (10 years for accounting records under Article L. 123-22 of the French Commercial Code).
- Push notification tokens and digital passes: Push tokens (Expo/FCM/APNs) and Apple Wallet / Google Wallet passes are retained while the account remains active and are deleted immediately upon sign-out or account deletion.
8. Your rights and account deletion
Subject to the GDPR and your circumstances, you may request access, correction, erasure, restriction, objection and portability, and withdraw consent without retroactive effect. You may complain to the CNIL or your competent supervisory authority.
Deletion is available in the app and on the Account deletion page. Recent reauthentication is required. For Apple accounts, Timkelo first attempts server-side revocation; inability to revoke is reported and deletion is not presented as complete.
Deleting a Timkelo account does not necessarily cancel a subscription billed by Apple or Google. The user must manage it in the relevant store settings.
9. Security and international transfers
Timkelo uses Supabase row-level security (RLS), isolated server functions, secret separation and encryption in Supabase Vault, and systematic encryption in transit (TLS/HTTPS). No measure can guarantee zero risk.
Certain essential technical processors (notably Supabase Inc., Cloudflare Inc., RevenueCat Inc., and Expo / 650 Industries) are established in the United States. Transfers of personal data to these processors are governed either by the adequacy decision regarding the EU-U.S. Data Privacy Framework for certified entities, or by Standard Contractual Clauses (SCC) adopted by the European Commission pursuant to Article 46.2.c of the GDPR. These contractual safeguards are supplemented by technical security measures, including transport encryption (TLS/HTTPS), encryption at rest of sensitive credentials within Supabase Vault, and strict data minimisation.
10. Minimum age and minor protection
Universal minimum age: 16 years. Timkelo is strictly prohibited for persons under the age of 16. Registration is blocked below 16 and no data from children under 16 is knowingly processed. If an account held by a person under 16 is identified, access is immediately blocked.
Protection of users aged 16 to 17: adolescents aged 16 and 17 benefit from a strictly protective, guarded environment:
- Recording and publishing their memories according to implemented visibility rules (personal log, attraction history, associated photos), without any unconsented social broadcast.
- Their planned visits are strictly private and invisible to all other users.
- They have no public profile, cannot be discovered in search, cannot receive contact requests, and cannot add friends.
- They have no access to private messaging, social interactions (reactions, comments), or shared Visits.
- No advertisements are served to minors and Premium subscriptions are inaccessible to them.
- Content recorded during minority remains isolated and private by default upon reaching 18, with the ability to voluntarily and individually publish them at a later time.
Territory availability: Timkelo is available at launch across the 20 priority countries (France, United States, United Kingdom, Germany, Netherlands, Belgium, Canada, Poland, Denmark, Sweden, Australia, Ireland, Norway, Finland, Switzerland, Austria, Spain, Italy, Singapore, Portugal). All other territories remain currently unsupported pending future expansion.
11. Contact and updates
For any enquiries regarding personal data protection or to exercise your rights (access, rectification, erasure, restriction, objection, portability): by email to legal@timkelo.com or by postal mail to: Keroan MICHEL (Timkelo), 8 rue Fernand Pelloutier, 92110 Clichy, France.
You also have the right to lodge a complaint with your competent supervisory authority, including the French Data Protection Authority (CNIL: 3 Place de Fontenoy, TSA 80715, 75334 Paris Cedex 07: cnil.fr).
Material changes will be brought to users’ attention and, where required, renewed acceptance or consent will be requested.