Make Me
What About Everyone
← Back

Privacy Policy

Effective November 19, 2026

Make Me ("Make Me," "we," "us") is an iPhone app published by Make Me ("the company"). This Privacy Policy describes what data the app handles, where it goes, and what choices you have. It applies to the Make Me iOS app and the pages at trymakeme.app.

Most of what the app knows about you stays on your phone and in your own iCloud. Some things leave it: what you share with other players, an account if you choose to sign in, usage analytics that help us fix and improve the app, and the services that run subscriptions, payments and ads. Each is described below. We do not sell your data, and we do not ask to track you across other companies' apps and websites.

Contents
  1. Quick summary
  2. On your device and in your iCloud
  3. What other players see
  4. Your account (optional)
  5. Analytics and diagnostics
  6. Subscriptions and payments
  7. Advertising
  8. Service providers
  9. Permissions the app requests
  10. HealthKit data
  11. Screen Time data
  12. Camera and photos
  13. Location data
  14. Contacts
  15. Retention & deletion
  16. Children's privacy
  17. California (CCPA / CPRA)
  18. EEA / UK (GDPR)
  19. Security
  20. Changes
  21. Contact

1. Quick summary

  • Your goals, history, blocked-app selection and settings live on your phone and in your own private iCloud.
  • When you play with others (contests, shared goals, Wordhole, the Lobby, chat, the feedback wall), what you share there — your nickname, picture, progress and posts — is visible to those players.
  • Signing in is optional. If you sign in with Apple, Google or an emailed code, we keep your email address and, if Apple or Google gives it to us, your name. Your name is never shown in the app; other players see only your nickname. You can delete your account in the app at any time.
  • We use PostHog for usage analytics and crash and performance diagnostics, and Meta's SDK to measure our own ads. We do not ask for App Tracking Transparency, so the app never reads your advertising identifier.
  • Subscriptions run through Apple and RevenueCat. Funding a challenge with money runs through Stripe.
  • Camera frames used to count reps are processed on your phone and never recorded or sent. HealthKit data is read only to count what you do.
  • One optional place shows a non-personalized rewarded ad from Google AdMob.

2. On your device and in your iCloud

The following is stored in the app on your phone and, when iCloud is signed in, in your private iCloud database (container iCloud.com.mudbank.chibutt). Apple holds and encrypts your private iCloud data; we cannot read it.

  • Your goals, targets, routines and settings.
  • Your activity history (reps, steps, quiz answers, reading and writing, dates) and any minutes you've earned.
  • Your selection of apps to restrict, as opaque tokens from Apple (see §11).
  • Your history backup, if you are signed in (see §4).

3. What other players see

Playing with others needs some of your data to be shared with them. It is stored in the app's public iCloud database, which other Make Me users can read:

  • Your nickname, your picture or avatar, and your friend code.
  • The contests and shared goals you make or join, and your progress in them: the counts you do (reps, steps and the like, including counts read from HealthKit when a goal uses it), the days you finished, your Wordhole guesses, and results.
  • What you post: chat and reactions in a contest's room, Lobby posts (such as a level completed), and feedback-wall notes and comments, each under your nickname.
  • A one-way hash of your email address, if you signed in or gave one, so friends who have it in their contacts can find you (see §14). Your email address itself is never shown to anyone.

Reports of abusive content are reviewed by us, and we may remove content or reset a nickname.

4. Your account (optional)

You can use Make Me without signing in. If you sign in — with Apple, with Google, or with a code we email you — our server (hosted with Netlify and Neon) keeps:

  • your email address (with Sign in with Apple this may be an Apple relay address);
  • your name, if Apple or Google gives it to us. It is kept for us only and is never shown in the app or to other players;
  • the account identifiers Apple or Google assign, a link to your app's iCloud identifier, and the sign-in tokens needed to keep you signed in and to revoke Apple's access when you delete your account;
  • the codes we email you, stored only as a keyed hash and deleted once used or expired.

