StopBy Privacy Policy
StopBy (ここメモ in Japanese) is a to-do app for iPhone and Android that reminds you of things to do when you arrive at or leave a place, and lets a household share those lists. This policy explains what information the apps handle, what stays on your device, what is sent to our servers, and what is shared with other companies. It covers both the iOS app and the Android app; where they differ, it says so.
Your current location
StopBy uses your location to show how far away your places are and to notice when you arrive at or leave one. This detection runs on your device: iOS uses Apple's geofencing, and Android uses the geofencing in Google Play services. To work while the app is closed, it asks for the "Always" location permission on iOS, or "Allow all the time" on Android.
Your current location is never sent to our servers, and it is not stored as a history. When you search for a place or create one from your current location, the app sends your current location to the provider of the map and place search (Apple on iOS, Google on Android) so it can suggest nearby places first and look up the address, as described under "Maps and place search". The only location data that reaches our servers is the map point of a place you chose to save, as described under "Accounts and sync". You can change or revoke the location permission at any time in Settings > Privacy & Security > Location Services on iOS, or in Settings > Apps > StopBy > Permissions on Android.
Data on your device
Everything you create in StopBy is stored on your device:
- The places you save: their names, map coordinates, notification radius, and category.
- Your to-dos: their titles, which place they belong to, whether they remind you on arriving or on leaving, how often they repeat, who they are assigned to, and when they were completed.
- Your settings, such as the default notification radius.
- While you are at one of your places, when you got there, so that a reminder for leaving is not sent when you only pass by.
- If you use the Apple Watch app, a copy of your places and to-dos on your watch.
Until you sign in, this data exists only on your device, and deleting the app deletes it.
Accounts and sync
You can use StopBy without an account. If you sign in with Apple or Google, we create an account for you and your places, to-dos, and categories are uploaded to and kept in sync with servers operated by us. These servers run on Amazon Web Services in the United States (Oregon), so if you live outside the United States, your data is transferred there.
| What we store on our servers | Why |
|---|---|
| The identifier Apple or Google assigns to your account for StopBy, and your name, if you chose to share it at sign-in or set one in the app. We do not store your email address, including Apple's relay address. | To recognize you when you sign in again |
| A token from Apple, stored encrypted (Sign in with Apple only) | To revoke your Sign in with Apple session when you delete your account |
| Your places, to-dos, categories, and the household they belong to, including who added and who checked off each to-do, whether each to-do reminds on arriving or on leaving, how often it repeats, and, when you complete a repeating to-do, your device's time zone, so that it comes back on the right day | To sync them across your devices and with your household |
| Session tokens for your devices | To keep you signed in without asking again |
| A push notification token (iOS) or a Firebase installation identifier (Android) for each of your devices | To tell your other devices that something changed (see "Notifications") |
Family sharing
If you create or join a household, the other members of that household can see all places, to-dos, and categories in it, including who checked off each to-do and the display names of the members. Invitations are single-use links that expire after 72 hours. The owner of a household can remove members, and any member can leave. When you leave or are removed, the shared data stays with the household and is removed from your device.
Notifications
Reminders when you arrive or leave are local notifications created on your device. If you are signed in, our servers may send silent push notifications to your devices, through Apple on iOS and through Google's Firebase Cloud Messaging on Android; these carry no content and only tell the app to sync.
When someone in your household checks off a to-do you added, our servers send you a notification with their display name and the to-do's title, through Apple or Google in the same way. You can turn this off in the app under Settings > Notifications.
If you opt in, we may send push notifications about new features, updates, and offers. You can withdraw consent at any time in the app's settings, or turn notifications off in your device settings. Reminders and the notifications that keep your devices in sync work separately and are not affected by this choice.
To send these, we keep your device's push notification token (iOS) or Firebase installation identifier (Android), the app's language, and whether you opted in, even if you are not signed in. If you withdraw consent while signed out, we delete that device record; a signed-out device that has not opened the app for 180 days is deleted as well. We also keep a record of when consent was given or withdrawn, to show that we only send these notifications with your agreement; it holds an internal device identifier and the time, and is no longer linked to your account once the account is deleted.
Maps and place search
On iOS, the map, the place search, and address lookup come from Apple Maps, which is part of iOS: to suggest places and show addresses, the app sends Apple the text you type when searching for a place, your current location or the point you picked so nearby places come first, and the coordinates of a point whose address it looks up, including your current location when you create a place from it. Apple processes this under the Apple Privacy Policy. On Android, they come from Google Maps Platform: to draw the map, suggest places, and show addresses, the app sends Google the area of the map you are looking at, the text you type when searching for a place, your current location so nearby places come first, the place you pick, and the coordinates of your current location when you create a place from it. Google processes this under the Google Privacy Policy. We do not receive the searches themselves; only the place you save reaches our servers, and only if you are signed in.
Subscriptions
StopBy Pro is an optional subscription sold through the App Store or Google Play. Apple or Google handles the payment; we never see your payment details. We use RevenueCat, Inc. to verify purchases and track subscription status. RevenueCat receives your App Store receipt or Google Play purchase token, your account identifier, device information, and, if usage analytics is on (see "Usage analytics"), the app's Firebase app-instance identifier, and processes them under the RevenueCat Privacy Policy. On our behalf, RevenueCat also sends subscription events (a trial starting, a trial converting, a renewal, a cancellation, an expiration, or a billing problem, with the price and currency) to Google Firebase Analytics, tied to that app-instance identifier.
Usage analytics
To understand whether StopBy is useful, the app sends a small amount of usage data to Google Firebase Analytics.
In the European Economic Area (EEA) and the United Kingdom, the app sends this data, and the crash reports described below, only if you agree. It asks at the end of the first-time setup, and you can change your answer at any time in the app under Settings > Privacy. Until you answer, what the app would send is held only in the app's memory on your device; if you agree, it is sent then, and if you decline, it is discarded. Whether you are in the EEA or the UK is decided from the country of your App Store or Google Play account, or, if that is not available, from your device's region setting. Elsewhere, the app sends this data by default.
| What is sent | Why |
|---|---|
| That a reminder was shown or opened when you arrived at or left a place, or that an arrival or departure was noticed without a reminder and why (nothing left to do, assigned to someone else, reminded recently, notifications off, or you left too soon after arriving), how long it took to open, how many open to-dos it listed, and the place's category and reminder radius | To measure whether reminders fire and help |
| Which screens you open and from where; when you add, delete, or complete a place or to-do, with how many you have, how long the item existed, the place's category and radius, how it was picked on the map, which screen you added it from, whether a to-do reminds on arriving or on leaving, how often it repeats, and whether it was completed shortly after its reminder, from the notification, in the app, or on an Apple Watch | To understand how StopBy is used and what to improve |
| Once a day: how many places, open to-dos (and how many of them remind you when leaving), repeating to-dos, and custom categories you have, how many to-dos you completed in the past week, how many people share your household, your plan, whether you are signed in, whether location (and precise location) and notifications are allowed, how many days ago you installed the app, and, on iOS, whether the Apple Watch app is installed | To see which patterns of use keep StopBy useful |
| Onboarding results and changes to the location and notification permissions | To see where reminders stop working |
| For the first place added during onboarding: how many to-dos it got, and which of the suggested to-dos were among them (only that a suggestion was used, never what you typed) | To improve the suggestions |
| That you agreed to share usage data, and whether during the first-time setup or in Settings (EEA and UK only; a refusal is never sent) | To know how many people the numbers come from |
| Whether you receive news and offers, whether you were asked and how you answered, which of these notifications you opened and how long it took to open them | To check that these notifications are welcome and to send fewer if they are not |
| That a paywall was shown or closed, that a purchase was started, canceled, failed, or completed, that purchases were restored, and whether the plan was yearly or monthly | To understand which plans people choose |
| Subscription events sent by RevenueCat, as described under Subscriptions | To understand whether subscriptions work for people |
| An app-instance identifier (Apple's identifier for vendor on iOS, a Firebase installation identifier on Android), device model, operating system version, app version, language, and an approximate country derived by Google from your network address | Standard Firebase Analytics data used to count users and sessions |
The names of your places, their coordinates, your to-do titles, your display name, and your precise location are not included in any analytics event. StopBy does not use the advertising identifier (IDFA on iOS, the advertising ID on Android) and does not track you across other apps or websites.
Google processes this data on our behalf under the Google Privacy Policy and retains event-level data for 14 months. We also export the same event data to Google BigQuery for our own analysis and keep it there no longer than 14 months. Aggregated statistics may be kept longer.
Crash reports
If the app crashes, or runs into an error that would silently lose data or a reminder, a report is sent (in the EEA and the UK, only if you agreed, as described under "Usage analytics"; until you answer, reports stay on your device, and they are deleted if you decline) to Google Firebase Crashlytics: where in the app it happened, the app version, the operating system version, the device model, free memory and storage, and the time. To show what led up to it, a report also carries the usage data described under "Usage analytics" that the app sent shortly before, how many places were being watched, and how many changes were last synced. Reports carry the app-instance identifier described under "Usage analytics", so that we can find them when you contact us; they contain no account identifier, no location, and none of your places or to-dos. Google processes them under the Google Privacy Policy and retains them for 90 days.
Support emails
When you contact us, we receive your email address, what you write, any attachments, and the details the app fills in when you use Settings > About > Contact Support: the app and operating system versions, the device model, the app's language and your time zone, your plan, the app's location and notification permissions and related battery settings, the app-instance identifier if usage analytics is on (otherwise a note that it is off), and your account identifier if you are signed in. You can see and edit these details before sending. We use them only to answer you and to look into the problem, and delete the conversation within one year of its last message. We never delete or change your account, or disclose its data, only because of an email; we first ask you to confirm that the account is yours.
Who else receives data
- Apple: Sign in with Apple, App Store purchases, push notification delivery, and maps, place search, and address lookup on iOS.
- Google: Sign in with Google, Google Play purchases, push notification delivery, maps, place search, and address lookup on Android, Firebase Analytics and Crashlytics on both platforms, as described above, and Google Workspace (Gmail), where we receive and keep support emails.
- RevenueCat: subscription verification as described above.
- Amazon Web Services: hosts our servers, our database backups (encrypted at rest), and our server logs in the United States.
- Cloudflare: routes traffic to our servers and serves this website. Cloudflare Web Analytics counts page views on this website without cookies or personal identifiers.
We do not sell your data, we do not show ads, and we do not share data with anyone else except when required by law.
Retention and deletion
- Data on your device is deleted when you delete the app.
- Data on our servers is kept while your account exists. You can delete your account from Settings in the app, or on the web at Delete your StopBy account by signing in the same way; this removes your account, your devices, and, if you are the household owner, the household and everything in it. Database backups are taken daily and removed within 70 days.
- Server logs, which include account and household identifiers and details of each request, are kept for 30 days to operate the service and keep it secure.
- If we end the service, accounts and data on our servers are deleted after it ends.
- Analytics data is retained by Google as described above, and crash reports for 90 days. To ask us to delete analytics data associated with your app instance, contact us at the address below.
- Support emails are deleted within one year of the last message in the conversation.
Your choices
- Location: change the permission at any time in iOS or Android Settings. Without "Always" (iOS) or "Allow all the time" (Android), reminders only work while the app is open.
- Notifications: turn them off in iOS or Android Settings.
- News and offers: off unless you turn them on; turn them off at any time in the app under Settings > Notifications.
- Sync and sharing: use the app without signing in, or delete your account to stop syncing.
- Subscriptions: manage or cancel in your Apple ID settings or in Google Play.
- Usage analytics and crash reports (EEA and UK): sent only if you agree; change your answer at any time in the app under Settings > Privacy.
If you are in the EEA or the UK
The controller of your personal data under the EU General Data Protection Regulation (GDPR) and the UK GDPR is Tetsuro Mikami, the individual who develops and operates StopBy. You can reach him at [email protected].
| What we do | Legal basis |
|---|---|
| Accounts, sync, family sharing, the notifications that keep your devices in sync and tell you when family checks something off, and subscriptions | Performance of our contract with you (the terms of use) |
| Usage analytics and crash reports | Your consent |
| News and offers by push notification | Your consent |
| The record of when you agreed to or withdrew from news and offers | Our legal obligation to be able to show consent |
| Server logs and database backups | Our legitimate interest in running StopBy reliably and securely |
| Answering support emails | Our legitimate interest in answering you and fixing problems you report |
You have the right to access your personal data, to have it corrected or erased, to restrict or object to its processing, and to receive the data you gave us in a portable format. Where we rely on your consent, you can withdraw it at any time; this does not affect what was done before. You can delete your account and its data yourself as described under "Retention and deletion". For anything else, email [email protected]; we will ask you to confirm that the account or app instance is yours, and answer within one month.
Our servers and the companies listed under "Who else receives data" process data in the United States. Transfers there rely on the EU-U.S. Data Privacy Framework and its UK Extension where the recipient is certified, and otherwise on the European Commission's Standard Contractual Clauses and the UK Addendum to them.
You can also complain to the data protection authority of the EEA country where you live or work, or, in the UK, to the Information Commissioner's Office (ICO).
Children
StopBy is not directed to children under 13, and we do not knowingly collect information from them. In the EEA and the UK, if you are under 16 (or the lower age set by your country), please ask a parent or guardian before agreeing to share usage data.
Changes
We may change this policy. The changed policy is posted here with its effective date, and we may not announce changes in the app or individually.
Contact
Questions about this policy: [email protected]