Tamor Privacy Policy
This policy explains how information is handled in “Tamor”, an iPhone and iPad app provided by Tadashi Sugie (“we”, “us”), and on these support pages. Because who processes what, and where it goes, differs by context, it is described in four parts.
- The app itself (on-device processing)
- In-app purchases (Apple / RevenueCat)
- This support site and contacting us
- The TestFlight beta (if it applies to you)
1. The app itself (on-device processing)
The app has no registration, login or social features. It never asks for your name, email address, phone number, address, date of birth, location, contacts, photos, camera, microphone or health data. It shows no advertising and contains no advertising or behavioural analytics SDK. It does not carry out “tracking” as defined by App Tracking Transparency.
The following is stored only on your device and never sent to our servers.
| Information | Where it is stored | Purpose |
|---|---|---|
| Gems you have earned, the result of each run (gem, depth, grade, elapsed time, mistakes, date), ring layout, titles and personal bests | JSON files in the app’s own container (Application Support/Tamor/save-v1.json and a backup copy) |
Keeping your progress and collection |
| An unfinished Crusher Room run | A file in the same folder (crusher-timed-checkpoint.json) |
Resuming after the app is relaunched |
| Settings such as rendering quality, and a random identifier the app generates on the device | The app’s preferences (UserDefaults) | Keeping your settings; telling which device a recorded result came from |
The random identifier is generated on your device and is not linked to your name, email address or Apple Account. Version 1.0 does not transmit it anywhere.
Motion sensor: the app uses motion sensor information on your device to adjust the jewel ring to the way you tilt your device. This information is processed only on your device and is never stored or transmitted. You can disable this effect in the app’s settings; it is also disabled automatically when iOS “Reduce Motion” is on.
Deletion: all of the above is removed from the device when you delete the app, and we hold no copy of it. Before deleting, export anything you want to keep with Settings → “Saving & Restoring Gems” → “Export Save Data”. The exported file stays under your control and is not sent to us.
2. In-app purchases (Apple / RevenueCat)
Purchases are processed through Apple’s in-app purchase system. To validate a purchase, determine your unlock status and restore purchases, we use the SDK of RevenueCat, Inc. (United States), purchases-ios 5.90.2. The following is sent to RevenueCat’s servers when you open the purchase screen, buy or restore, and when the app launches or returns to the foreground.
| Information | Details | Recipient | Purpose |
|---|---|---|---|
| Purchase and transaction data | App Store receipt, product ID, purchase and restore status, the time the app was last used | RevenueCat (payment itself is processed by Apple) | Validating purchases, determining the unlock, restoring, preventing abuse |
| Anonymous App User ID | A random ID generated by the RevenueCat SDK. We do not set an ID of our own | RevenueCat | Managing purchase state |
| Vendor identifier (IDFV) | An identifier Apple issues per device for apps from the same developer; the SDK adds it to request headers | RevenueCat | Operating the purchase infrastructure |
| Device and app technical data | Device model, OS version, app version, build number and bundle ID, preferred languages, App Store country/region, SDK version, whether the request is in the sandbox | RevenueCat | Operating the purchase infrastructure, compatibility, troubleshooting |
| IP address | Received by the server as part of ordinary internet communication | RevenueCat | Delivering the request, security |
- Payment details are handled by Apple. Neither we nor RevenueCat receive your card number or other payment credentials. Apple’s handling is governed by the Apple Privacy Policy.
- We do not collect or send the advertising identifier (IDFA), and we do not pass contact details such as your email address to RevenueCat.
- What we can see in RevenueCat’s dashboard is purchase status and aggregate figures tied to the anonymous ID. We do not connect that to an identified individual.
- Even if you only play the free range (Depths 1–3), this communication takes place so the app can check your unlock status. Offline, it does not happen and the game still works.
- RevenueCat acts as our processor. According to its own description, data is stored on Amazon Web Services in the United States, so the information above is transferred outside Japan. See the RevenueCat privacy policy.
3. This support site and contacting us
These support pages are pre-rendered static HTML files served from an Ubuntu server on Sakura Internet’s cloud. That infrastructure serves the pages; it is not where the app’s gems or play records are stored.
- Contacting us: write to tamor@sapp.sakura.ne.jp. We use the email address, the name if you give one, and the body of your message to reply and to follow up where needed. These support pages contain no input form.
- Cookies: these support pages are static HTML and set no cookies. We use no analytics tools, advertising tags, third-party advertising or external behavioural tracking.
- Server logs: the web server records access information (IP address, timestamp, request, user-agent and similar) for troubleshooting and security. The retention period follows our server configuration.
Personal information across the website as a whole is also covered by the company privacy policy, which also applies if you use the contact form on that site.
4. The TestFlight beta (if it applies to you)
TestFlight is Apple’s beta distribution service. If you take part as a tester, the following differs from the public release.
- Apple manages invitations and participation. The email address used for the invitation and your name in TestFlight are handled by Apple; we see the tester list and testing status through App Store Connect.
- Feedback you send from the TestFlight app or from inside the beta app — the text, any screenshot you choose to attach, and information such as device, OS and app version — together with crash information, is visible to us in App Store Connect. A screenshot contains whatever was on screen, so please check it before sending.
- We look at aggregate figures such as session and crash counts. We do not analyse them against names or other identifying details.
- In-app purchases in a TestFlight build run in the sandbox environment, and no real payment is taken.
- Apple’s handling of information in TestFlight follows Apple’s own terms (see TestFlight and the Apple Privacy Policy).
5. Purposes of use
We use the information above only for:
- providing in-app purchases, validating them, determining the unlock and restoring purchases;
- preventing fraudulent purchases and abusive form submissions;
- replying to inquiries and making necessary contact;
- investigating defects and improving quality, including beta feedback;
- aggregating sales figures.
We do not use it for advertising, profiling, or sale to third parties.
We do not use the information for any purpose other than those listed above. We do not repurpose it for other services or for other activities of ours. If the purposes change, we will revise this policy and publish the revision on this page beforehand.
6. Third parties, processors and processing outside Japan
Except as required by law, we do not provide the information to third parties. We engage RevenueCat, Inc. as a processor for in-app purchases and SAKURA internet Inc. for hosting this website. Because RevenueCat stores data in the United States, the information in section 2 is processed outside Japan. Payment processing and the operation of the App Store and TestFlight are carried out by Apple under its own responsibility.
7. Retention and deletion
- On-device data: kept until you delete the app, which you can do at any time.
- Purchase data: kept for as long as needed to support restores and accounting. RevenueCat states that it retains data for as long as we hold an account with it, and for six years afterwards.
- Inquiries: kept as email for as long as needed to respond and to prevent recurrence.
- Deletion requests: please email tamor@sapp.sakura.ne.jp. Note that purchase data is tied to an anonymous ID and we cannot identify you from it; we may ask for information to confirm the request comes from you, and we cannot delete purchase records held by Apple.
8. Access, correction and suspension of use
Requests for disclosure, correction, suspension of use or erasure under Japan’s Act on the Protection of Personal Information or other applicable law can be made by email to tamor@sapp.sakura.ne.jp. We do not charge a fee unless the law provides otherwise. Because the app has no account, we hold none of your on-device data; such a request can therefore only cover our record of your inquiry and the purchase data tied to the anonymous ID.
9. Children
The app is not directed specifically at children and is not offered in Apple’s Kids category. Regardless of age, it never asks for identifying information such as a name or email address. In-app purchases can be restricted by a parent or guardian using Screen Time on the device. If a child has sent us information by mistake, please contact us at the address above.
10. Changes to this policy
We may revise this policy as necessary, and revisions take effect when posted on this page. For significant changes — for example if a future version adds cloud storage — we will announce the effective date on this page in advance.
11. Contact
For questions about this policy, please email tamor@sapp.sakura.ne.jp.