Mashu privacy policy

The short version

• Mashu is a stretching app for iPhone made by 140G Labs LLC. Mashu is the new name of Mochi from version 2.0. This policy covers both.
• We collect what the app needs to build your stretching plan, run the game and keep your account: your email, the answers you give when you set up the app, your stretches and your progress.
• In Mashu 2.0 and later, the answers about your body (the areas you want to loosen up, how stiff you feel, and a goal of easing aches) stay in our database and don't go to our analytics provider. Mochi, the app before 2.0, does send them to it (section 3.10). We don't use these answers for ads, prices or offers.
• If you add friends in the stretch club, they see your first name and your Mashu, and the friend who invited you sees your progress in your first weeks.
• Purchases go through Apple. We don't receive your card details. Our purchase provider knows you by random ids, not by your email or name.
• We don't sell your data, show ads or track you across other companies' apps.
• You can delete your account in the app. Analytics data may stay after you delete your account, until you ask us to delete it. Our purchase provider keeps a record of your purchases under a random id, for accounting, refunds and fraud prevention (section 8).

1. Who we are

Mashu is operated by 140G Labs LLC, a limited liability company registered in the State of Wyoming, United States.

• Address: 30 N Gould St Ste R, Sheridan, WY 82801, United States
• Contact: help@stretchwithmochi.com

"We", "us" and "our" mean 140G Labs LLC. Under the EU and UK General Data Protection Regulation ("GDPR"), 140G Labs LLC is the controller of your personal data.

Mochi is being renamed Mashu, starting with version 2.0. Your account and your history carry over. Where this policy says "Mashu" or "the app", it also means the versions called Mochi.

2. What this policy covers

This policy covers:

• the app for iPhone, including its widgets;
• our websites at getmashu.com and stretchwithmochi.com, including invite pages;
• our emails and push notifications, and the support we give you.

Together we call these the "Service".

3. What we collect

What we collect depends on the version of the app you use and the features you use. Some features described here are only in Mashu 2.0 and later.

3.1 Your account

You sign in with a one-time code we email you, or with Sign in with Apple.

• Email address. It is your login, and we use it for service emails (section 3.11).
• One-time sign-in codes. We store them in a scrambled form (a hash), and they stop working after a short time.
• Apple ID identifier. Only if you use Sign in with Apple. Apple gives us an identifier and, if you allow it, your name and an email address, which may be Apple's private relay address.
• Sessions. A session token keeps you signed in. It is stored on your phone in the iOS Keychain. Our servers keep a record of each session, with the IP address and the app and iOS version it signed in from.

3.2 The answers you give when you set up the app

When you set up the app, it may ask questions like the ones below to build your stretching plan and your reminder. Some are optional, and you can skip those. You need an email address or Sign in with Apple to have an account. If you skip an optional question, the app builds your plan without that answer.

"Prefer not to say" stores nothing. To change or remove an answer, use its setting in the app where there is one, or write to us from your account's email address.

The app builds your plan from these answers automatically. The plan has no legal or similarly significant effect on you.

3.3 Answers about your body

The areas you want to loosen up, your stiffness, and a goal of easing aches can say something about how your body feels. We treat them with extra care:

• We use them to build your plan and, in aggregate, to improve our stretch library.
• We don't use them for advertising, marketing, prices or offers, and we don't sell them.
• Mashu 2.0 and later don't send them to our analytics provider. Mochi, the app before 2.0, does (section 3.10).
• Mashu doesn't diagnose anything (see the Terms, section 16).

We use these answers to provide the plan you ask the app for, which is our contract with you (GDPR Article 6(1)(b)).

3.4 Your stretching and your game

• Your stretches. Which routines and stretches you did, when, for how long, and which you skipped.
• Your progress. For example your streak, paws, items and other progress in the game.
• A record of your game. The actions that change your game, such as a stretch, a purchase with paws or a reward.
• What you create. Your own stretches and routines, suggestions and feedback you send us from the app (with the app version, platform and language).
• Your time zone. The app dates each stretch in your phone's time zone, so your reminders and your day line up.

3.5 Friends and the stretch club

If you use the stretch club, you can invite friends with a link or a code. When someone accepts, you become friends in Mashu. We store:

• your invite code, and who invited whom;
• your friendships, and anyone you blocked;
• for a new player who joined with an invite, the dates of their first stretches, so we can tell whether their invite counts for the club;
• reports you file about a friend (a reason you pick from a list);
• the rewards the club gave you.

What other people see:

Friends don't see your email, your stretch history, your streak or your location. We may show your name as "A friend" instead, for example after a report.

The app doesn't read your phone's address book. You share your link with iOS's share sheet, and the app doesn't see who you send it to. If you tap Paste to enter an invite code, the app reads your clipboard to find the code.

3.6 Purchases

If you buy something in the app, Apple processes the payment. We don't receive your card number, billing address or other payment details.

Your account gets a random billing id. Apple receives it with each purchase, and RevenueCat (section 5) knows your account by it and by a second random id that links its purchase events to your analytics profile (section 3.10). RevenueCat doesn't receive your email or your name. RevenueCat may also send purchase events to our analytics provider under your billing id, on a separate record with no email or name.

When you buy Mashu Plus or a one-time purchase, or start a free trial:

• RevenueCat keeps what you bought, when, the price and currency, whether it's a trial, when it renews or ends, and any refund;
• we keep whether you have Plus, until when, whether it renews and which product it is, including Plus we give for free.

If you restore purchases on a second account that uses the same Apple ID, your purchases move to the account that restored.

3.7 Notifications

If you turn notifications on, we store for each phone a device id, the push token Apple and Expo give us, and details such as the phone's language, the app version, your notification settings and when we last sent one. Your reminder time is stored with your account.

With notifications on, we may send reminders to stretch, news from your stretch club, and reminders before a free trial ends or a subscription renews. During a routine, the app can also show its own cues on a locked phone. Those are scheduled on your phone and don't reach us.

Turn notifications off in the app (Settings in Mashu, the Profile tab in Mochi) or in your iPhone's Settings.

3.8 Settings kept on your phone

Your appearance, sounds and haptics settings are stored on your phone. The app sends your language to our servers so notifications come in your language, and may send your appearance and language to our analytics provider (section 3.10). Widgets show your stretch, streak or progress on your Home Screen and Lock Screen, where anyone holding your phone can see them.

3.9 Device and technical data

• Device model, iOS version, app version, language, region and time zone.
• An install id the app creates. It is not Apple's advertising identifier (IDFA).
• Your IP address when your phone or browser talks to our servers, our content network or our website. We use it for security, abuse prevention and to infer your country.
• Crash reports and errors, with the app's state at that moment, linked to your account (section 3.10).

3.10 Product analytics

We use PostHog to learn how people use the app, to fix bugs and to improve the Service. PostHog may receive:

• events about what you do in the app, such as screens you open, taps, setup steps, stretches, purchases and friends added, with the app version, device type, iOS version and language;
• your IP address, from which PostHog works out your approximate location;
• a profile for your account, identified by your email address once you sign in, which also holds your account id;
• some of your setup answers and settings as properties of that profile, such as your goal (in Mashu 2.0, never a goal of easing aches), how often and where you stretch, your reminder time, your age range (including "under 18"), your gender, your usual day and how you heard about Mashu;
• which version of a screen, offer or feature you saw when we test more than one;
• purchase events from RevenueCat (section 3.6);
• crash reports and errors.

Mashu 2.0 doesn't send PostHog your name, words you type in the app (such as a search or a stretch's name), or the body areas, stiffness or goal of easing aches you give when you set up the app. Mashu doesn't record sessions.

If you use Mochi (before 2.0). Mochi sends PostHog similar events, and also the answers from its setup: your sex, your goal (which can be pain relief), the hours you sit each day, how stiff you feel and the areas where you feel tension, along with your streak and points, and the names you give your own routines. Mochi versions up to 1.2.0 also record sessions: a replay of the app's screens and taps, with what you type hidden. Mochi 1.2.1 and later don't record sessions, and updating to Mashu 2.0 stops the rest. Recordings and other data already sent are kept like other analytics data (section 7), and you can ask us to delete them (section 8).

Opting out. You can object to analytics. Email us from your account's address with "Analytics opt-out" in the subject, and we will turn analytics off for your account. After that, phones signed in to your account with Mashu 2.0 or later stop sending analytics for it, apart from a small amount a phone may record right after the app opens, before it learns of the opt-out. A phone still on Mochi keeps sending until you update it. RevenueCat may still send purchase events under your billing id, on the separate record in section 3.6. Opting out doesn't delete data already collected. Ask us in the same email if you want it deleted.

3.11 Emails we send

• Sign-in codes.
• If you subscribe, reminders before a free trial ends or a yearly plan renews.
• Notices about important changes to the Service, the Terms or this policy.
• Replies when you write to us.
• If you join the Google Play waitlist, one email when Mashu arrives on Google Play (section 3.14).

3.12 What we don't collect

The app doesn't collect:

• your precise location;
• your phone's address book, calendar or photos;
• Apple Health data;
• audio or video from your camera or microphone;
• Apple's advertising identifier.

3.13 If you used Mochi

Your account, stretch history, streak, paws, items and routines carry over to Mashu. Mochi's setup asked your sex, goal, hours sitting each day, stiffness and the areas where you felt tension, and recorded when you accepted its pledge. We keep those answers and use them for your plan. Mashu shows your sex and goal in its own words, and sends them to our analytics provider as your gender and goal (section 3.10), except a goal of easing aches. To change or remove any of these answers, write to us.

If you ever had a Mochi Access trial or subscription, we keep its record (account id, product, Apple transaction id, status and dates) while your account exists, and delete it with your account.

3.14 The Google Play waitlist

Mashu isn't on Android yet. If you leave your email on our website to hear when it arrives on Google Play, we store:

• your email address, so we can send you that one email;
• the language of the page you used, so the email is in that language;
• the date you signed up and which version of the form's text you saw.

We use the address only to send one email when Mashu arrives on Google Play, and we don't add it to an account or to our analytics. To limit abuse, the form also counts sign-ups per network for a short time, using a code made from your IP address with a secret key, rather than the address itself.

We keep your address until we send that email, then delete it from the waitlist. If you change your mind before then, write to help@stretchwithmochi.com from that address and we will delete it. The email has an unsubscribe link, and we send no other email from the waitlist.

4. Why we use your data, and our legal bases

We don't show ads in the app, we don't use your data for advertising in other companies' apps or websites, and we don't sell it. We don't make decisions about you by automated means that have legal or similarly significant effects.

5. Who we share it with

We use service providers that process data for us, on our instructions. They include:

We may add or replace providers over time, and we update this list when we do.

Other users. Friends you add see what section 3.5 lists.

Legal reasons. We may disclose data when the law requires it, or to protect the rights, safety or property of our users, the public or 140G Labs LLC.

Business transfers. If 140G Labs LLC is merged or acquired, or sells the app, your data may move to the new owner as part of that transaction.

We don't sell or rent your personal data, and we don't share it for cross-context behavioral advertising.

6. International transfers

Our servers and most of our providers are in the United States. If you live in the European Economic Area, the United Kingdom or Switzerland, your data is transferred to and processed in the United States. For these transfers we rely on the EU-US Data Privacy Framework (and its UK and Swiss extensions) where a provider is certified under it, and on the European Commission's Standard Contractual Clauses or another safeguard the law allows otherwise. You can ask us for a copy of these safeguards.

7. How long we keep it

• Your account, answers, stretches, game record, friendships and purchases: while your account exists.
• Sessions: a session stops working when you sign out or after a long period without use. We keep its record no longer than your account exists.
• After you delete your account: we delete your data as section 8 describes. Copies may remain in backups for a limited time, until they are overwritten.
• Analytics data (section 3.10), including crash reports and errors: for as long as it helps us understand and improve the Service, including after you delete your account. You can ask us to delete it at any time (section 8).
• Purchase records with RevenueCat (section 3.6), after you delete your account: under your random billing id, for as long as we need them for accounting, tax, refunds, restoring purchases, preventing fraud and legal claims.
• Your email address, account id and billing id after you delete your account: we keep them only to have RevenueCat remove the analytics id, and to find and delete your analytics data and your purchase records if you ask, and remove them once we have.
• Reports about a friend: while the reported account exists. Reports you filed stay without your account id after you delete your account.
• Messages you send us: for as long as we need them to help you, keep a record of our answers and meet legal obligations.
• Security records, such as counts of sign-in codes sent and of waitlist sign-ups: for a short time.
• The Google Play waitlist (section 3.14): until we send the email that tells you Mashu is on Google Play, then we delete your address from the waitlist, or sooner if you ask us.

8. Deleting your account

You can delete your account in the app: in Mashu, in Settings; in Mochi, on the Profile tab. This permanently deletes:

• your account, profile and answers;
• your stretches, game record, progress and items;
• your own stretches, routines, suggestions and feedback;
• your friendships, blocks and club data;
• your notification devices;
• your purchase records with us.

Purchase records stay with RevenueCat. RevenueCat keeps the record of your purchases (section 3.6) under your random billing id. We need that record for accounting, tax, refunds, restoring purchases and preventing fraud. When you delete your account, we ask RevenueCat to remove the random analytics id and the other details we or the app stored with that record. RevenueCat may keep your IP address and basic device data it received, such as your country and app version. We also remove our link between your account and the billing id, apart from the record in section 7 that lets us answer a later request. To ask us to delete your purchase records too, email us from your account's address with "Delete purchases" in the subject, ideally after any subscription has ended. We may keep what we need for accounting, tax or legal claims.

Analytics data stays. Deleting your account doesn't delete your analytics data in PostHog, or the separate record under your billing id (section 3.6). To have it deleted, email us from your account's address with "Delete analytics" in the subject, before or after you delete your account. If your account still exists, we also turn analytics off for it (section 3.10). If you have a subscription, RevenueCat may send new purchase events after that, for example when it renews, ends or is refunded, and start a new separate record under your billing id. If your account still exists, ask us again if you want it deleted. If you deleted your account, ask us once any subscription has ended, or ask us in the same email to delete your purchase records too.

What stays, with your account id removed:

• If you joined with an invite, the invite record may stay, so your friend's club keeps what it earned, with your account and your stretch dates removed from it.
• If you invited friends, they keep their rewards and their own history.
• Reports you filed stay, without your account id.

Deleting your account does not cancel a subscription. Apple bills you until you cancel in your iPhone's Settings, under your name, then Subscriptions. Cancel there before you delete your account. Apple keeps its own records of your purchases under Apple's privacy policy.

9. Your rights

9.1 In the EEA, the UK and Switzerland

You have the right to:

• access your data and get a copy;
• correct it;
• delete it;
• restrict how we use it;
• receive it in a structured, machine-readable format, and have it sent to someone else;
• object to uses based on our legitimate interest, including analytics;
• withdraw consent where we rely on it, without affecting what we did before;
• complain to your data protection authority. In Italy that is the Garante per la protezione dei dati personali.

9.2 In California and other US states

Depending on where you live, you may have the right to know what we collect and why, to get a copy, to correct it, to delete it, and not to be treated differently for using these rights. We don't sell your personal information or share it for cross-context behavioral advertising, as California law defines those terms. We use sensitive personal information only for purposes California law allows without a right to limit, such as providing and improving the Service.

9.3 How to use them

• Delete your account in the app (section 8).
• Change your answers in the app where there is a setting for them, or by writing to us.
• Get a copy of your data: email us from your account's address with "Data export" in the subject.
• Opt out of analytics: see section 3.10.
• Delete your analytics data, with or without your account: see section 8.
• Delete your purchase records: see section 8.
• Anything else: email us.

Any clear request works; a subject line just helps us find it. We answer within the time the law gives us. We may need to confirm your identity first, for example by asking you to write from your account's email address.

10. Security

We use reasonable technical and organizational measures to protect your data, such as encryption in transit, keeping session tokens in the iOS Keychain, storing sign-in codes only as hashes, and limiting who can reach our systems. No system is completely secure, and we can't guarantee the security of your data. If a breach affects your data, we will notify you and the authorities where the law requires.

11. Children and teens

The Service is not for children under 13, or under 16 in the EEA, the UK and Switzerland. We don't knowingly collect data from them. If you are a parent or guardian and think your child gave us data, write to us and we will delete it.

If you tell us you are under 18, the app may hide some paid offers, such as offers that are only available for a limited time. Your age range reaches our analytics provider like the other answers in section 3.10.

12. Storage on your phone and cookies

The app doesn't use cookies for analytics or advertising. It stores your session in the iOS Keychain, and your settings, a copy of your recent data (so the app opens fast and works offline) and the analytics install id in storage only the app can read.

Our websites don't use analytics, advertising cookies or tracking pixels. If that changes, we will update this policy.

13. Tracking

Apple's App Tracking Transparency asks apps to get permission before they track you across other companies' apps and websites. We don't track you as Apple defines it, so the app doesn't show that prompt.

When you open the App Store from an invite page or one of our campaign links, the link tells Apple where it came from. Apple shows us totals of such visits and downloads, not who you are.

14. Links to other services

The Service links to services we don't run, such as the App Store and Apple's subscription settings. Their own privacy policies apply there.

15. Changes to this policy

We may update this policy. We will change the date at the top when we do. If a change is material, we will tell you in advance where the law requires, for example in the app or by email. You can always read this policy at getmashu.com/privacy.

16. Contact us

• Email: help@stretchwithmochi.com
• Mail: 140G Labs LLC, 30 N Gould St Ste R, Sheridan, WY 82801, United States

In the EEA, the UK and Switzerland you can also contact your data protection authority at any time.