Contents
1Introduction
"タープの張り方3D" (Tarp Setup 3D, the "App") is a mobile app that shows how to pitch a tarp in 3D, one step at a time. The App is provided by an individual developer.
This Privacy Policy explains which information stays on your device when you use the App, which information leaves the device, what it is used for, and how you can stop it. By using the App, you are deemed to have agreed to this Policy.
The App has no account registration, no sign-in and no text fields, so there is no way to enter your name, email address or phone number. The developer operates no server, and the App itself never communicates with the developer. The only information that leaves your device is sent by the Google services embedded in the App for advertising and measurement.
2What stays on your device
The following information is stored only on your device and is never sent anywhere by the App.
- The pitches you added to your favorites
- Display settings (language, see-through tarp, angle guides) and whether "Send usage data" is on or off
- The number of poles, pegs and lines and the tarp size you entered in "Only what my gear can pitch"
- Which pitches you have already opened (to clear the "new" mark)
- Counters used to decide when to show the "Rate this app" prompt: launches, pitches opened, how many times and when the prompt was shown
- Your answers to the consent form in the European Economic Area (EEA), the UK and Switzerland (stored by Google's consent management tool; the App only reads them)
Deleting the App erases all of this. If your OS backup (iCloud Backup, or backup to your Google Account) is on, this data may be copied to your own account like the data of any other app. The developer never receives it.
3Usage measurement (Google Analytics for Firebase)
To learn which pitches and articles are viewed and at which step people leave, and to improve the App, we use Google Analytics for Firebase ("Firebase Analytics"), provided by Google LLC. Measurement is on by default. You can turn it off at any time under Settings → "Privacy" → "Send usage data" in the App (see section 6).
Actions the App records
When one of the following happens, the App sends it to Firebase Analytics. Pitches, knots and articles are sent as IDs (short codes that correspond to their names).
- Opening a pitch: which pitch, and from where (the list, the Shade tab or an article)
- Viewing a step of a pitch: which pitch and which step number
- Turning on "Only what my gear can pitch": the number of poles, pegs and lines you entered and how many pitches matched. The tarp size is not sent
- Changing the tarp size (the value itself is not sent)
- Opening a knot: which knot, and from where (Basics or a pitch)
- Tapping the link to the store page of the sister app "Tie Knots 3D": from which knot, or from Settings
- Opening the shade simulation: from where (a pitch screen, the Shade tab or an article) and, from a pitch screen, which pitch
- Opening a Basics article: which article
- Turning the angle guides on or off
- A screen failing to render: the type of error and which screen it happened on. The error message text, file names and URLs are not sent
What Firebase Analytics collects automatically
- Lifecycle records such as app launches, time in the app and screens shown
- Device model, OS version, language, screen size, App version and first-open date
- Country and region, estimated from your IP address (the IP address is used for the estimate and is not stored)
- An app instance ID (an identifier Firebase assigns to each installation; it changes when you reinstall) and a Firebase installation ID
- On Android, the advertising ID. You can reset or delete it in your device settings (see section 6)
- On iOS, the IDFV (an identifier shared by apps from the same developer). Measurement on iOS does not use the advertising identifier (IDFA)
- On Android, Firebase Analytics may receive the install source from Google Play (which ad or link the install came from) and use it to measure installs
None of these records is linked to your name or email address. They are, however, sent together with per-installation identifiers (the app instance ID, the advertising ID or the IDFV), so actions from the same device are grouped together. The data is processed on Google Analytics servers and may be combined with other Google services (see section 5).
4Advertising (Google AdMob)
To keep the App free, it shows one banner ad at the bottom of the screen. Ads are served by Google AdMob, a service of Google LLC. The App does not use interstitial (full-screen) or video ads.
To serve ads, the AdMob SDK collects the following and sends it to Google.
- Advertising identifiers: on Android the advertising ID and the App Set ID; on iOS the IDFA, only if you allowed it in the App Tracking Transparency (ATT) prompt
- Your IP address (used to estimate your approximate region)
- Device model, OS version, language, screen size and network type
- Interaction records such as app launches and ad impressions and taps
- Diagnostics such as ad load time, crashes and hangs
This information is used to show ads, to count impressions and detect invalid clicks, and, where you have consented, to select ads based on your interests (personalized ads). On Android, the ads SDK may use the Android Privacy Sandbox APIs (Topics and Attribution).
The data sent to serve ads is not stopped by turning off "Send usage data". See section 6 for how to stop ad personalization and how to change your consent in the EEA, the UK and Switzerland.
5Sharing with third parties
The information in sections 3 and 4 is sent directly to Google's servers by the Google LLC SDKs embedded in the App. The developer does not receive it and does not pass it on to anyone. Google processes it under its own privacy policy and data processing terms. The developer relies on those terms to confirm that Google provides protection equivalent to this Policy.
| Service | Purpose | Google's documentation |
|---|---|---|
| Google AdMob (Google LLC) |
Serving and measuring banner ads, detecting invalid traffic | Google Privacy Policy / How Google uses information from sites or apps that use our services |
| Google Analytics for Firebase (Google LLC) |
Usage measurement (receiving and aggregating the records in section 3) | Privacy and Security in Firebase / Google Privacy Policy |
| Google User Messaging Platform (Google LLC) |
Showing the consent form in the EEA, the UK and Switzerland (uses your IP address to decide which form to show) | Google Privacy Policy |
The App's Firebase project is linked to AdMob. The measurement data in section 3 is therefore shared with AdMob (Google) to measure ad performance and improve ad delivery.
Except where disclosure is required by law, no information is provided to any third party other than those listed above.
6Consent and how to withdraw it
Stopping usage measurement (all regions)
Turn off Settings → "Privacy" → "Send usage data" in the App. From then on, none of the records in section 3 is sent and the automatic collection by Firebase Analytics stops as well. The setting is stored on your device and can be turned back on at any time. It does not stop the data sent to serve ads (section 4).
Consent in the European Economic Area (EEA), the UK and Switzerland
In these regions, Google's consent management tool (a Google-certified CMP) appears on first launch and asks whether information on your device may be used for advertising and measurement. Your choices are applied to ad serving and to the consent settings of Firebase Analytics (storage of measurement data, storage and use of data for ads, and ad personalization). You can change or withdraw your consent at any time from Settings → "Privacy" → "Ad privacy settings" in the App (this row appears only in regions where consent management is required).
Launch records created in the short time before the consent form appears on first launch may be sent before you have answered. To stop measurement altogether, turn off "Send usage data" as described above.
App Tracking Transparency (ATT) on iOS
On iOS, after the consent form, the App shows Apple's ATT prompt asking for permission to track. If you allow it, AdMob uses the advertising identifier (IDFA) to personalize ads and measure their performance. If you do not allow it, ads are still shown but are not personalized. The App's measurement (Firebase Analytics) does not use the IDFA either way. You can change your ATT choice at any time under iPhone Settings → Privacy & Security → Tracking.
Resetting the advertising ID and turning off personalized ads
- Android: Settings → Google → All services → Ads lets you reset or delete the advertising ID. After deletion, a string of zeros is sent instead of the ID
- iOS: Settings → Privacy & Security → Tracking → turn off "Allow Apps to Request to Track"
- If you are signed in to a Google Account, you can also manage personalization in Google's ad settings
7External links and contacting us
The App's Settings screen has links to this Privacy Policy, to contact us, to "Rate this app" and to the "Sister app: Tie Knots 3D". Each opens your device's browser, mail app or store app only when you tap it, and the site or app that opens then communicates in the usual way under its own policy.
"Contact us" only opens your mail app, with the App version in the subject line. Your email address, the subject and the message reach the developer only when you send the email. They are used solely to reply to you and to investigate the problem you report.
8Retention and deletion
The information in section 2 exists only on your device and is erased when you delete the App.
The measurement data in section 3 is kept on Google Analytics servers. User-level data retention is set to 2 months, after which it is deleted automatically (aggregated reports that contain no individual data are not subject to this limit). The advertising data in section 4 is retained by Google under Google's policies.
The developer has no means of identifying which measurement data came from your device. Requests to access or delete individual data can therefore be honored only within technical limits. Send any request to the contact address in section 11; we will do what we can and explain anything we cannot do. On your side, deleting the App, resetting the advertising ID (Android) and turning off "Send usage data" stop further records and break the link to the identifiers.
9Children's privacy
The App is not directed at children under 13, and we do not knowingly collect personal information from children under 13. If you are a parent or guardian and believe your child has provided personal information through the App, please contact us at the address in section 11.
10Changes to this policy
When we change the embedded services or what the App records, we update this Policy and publish the latest version on this page. Changes that increase the information sent are published here before the App version that sends it is distributed. The date of the last update is at the end of this page.
11Contact
For questions about this Privacy Policy, or to request access to or deletion of data, please email us at the address below.
For help with the App or to report a problem, see the support page.
Last updated: