RestCall

Privacy Policy

Last Updated: November 14, 2026

RestCall (the “App”) is an Android and iOS app provided by Pehebase (ぺへベース) (“we”, “us”). This Privacy Policy explains what information the App handles, where it is sent, and how it is used.

1. At a Glance

  • There is no account. We never ask for your name, email address, or phone number
  • Your workout records are never sent to us. The only thing that reaches our server (Cloudflare) is a question or request you choose to send (Section 3.4)
  • The only information sent outside your device is usage data and crash reports for improving the App and fixing bugs (Google Firebase), the information needed to check for app updates, the information needed to confirm Pro purchases (RevenueCat), and questions or requests you send (Sections 3, 5 and 6). This is the same for the Android and iOS versions

2. Information Kept Only on Your Device

2.1 Workout Records and Settings

The App stores the following information only on your device:

  • Workout records (start and end times, set marks, exercise names, memos)
  • Settings (announcement interval, speech rate, language, theme, etc.)

This information is not transmitted anywhere. It is deleted when you uninstall the App.

2.2 Export and Import

Export writes your records to a file in a location you choose. Import reads records from a file you choose. Neither goes through any server of ours. You are responsible for storing and sharing exported files.

2.3 Reading Elapsed Time Aloud (Speech Synthesis)

The App reads the elapsed rest time and similar information aloud using the text-to-speech feature installed on your device. Speech is generated on your device, and the App does not send what is read aloud to anyone.

2.4 Device Features Used by the iOS Version

The iOS version uses the following features on your device only. None of them send information outside your device.

  • Detecting an ongoing call: To stay silent during phone calls, the App uses iOS CallKit only to check whether a call is in progress. It does not access the other party, phone numbers, or call content
  • Notifications: The App schedules local notifications on your device to let you know when announcements were stopped, for example by a phone call
  • Lock Screen and Control Center: The App uses a Live Activity and a Control Center control to show the elapsed time and let you control the timer

3. Information Sent Outside Your Device

This section and Sections 5 and 6 apply to both the Android and iOS versions.

3.1 Usage Data (Firebase Analytics)

To improve the App, we send the following usage data through Firebase Analytics, provided by Google LLC:

  • App opens and screen views
  • Workout start, set done, and workout end, with their numbers (announcement interval, number of sets, duration, and whether an exercise name was set)
  • Onboarding progress (which step was viewed, whether it was completed or skipped)
  • Views of the Pro screen
  • Settings changes (which setting and its new value)
  • Sending a question or request (and whether it was the first one) and deleting a conversation. The message itself is not sent
  • Information Firebase adds automatically (app instance ID, device model, OS and app version, language, country/region, approximate time of use, etc.)

We do not send exercise names, memos, or any other text you enter.

We do not collect the advertising ID (Android advertising identifier or iOS IDFA). The App disables advertising ID collection in Firebase Analytics and does not use the permissions needed to read the advertising ID (the iOS version never asks for tracking permission). Usage data is not used for advertising or for tracking you across other apps or websites.

Turning it off: You can stop sending data to Firebase Analytics and Firebase Crashlytics (Section 3.2) by turning off “Send analytics data” in Settings. If you use the App in the EU, EEA, UK, or Switzerland, this setting starts off, and nothing is sent until you turn it on yourself.

3.2 Crash Reports (Firebase Crashlytics)

To fix bugs, when the App crashes we send the following information through Firebase Crashlytics, provided by Google LLC:

  • Crash details (error and where in the code it occurred)
  • Device model, OS and app version, and device state at the time (memory, free storage, etc.)
  • An ID that Crashlytics assigns to each installation

Crash reports do not include your workout records or any text you enter.

3.3 Checking for App Updates (Revopush)

To deliver small fixes without going through the store, the App uses Revopush’s service to check for and download updates. When it does, the app version, a deployment key, information about the currently installed update, a per-device identifier (Android ID on Android, identifier for vendor on iOS), and the result of applying an update are sent to Revopush’s servers. Your workout records and any text you enter are not sent.

3.4 Questions and Requests (In-App Support)

Only when you send a message from “Send a question or request” in Settings, the following is sent to our support service (servers of Cloudflare, Inc.):

  • The message you typed
  • An anonymous key the App generates for each device (used only to know where to deliver replies; it is not linked to your name or email address)
  • The app version, OS and OS version, language, and device model (Android only)

Your workout records are not sent. Replies appear on the same screen. No sign-up or email address is needed. If you have never sent a message, the App does not contact the service. If you delete the App, the key is deleted too and you can no longer see past messages.

4. How We Use Information

  • Information on your device: To provide the App’s features, such as announcements, records, and settings
  • Usage data: To understand how features are used and improve the App
  • Crash reports: To identify and fix bugs
  • Update checks: To deliver fixes
  • Questions and requests: Replying to you, investigating bugs, and improving the App

We do not sell this information, and we do not use it for advertising.

5. External Transmissions (Disclosure under Japan’s Telecommunications Business Act)

In accordance with the external transmission rules of Japan’s Telecommunications Business Act, we disclose the information sent from your device to external parties as follows.

RecipientServiceInformation sentPurposeRecipient’s privacy policy
Google LLCFirebase AnalyticsUsage events and numbers (Section 3.1), app instance ID, device model, OS and app version, language, country/regionUsage analysis and app improvementhttps://policies.google.com/privacy
Google LLCFirebase CrashlyticsCrash details, device model, OS and app version, device state, per-installation IDIdentifying and fixing bugshttps://firebase.google.com/support/privacy
RevenueCat, Inc.RevenueCat (Pro purchase confirmation)Anonymous user ID generated by the app, purchase history (product, price, currency, purchase date) and store transaction information, OS and app version, country/regionConfirming Pro access and processing purchaseshttps://www.revenuecat.com/privacy
RevopushRevopush (app update delivery)App version, deployment key, current update information, per-device identifier (Android ID on Android, identifier for vendor on iOS), update resultsDelivering fixeshttps://revopush.org/privacy
Cloudflare, Inc.Support service (Cloudflare Workers)Messages you send, anonymous key, app version, OS and OS version, language, device model (Android only). Only when you send a messageReplying to questions, investigating bugshttps://www.cloudflare.com/privacypolicy/

You can stop transmission to Firebase Analytics and Firebase Crashlytics by turning off “Send analytics data” in Settings. In the EU, EEA, UK, and Switzerland, it starts off.

6. Pro Purchase

The App offers an optional one-time “Pro” purchase. Payment is processed by Google Play in the Android version and by the App Store in the iOS version, and your credit card and other payment details are handled by Google or Apple. Neither the App nor we receive your payment details.

To confirm whether Pro is available to you, we use RevenueCat, provided by RevenueCat, Inc. When you open the App, and when you purchase or restore Pro, the following information is sent to RevenueCat:

  • An anonymous user ID generated by the App
  • Purchase history (product, price, currency, purchase date) and store transaction information
  • OS and app version, country/region

No personal information such as your name or email address, and no workout history, is sent. Purchase information is handled in accordance with RevenueCat’s Privacy Policy (https://www.revenuecat.com/privacy) and the privacy policy of Google (https://policies.google.com/privacy) or Apple (https://www.apple.com/legal/privacy/).

7. Retention and Security

  • Information on your device remains there until you delete it or uninstall the App. Its security also depends on your device’s settings, such as the screen lock
  • Usage data and crash reports are stored on Google’s servers in accordance with Firebase’s terms. Usage data is retained for up to 14 months, and crash reports for up to 90 days
  • Questions and requests are stored on Cloudflare’s servers. Conversations are deleted automatically one year after the last message

8. Your Choices and Rights

  • You can delete records within the App. Uninstalling the App deletes all records
  • You can stop sending usage data and crash reports by turning off “Send analytics data” in Settings
  • You can delete a conversation you sent, including from our support service, with “Delete this conversation” in the ”…” menu at the top right of that screen
  • To request deletion of usage data already sent, contact us using the details in Section 12. We may not be able to identify your data without your app instance ID

9. Children’s Privacy

The App does not knowingly collect personal information from children under 13. If you are a parent and believe your child’s information has been sent, please contact us.

10. International Transfers

Firebase, Revopush, RevenueCat and Cloudflare may process information on servers outside Japan, including in the United States. Each company handles information in accordance with its own privacy policy and applicable laws.

11. Additional Information for Specific Regions

11.1 Users in the EU, EEA, UK, and Switzerland (GDPR and similar laws)

  • Controller: Pehebase (ぺへベース)
  • Legal basis: Usage analytics and crash reporting are based on your consent. In these regions, “Send analytics data” starts off, and data is sent only after you turn it on. You can withdraw your consent at any time by turning it off in Settings. Update checks are based on our legitimate interest in delivering fixes. Questions and requests are handled to respond to your request
  • Processors: Google LLC (Firebase Analytics and Firebase Crashlytics), Revopush (app update delivery), RevenueCat, Inc. (Pro purchase confirmation), Cloudflare, Inc. (receiving questions and requests)
  • Your rights: Access, rectification, erasure, restriction of processing, data portability, and objection. You may also lodge a complaint with the supervisory authority in your country

11.2 California Residents (CCPA)

  • Categories of information: Identifiers (app instance ID, per-installation ID, per-device ID, anonymous support key), in-app usage activity, device information, and questions or requests you send
  • Sale and sharing: We do not sell personal information, and we do not share it for cross-context behavioral advertising
  • Your rights: The right to know, the right to delete, the right to correct, and the right not to be discriminated against for exercising these rights

You can exercise any of these rights using the contact details in Section 12.

12. Contact

For privacy-related questions or requests, please contact:

  • Trade name: Pehebase (ぺへベース)
  • Address: RMBld. 701, 5-31-1 Minami 2-jo Nishi, Chuo-ku, Sapporo, Hokkaido 060-0062, Japan
  • Contact: “Send a question or request” in the App’s Settings, or the contact form (also linked from our Contact page)

13. Changes to This Policy

We may update this Policy as needed. When we do, we will update the “Last Updated” date on this page. Significant changes will also be announced in the App.


Effective Date: October 27, 2026