While you are signed in, the app backs up your history to your own private iCloud so it can be restored on a new phone. We also attach your email address to your analytics profile (PostHog, §5) and your subscription record (RevenueCat, §6), so we can help you with your account.

Emails (sign-in codes, and invitations you ask us to send to a friend) are sent through Resend. If you invite a friend by email, we keep their address and the name you give for that invitation.

5. Analytics and diagnostics

The app sends usage events to PostHog (PostHog Inc., US cloud) so we can see what works, find what breaks, and measure features and experiments. Events describe what you do in the app — for example, that a goal was made, a screen was opened, a purchase screen was shown, or a day was finished — along with the app version, device model, OS version, language and time zone. PostHog derives an approximate location (country or city) from your IP address. Events are tied to an identifier the app makes for this install, not to your name; if you sign in, your email is attached as described in §4. The app also sends crash reports and performance and memory diagnostics (from Apple's MetricKit) to PostHog. We do not record your screen.

The app includes Meta's SDK (Meta Platforms, Inc.) to measure our own ads on Facebook and Instagram: it reports that the app was installed and opened and a few steps such as making a first goal, with the goal's type. Trial and purchase events reach Meta from RevenueCat. Advertising identifier collection is turned off, and we never show the App Tracking Transparency prompt, so Meta does not receive your IDFA from us. Attribution uses Apple's privacy-preserving SKAdNetwork.

If you opted in to share analytics with developers in iOS Settings, Apple may also send us anonymous crash logs.

6. Subscriptions and payments

Subscriptions. Purchases go through Apple. We use RevenueCat, Inc. to manage subscriptions: it receives an identifier for your app account (your app's iCloud user identifier), the analytics identifier from §5, your purchases, entitlements and renewal status, and your email if you are signed in. We never see your payment card. See revenuecat.com/privacy.

Funding a challenge. If you put money into a challenge, payment is processed by Stripe; we never see your full card number. Our server keeps a record of the challenge, the amounts, and the resulting rewards and donations, which we keep as long as the law requires for financial records. We make the donations to the charities named.

7. Advertising

One optional place in the app offers a rewarded ad you can choose to watch for a small in-app benefit. Ads are served by Google AdMob and are non-personalized: we don't request App Tracking Transparency, so your advertising identifier stays all zeros, and we pass AdMob no user identifier, email or activity. AdMob may process limited information to serve the ad and prevent fraud, such as your IP address and device type, under Google's policies: support.google.com/admob/answer/7676680.

8. Service providers

  • Apple — App Store, iCloud / CloudKit, Sign in with Apple, StoreKit, Screen Time, HealthKit, push notifications.
  • PostHog — usage analytics, crash and performance diagnostics (§5).
  • Meta Platforms — measuring our ads (§5).
  • RevenueCat — subscriptions (§6).
  • Stripe — payments when you fund a challenge (§6).
  • Google — AdMob rewarded ads (§7), and Sign in with Google if you choose it (§4).
  • Netlify and Neon — hosting our server and its database (§4, §6).
  • Resend — sending sign-in codes and invitation emails (§4).
  • OpenAI — scoring a bed photo, only when you submit one (§12).

Each receives only what it needs for its job and processes it under its own privacy policy and our agreements with it.

9. Permissions the app requests

Each permission is asked for only when you use the feature that needs it, and you can change it any time in iOS Settings:

  • Screen Time — so the app can lock the apps you choose (§11).
  • Camera — to count push-ups and squats on your phone, or to take a bed photo (§12).
  • Health — to read steps, workouts and similar counts for goals that use them (§10).
  • Location — for routines tied to a place (§13).
  • Microphone and speech recognition — for voice features, when you use them.
  • Contacts — to find friends who use Make Me (§14).
  • Notifications — for reminders, contest news and messages.
  • Alarms — for wake-up goals.

App Tracking Transparency is not requested.

10. HealthKit data

If you allow it, Make Me reads health data such as steps and workouts, only to count what a goal asks for. We do not write to HealthKit. Raw HealthKit data is not sent to us or to any analytics or advertising service. When a goal you play with others uses it, the resulting count (for example, today's steps) is shared with those players, as described in §3, because that is how the contest is played.

11. Screen Time data

When you choose apps to restrict, Apple's Family Controls framework gives the app opaque tokens. The app can hand them back to iOS but cannot see which apps they are; we never see app names, icons or your usage history. The tokens are kept on your phone and in your private iCloud.

12. Camera and photos

Push-up and squat counting uses the camera with Apple's on-device Vision framework. Only body-pose points are worked out from each frame, on your phone. No frames are recorded, stored or sent.

If you choose the bed goal and submit a photo of your bed, the photo is sent through our server to OpenAI to be scored and is not kept by us. OpenAI's API terms apply: openai.com/policies/api-data-usage-policies.

13. Location data

Routines tied to a place (for example, "leave the office by 5") use iOS geofences. The place you choose is stored on your phone and in your private iCloud; the log of arrivals and departures stays on your phone. Your live location is read only to show it on screen and is not stored or sent. Location is optional, and the rest of the app works without it.

14. Contacts

If you let Make Me look at your contacts to find friends, the email addresses in your address book are turned into one-way hashes on your phone, and only those hashes are compared with other players' hashes in iCloud. Names, phone numbers and the addresses themselves never leave your phone. A hash keeps addresses out of view but is not a secret: someone who already knows an address can compute its hash.

15. Retention & deletion

Delete your account in the app: Profile › Account › Delete account. This deletes your account on our server — your email address, your name and your sign-in tokens — revokes Apple's sign-in for the app, signs you out on your devices, and deletes your history backup from your iCloud. We keep only a record that the account was deleted, holding no email or name, and any payment and donation records the law requires us to keep.

Shared content (§3) stays with the contests and posts it belongs to under your nickname. To have it removed, or to have your data removed from PostHog or RevenueCat, email privacy@trymakeme.app.

Without an account, deleting the app removes its data from your phone; to remove the iCloud copy, go to Settings › your name › iCloud › Manage Storage.

Emails you send us are kept only as long as needed to answer, generally no more than 24 months.

16. Children's privacy

Make Me is not directed at children under 13, and we do not knowingly collect personal information from children under 13 (or under 16 where that age applies). Ads in the app are non-personalized. If you believe a child has given us personal information, contact privacy@trymakeme.app and we will delete it.

17. California residents (CCPA / CPRA)

California residents have the right to know what personal information we hold, to delete it, to correct it, to opt out of its sale or sharing, and not to be discriminated against for using these rights. The categories we collect are described above: identifiers (email, account and install identifiers), name (if Apple or Google provides it), commercial information (subscriptions and payments), internet and device activity (§5), approximate location from IP, and the content you share (§3). We do not sell personal information. We use Meta's SDK to measure our own advertising (§5); to opt out of that, email us. To use any of these rights, email privacy@trymakeme.app; we may ask you to confirm details only the account holder would know.

18. EEA, UK, and Switzerland (GDPR)

You have rights of access, rectification, erasure, restriction, portability and objection. Contact privacy@trymakeme.app.

Legal basis. (a) Contract, to provide the app, your account, your subscription and the contests you join; (b) legitimate interest, for analytics and diagnostics, security, measuring our ads, and non-personalized ads; (c) consent, for optional permissions (Health, camera, location, contacts, notifications).

International transfers. Our service providers (§8) are based in or process data in the United States. Where data leaves the EEA, UK or Switzerland, we rely on appropriate safeguards such as Standard Contractual Clauses.

Complaints. You may complain to your local data protection authority.

19. Security

Data on your phone is protected by iOS file protection, iCloud data is encrypted by Apple, and every connection the app makes uses TLS. Sign-in codes are stored only as keyed hashes. No system is perfectly secure; if you find a vulnerability, email security@trymakeme.app.

20. Changes to this policy

If we make material changes, we will update the date above and tell you in the app.

21. Contact

  • General: support@trymakeme.app
  • Privacy requests: privacy@trymakeme.app
  • Security: security@trymakeme.app
© 2026 Make Me · v1.0
What About Everyone FAQ Support