Legal

Privacy policy.

What we collect, why, who can see it, who we share it with, how long we keep it, and how you stay in control.

Version 2.1 · Effective 15 October 2026 · Last updated 15 October 2026

1. Who we are

twekes is a running app for iPhone and Android, the website twekes.com and the partner portal at twekes.com/partners (together, the "Service").

The Service is provided by Marc Tanas, an individual, Bitar Street, Msaytbeh, Beirut, Lebanon ("twekes", "we", "us"). We decide why and how your personal data is used, so we are its controller.

2. The short version

3. What we collect and why

3.1 Your account and how you sign in

WhatWhy
Email address and password. Our sign-in provider (Supabase Auth) stores only a secure hash of the password; nobody at twekes can read it.To create your account, sign you in, reset your password, and send you service emails (for example the confirmation that your account was deleted).
Display name and handleSo other runners can recognise you.
The version and date of the Terms you accepted, including your confirmation that you are 16 or olderTo apply our minimum age and keep a record of what you agreed to.

Sign in with Apple (iPhone). You can create an account or sign in with your Apple Account instead of a password. Apple confirms who you are to us. We never receive your Apple Account password. From Apple we receive:

We receive no contacts, payment details or other data from your Apple Account.

3.2 Your profile

Optional fields: profile photo, city, area, bio, run types, other sports, interests, preferred run areas, date of birth, and a home pin on the map. You decide what to fill in.

WhoWhat they see
Everyone, including people without an accountYour name, photo, city and bio, and your follower counts
Runners you are connected with (you follow each other, or you have exchanged messages)Also your area, run types, interests and preferred run areas
Nobody elseYour date of birth and home pin are never shown to other people

The athletes directory. Runners are listed in the athletes directory by default, so other people can find you by name or handle in search. Today you cannot switch this off in the app. Ask us through Send feedback or at info@twekes.com and we will remove you.

We use your home pin to suggest after-run places near you when your live location is not available.

3.3 Location

twekes uses your phone's location only while you are using the app. It never tracks you in the background. It does not ask for "Always" location, and background location is blocked in the Android app. You can refuse or withdraw location permission in your phone's settings at any time. The map then starts from a default city, and you can move it yourself.

When we ask. Explore asks once, the first time you open it. Other screens ask only when you tap something that needs your location.

How we use it, and how precisely:

UseWhat we receive
Explore mapOnly the map area you are looking at, not your position
Home and Community "near you"Your position rounded to about 1 km
After-run suggestions and the area of a MomentYour position rounded to about 100 m
Moment area tagWe keep only the neighbourhood-sized area and its name, never the point. You can switch the tag off for each Moment.
Collecting a perk stamp at a partner venueYour exact position, used once to confirm you are at the venue. We keep only your distance from the venue with the stamp, not your position.
Ask twekes, when "Use my location" is onYour exact position, used on our server only to rank nearby results. It is not passed to Anthropic (section 7).

Pins you place yourself:

The "Use my location" switch (Privacy & settings, off by default) lets the app use your live position to sort nearby clubs and places, and to tailor Ask twekes. When it is off, those lists use your home pin if you set one. It does not stop the screens in the table above from using your rounded location while your phone allows location. To stop all location use, withdraw the permission in your phone's settings.

Other location data:

3.4 Runs and activities

We store runs you log by hand and the workouts synced from the services you connect (sections 4 and 5). For each one: the type of activity, date and time, distance, duration and pace, the app or device that recorded it, and, where the source provides them, heart rate, calories, elevation and the route. Strava routes are not stored.

What we use runs for:

Only runs count as runs. Other workouts your watch or health app sends (for example strength training, cycling or walks) are stored with your activities but do not appear in your runs, stats or leaderboards.

Deleting runs. You can delete a run you logged by hand: open it in My Running and tap Delete run. A synced run shows where it came from and cannot be deleted in the app, because the next sync would bring it back. To have synced runs removed, ask us at info@twekes.com.

Public runs. In Privacy & settings you can choose whether new synced runs are private (the default) or public, and how much detail a public run shares: distance and time, or at "Full details" also pace, heart rate, climb and energy. No screen in the app shows other runners' individual runs today, but other signed-in twekes accounts can still retrieve the details of runs you made public, with your name and handle, from our database. Routes are never included. Keep runs private if you do not want this.

3.5 Moments, photos, videos and sound

Moments are photos and short videos, with sound if you allow the microphone. A Moment has:

Who sees a Moment. Moments are for people signed in to twekes.

Location metadata. When you upload a Moment, our server removes the location and other metadata embedded in the file. Photos are re-encoded; video location data is stripped.

Other photos. Your profile photo, club photos, business cover photos and screenshots attached to feedback are stored in storage that is reachable by anyone who has the exact link. For these photos, the current app re-encodes the image on your phone before upload, which normally drops embedded metadata such as location. Videos, and photos uploaded from older app versions, are stored as they were uploaded.

Camera, microphone and library.

3.6 Messages

Direct messages, club chats and run chats (text only) are stored so that the people in the conversation can see them. Our moderators can read a message when it is reported to them.

3.7 Clubs, runs and sessions

3.8 Ask twekes

See section 7.

3.9 Support, feedback and requests

3.10 Safety and moderation

3.11 Diagnostics

We do not use third-party analytics or crash-reporting tools. The app itself sends us two things:

We use both only to find and fix bugs and slow screens. How long we keep them: section 14.

3.12 Device and notifications

Push token. We store a push notification token for your phone so we can send you notifications.

What notifications contain:

Notifications are delivered through Expo and through Apple's or Google's push services.

App updates. The app checks Expo's update service for new versions. This sends your app version, platform, a random install identifier and your IP address to Expo.

3.13 Partners, experts and club managers

Listing data. If you list a business, an expert profile or a club, we collect what you enter: name, category, address and map pin, opening hours, perks, description, photos, Instagram handle, and contact details (phone, email, website).

ListingWhat is publicWhat is not
Business and club listingsShown in the app and in search—
Expert profilesName, photo, types, region, bio, specialties and Instagram are publicEmail and phone go only to signed-in runners, one profile at a time

Partner sign-up and portal.

Emails to partners. We email partners about their listing (approved, or changes requested) through our email provider, Resend.

Club Instagram. A club that connects its Instagram account lets us store an access token and show its recent posts.

3.14 The website

3.15 What we do not collect

4. Health and fitness data from your watch and phone

Connecting a watch or a health app is optional. You choose what to connect in Profile → Privacy & settings → Connected devices. Because this data can reveal information about your health, we treat all of it as health data, and we use it only with your explicit consent, which you give when you connect a source and grant its permissions (section 13).

4.1 Sources, what we read and what we keep

SourceHow it reaches twekesWhat we readWhat we keep
Apple Health on iPhone, including Apple Watch workouts (the Apple Watch and Apple Health rows share one connection), and COROS workouts that the COROS app saves to Apple HealthRead on your iPhone with the permissions you grant in Apple Health. New data goes through the ROOK software built into twekes to ROOK, and then to us; new workouts can sync in the background. The first time you connect Apple Health on a phone, the app also sends your past running workouts from Apple Health straight to us, once, because ROOK brings only new data.Workouts, workout routes, walking and running distance, active energy, heart rate. Read only: twekes never writes to Apple Health.
  • Your workouts: type, date and time, distance, duration, calories, heart rate where available, and the app or device that recorded them. The one-time import of past workouts brings runs only.
  • Routes: for workouts that ROOK sends, and for imported runs from the last 90 days.
  • Daily summaries and heart-rate readings that ROOK builds from the data you allowed. We store them as received, for 30 days (section 14); no twekes feature uses them today.
Health Connect on AndroidRead on your phone with the permissions you grant in Health Connect, through the ROOK software, to ROOK and then to us. New workouts can sync in the background, so they arrive without you opening the app. Health Connect lets twekes read data from up to 30 days before you connect.Exercise sessions, distance, heart rate, elevation gained, active calories burned, total calories burned. Routes are not requested.Your workouts (as for Apple Health, without routes), and the daily summaries and heart-rate readings ROOK sends, stored as received for 30 days and unused.
Garmin (and Polar, Fitbit, Oura and Withings for runners who connected them earlier; the app no longer offers them, but lists them until you disconnect)You authorise the brand to share with ROOK; ROOK passes the data to us.Activities: type, time, distance, duration, pace, heart rate, calories, elevation and route where available.Your activities. The brand may also send ROOK daily summaries: steps, sleep, body measurements such as weight, resting heart rate and heart-rate variability, and nutrition. ROOK passes these to us, and we store them as received for 30 days, but no twekes feature uses them.
StravaOur own connectionSee section 5See section 5

ROOK (ROOK Motion) is the service provider that syncs wearable data for us. ROOK identifies you with your twekes account ID and processes the data on our behalf. Under ROOK's terms, ROOK may also use aggregated, de-identified data for its own analytics and product improvement.

4.2 How we use it

4.3 What we never do with it

4.4 Apple Health (HealthKit)

4.5 Health Connect

4.6 Your controls

5. Strava

Connecting Strava is optional. twekes is not developed, sponsored or endorsed by Strava.

6. Turf, leaderboards and what is public

These totals never include Strava runs. Other runners never see your routes, starts or finishes. People without an account do not see leaderboards or your stats.

7. Ask twekes (AI)

Ask twekes is an AI assistant. It answers questions about running where you are, using published twekes listings (clubs, sessions, runs, places to run, after-run places, races, experts and areas). It is provided by Anthropic, using Anthropic's Claude models; Anthropic processes the data on our behalf.

What we send to Anthropic:

Your training summary covers:

It excludes Strava runs, heart rate, routes, exact locations, your home pin and area.

Not sent: your email, your account ID, your messages, your exact location, your routes, your Strava data.

On our servers. If "Use my location" is on, the app sends your position with the question, so that we can rank nearby results. We do not pass it to Anthropic. We do not store your question; our logs record only its length, the number of results and timings.

At Anthropic. Anthropic keeps and deletes this data under its own published terms. At the time of writing, Anthropic's commercial terms say that it may not train its models on this content, and Anthropic states that it deletes API inputs and outputs within 30 days, unless they are flagged for a breach of its usage policy (then up to 2 years) or the law requires it to keep them longer.

On your phone. Your Ask twekes conversations (the 20 most recent) are stored only on your phone. They are removed when you sign out or delete your account.

Answers can be wrong. Check times, places and advice before you rely on them.

Report answer.

Without an account, Ask twekes receives only your question, your city and the listings; there is no personal summary.

Fair-use limits apply per minute and per day.

We do not use AI anywhere else to personalise twekes or to make decisions about you.

8. How we order what you see

Some lists (for example Moments, "near you" results and suggestions) are ordered by simple rules:

We do not build advertising profiles. We make no decisions based solely on automated processing that have legal or similarly significant effects on you. The automated word filter (section 3.10) only stops a post from being published, and you can contact us if you think it was wrong.

9. What other people can see

WhoWhat they can see
Everyone, including people without an account
  • Your name, handle, photo, city and bio, and your follower counts.
  • Shouts and replies (the app shows them without the author's name to people without an account).
  • Listings (clubs, places, races, experts).
  • The exact meeting point of club sessions.
  • An approximate area for community runs, without the host.
  • How many people are going to a run, but not who.
  • No Moments.
Signed-in runners

All of the above, plus:

  • Moments shared with Everyone;
  • Moments shared with your followers or your club, if they are in that audience;
  • Shouts and replies with your name, and comments;
  • community runs you post, with your name and the exact meeting point;
  • the runs and sessions you joined, with your name, handle and photo among the people going, until two days after the run starts (after that, only the organiser and the other participants);
  • clubs you are in;
  • your leaderboard and runner-page totals, only if you switched that on;
  • runs you made public (section 3.4);
  • if they are connected with you: your area, run types, interests and preferred run areas.
OrganisersThat you joined their run or session (we notify them with your name)
People in a conversationThe messages in that conversation
Runners you blockedYour profile card and listings, and your leaderboard totals if you share them. While signed in, they do not see your Moments, Shouts, replies, comments or chat messages, and they cannot send you direct messages.
PartnersYour display name, handle and stamp history at their venue (never your position); your messages if you contact them
ExpertsYour display name and what you send them. We never pass them your training history.
Our moderators and adminsContent and messages reported to them, and account data when needed for support, safety or security
NobodyYour Turf, routes, exact location, home pin, date of birth, email address and health data (other than leaderboard totals and public runs you chose to share)

10. Moments on our website and in our own promotion

Today, every photo on twekes.com is chosen and uploaded by our team, and they are photos from the twekes team's own Moments.

We may also show your Moments shared with Everyone, or a still image from them:

The Terms describe this licence in full.

11. Who we share data with

We share personal data only as described in this policy. Our service providers ("processors") handle it on our instructions, to provide the Service.

RecipientRoleWhat they receive
SupabaseProcessor: database, sign-in, file storageEverything stored in your account
RenderProcessor: hosts our serversAll requests between the app and our servers; platform logs
ROOKProcessor: wearable syncYour twekes account ID and the health and fitness data from the sources you connect (section 4)
AnthropicProcessor: Ask twekesAs described in section 7
ExpoProcessor: push delivery, app updatesPush tokens and notification content; app version, install ID and IP address
ResendProcessor: service emails (sign-up confirmation, password reset, account deletion confirmation, listing decisions, moderator alerts)Email address, name and the email content
ZohoProcessor: our mailbox (info@twekes.com)Emails you send us
IONOSProcessor: hosts twekes.comWebsite server logs
AppleSign in with Apple; push notifications; place names on iPhone; Apple Health on your phoneSign-in requests and, when you delete your account or disconnect Apple, the request to withdraw twekes's access; push tokens and notification content; coordinates you look up
GoogleAndroid push (Firebase Cloud Messaging); Health Connect on your phone; place names on Android; QR-code scanning on Android (ML Kit, on the phone); Google Maps on some screens; Google Fonts on the websitePush tokens, Firebase installation ID and notification content; the map area viewed and IP address; ML Kit may send usage and diagnostic information to Google
OpenFreeMap; OpenStreetMap and unpkg.com (maps)Map tiles and map softwareIP address and the map area you view
ipapi.co, ipwho.isCountry detection when your phone's location is not availableIP address
Meta (Instagram)Club Instagram posts shown in twekes load from InstagramIP address and Instagram's own cookies when you view such a post; the club's access token
StravaIndependent company, only if you connect itStrava receives Usage Data about our use of its API (section 5); Strava's own policy applies
Apple App Store, Google PlayIndependent companiesTheir own policies apply to downloads
Other runners, partners, expertsOther usersAs described in section 9

We may also disclose data:

We do not sell personal data, and we do not share it for cross-context behavioural advertising.

12. Where your data is processed

We run twekes from the address in section 1. Our providers process data in the European Union (for example, our servers run at Render in Frankfurt, Germany), in the United States and in other countries. So your data may be processed outside the country where you live.

Where the law of your country requires safeguards for sending your data abroad, we rely on the safeguards our providers offer under their own terms, such as standard contractual clauses. You can ask us about them at info@twekes.com.

If the data protection law of your country requires a legal basis for each use of your personal data, these are ours.

PurposeLegal basis
Creating and running your account, signing you in (including Sign in with Apple), and the features you use: profile, runs you log, Moments, clubs, messages, Shouts, notifications, TurfContract: it is necessary to provide the Service under the Terms
Keeping the Apple token and using it to withdraw twekes's access when you delete your account or disconnect AppleContract (carrying out your deletion request) and our legitimate interest in meeting Apple's rules for Sign in with Apple
Health and fitness data from Apple Health, Health Connect, Garmin and the other sources you connect, including the transfer to ROOKYour explicit consent, given when you connect a source and grant its permissions. You withdraw it by disconnecting the source or changing the permissions.
Appearing on leaderboards and showing totals on your runner pageYour explicit consent: the switch in Privacy & settings
Ask twekes, including the summary of your recent trainingYour explicit consent: the Ask twekes agreement
Location, camera, microphone, photos and notificationsYour consent, through your phone's permissions, for the features you use
Showing Moments on twekes.com and our own channels (section 10)Our legitimate interests in presenting twekes, with an easy opt-out
The athletes directoryOur legitimate interest in helping runners find each other. You can object (section 16).
Security, preventing abuse and fraud, moderation, blocking, the word filter, crash reports and diagnostics, ordering content, improving the ServiceOur legitimate interests in a safe, working service. You can object (section 16).
Service emails (sign-up confirmation, password reset, deletion confirmation)Contract
Keeping records the law requires; answering lawful requestsLegal obligation

You can withdraw consent at any time. This does not affect what we did before you withdrew it. Where we rely on legitimate interests, you can ask us how we balanced them against your rights.

14. How long we keep data

DataHow long
Account, profile, sign-in methods, Terms acceptanceUntil you delete your account
The Apple token used to withdraw accessUntil you disconnect Apple or delete your account; we then withdraw it at Apple and delete it
Runs, activities, routes and TurfUntil you delete your account. You can delete runs you logged by hand at any time (section 3.4).
Runs imported from StravaUntil you delete your account, including after you disconnect Strava
Raw data received from ROOK (including daily summaries and heart-rate readings)30 days after we receive it. Your workouts taken from it stay with your runs and activities. Deleted with your account.
Strava and ROOK connections and tokensUntil you disconnect the source or delete your account
Moments: view once and 24 hoursNo longer visible 24 hours after posting (view-once Moments can be opened once by each person). Their files are deleted by an automatic sweep that runs every 15 minutes. A Moment with an open report is kept for moderators until the report is closed.
Moments: Post and Event album, and who viewed themUntil you delete them or your account
Messages, Shouts, replies and commentsUntil you delete them or your account
Notifications in your inbox90 days after they are sent. Deleted with your account.
Push tokensWhile you are signed in on that phone. Deleted with your account. When you sign out, the token is unlinked from your account and kept as a device token for general announcements: deleted after 90 days without use.
Ask twekes conversationsOn your phone only; removed when you sign out or delete your account. Anthropic: see section 7.
Ask twekes "Report answer" reports6 months. Reports made while signed in are also deleted with your account.
Feedback, expert requests and claimsUntil you delete your account
Reports you makeUntil you delete your account
Reports about you or your content, with the excerpt of the reported contentWhile your account exists. After you delete your account, they are kept without your identity: 12 months after the report is closed.
Blocks and suspension recordsUntil you delete your account
Perk stampsUntil you delete your account. We never keep your position, only your distance from the venue.
Crash reports90 days. When you delete your account, your account ID is removed from them.
Performance diagnostics90 days. Deleted with your account.
Search terms saved by older versions of the appDeleted in October 2026. They are no longer collected.
Emails we receive at info@twekes.comKept in our mailbox (Zoho), with no automatic expiry. You can ask us to delete your emails, unless we need them for a legal claim.
Server logs (Render, IONOS)Kept by Render and IONOS for the period their own terms set, then deleted by them
Database backupsKept by Supabase for the period its terms and our plan set, then replaced. Deleted data drops out as backups are replaced.
Partner, expert and club listingsUntil removed. When you delete your account, your expert profile is deleted. Clubs and places you created stay listed and are no longer linked to your account; they keep the details shown on the listing, including any contact details entered for it, until the listing is changed or removed. Ask us to remove contact details that are yours.
Website waitlistDeleted 30 days after the public launch of the app.
Records the law requires us to keepAs long as the law requires

15. Deleting your account

How to delete it:

If you use Sign in with Apple: when we hold the Apple token from your sign-in, you need to do nothing more. Otherwise the app asks you to confirm with Apple once. If you skip that, we still delete your account, and the app tells you how to remove twekes from "Sign in with Apple" in your Apple Account settings.

What happens:

What we keep afterwards, and for how long, is in section 14 and on the deletion page. Three points to know:

16. Your rights

Wherever you live, you can ask us about your data. Depending on the law of your country, you have the right to:

How to use your rights.

17. Children

twekes is for people aged 16 and over. You confirm your age when you create an account, whichever way you sign up. We do not knowingly collect personal data from anyone under 16. If we learn that an account belongs to someone under 16, we delete it. If you think a child is using twekes, tell us at info@twekes.com.

18. Security

We protect your data with:

No system is completely secure, and we cannot guarantee that your data will never be accessed without permission. If a breach affects your personal data, we will tell you and the authorities when the law requires it.

19. Changes to this policy

We update this policy when the Service or the law changes. If we make a material change, we will tell you in the app or by email at least 14 days before it takes effect, and where the change needs it, we will ask for your agreement again. A change needed for legal or safety reasons, or one that only concerns a new feature, can take effect sooner. The version and date at the top show which version applies.

20. Contact

Marc Tanas (twekes), Bitar Street, Msaytbeh, Beirut, Lebanon. Email: info@twekes.com.