Privacy Policy

Effective date: 2026-09-24
Last updated: 2026-09-26 (version 1.1.0)

This Privacy Policy describes how Istvan Szoke, an individual developer based in Austria ("we," "us," "our"), processes personal information when you use the TipShark mobile application for iOS (the "App") and related services (together, the "Services").

Authoritative language. The original and legally binding version of this Privacy Policy is written in English. Any translation (whether provided by us, by your browser, by your device, by an automated translator, or by a third party) is offered solely for your convenience. In case of any discrepancy, ambiguity, or conflict between the English version and any translated version, the English version prevails.

1. Who we are

Controller: Istvan Szoke
Postal address: c/o RA Matutis, Fürstenstraße 5, 5400 Hallein, Austria
Contact (all privacy matters): support@tipshark.app

If you have questions about this Policy or how we handle your information, email us at the address above.

You also have the right to lodge a complaint with the Austrian data protection authority:
Österreichische Datenschutzbehörde (DSB)
Barichgasse 40–42, 1030 Wien, Austria
www.dsb.gv.at

2. Scope and age

The Services are intended for users at least 16 years old who use the App to record shifts, tips, and related notes for their personal work tracking. The App is not directed at children under 16. We do not knowingly collect personal information from children under 16.

TipShark is intended for personal record-keeping. It is not designed for use while driving, or at any time when using your phone is unsafe or not allowed, including at work.

Territorial availability. The App is currently offered in the European Union, Iceland, Norway, Switzerland, the United Kingdom, the United States, Canada, Australia and New Zealand. The App is not currently offered in, among other territories not listed above, mainland China or Turkey. If you access the App from another country, your local laws may not be addressed in this Policy. In that case, contact us at support@tipshark.app and we will respond to reasonable requests to the extent feasible.

Languages. The App is offered in English, German, Hungarian, Spanish, and French.

Legal version check. When it starts, the App fetches a small file from our website (tipshark.app/legal.json) to see whether these terms have changed. The request carries no personal data or identifiers; like any web request, our hosting provider (Cloudflare) processes the IP address to deliver it.

3. What information we process

TipShark is designed to keep your data on your device. However, some limited information is processed automatically through the App Store, subscription, and diagnostics providers described below.

3.1 Information you enter in the App

• Tip amounts, shift times, dates, categories, notes, and labels you create.
• This content is stored locally on your device in the App's sandboxed storage. We do not run our own servers for it, and we do not have accounts or logins.
• If iCloud is turned on for TipShark on your device, the App automatically and silently syncs this content to your own private iCloud database (Apple CloudKit, container iCloud.com.ist1code.app.tipshark), so it appears on your other devices signed into the same Apple Account. This private database belongs to your Apple Account — we cannot read, access, search, or export it; we do not have a copy. If iCloud is off, the App works fully offline and keeps your content only on the device.
• Deleting an entry, or deleting the App, removes it from the device (and, once sync catches up, from your other synced devices), but a copy can remain in your private iCloud account for a period even after that. Deleting the App does not, by itself, delete the iCloud copy. See Section 10 for how to remove it.
• Independently of iCloud sync, if Apple's whole-device backup (iCloud Backup) is enabled on your device, a snapshot of the App's local storage may also be captured in that backup. That backup is controlled by Apple and your iCloud settings, not by us.

3.2 Information collected automatically (analytics, configuration, and attribution)

We use the following providers to understand how the App is used and to attribute subscriptions to marketing sources:

• TelemetryDeck receives usage signals (for example which screens are opened, whether a paywall is shown, whether a purchase succeeds) with technical parameters: device model, OS and app version, language, region, time zone, screen size, accessibility settings and session counts. Each signal carries a random identifier created once per installation of the App, which TelemetryDeck hashes again on receipt; it is not derived from any device or advertising identifier. TelemetryDeck never receives tip amounts, shift notes, earnings, or job names. If you give a name to the "Other income" field, that name is sent with the usage signals so we can learn which kinds of income people track.
• Firebase Core and Firebase Remote Config (Google) deliver server-side configuration values to the App (for example, feature flags and the current monetization policy). To do so, the App sends a pseudonymous request to Google that includes a Firebase Installation ID and standard device/app metadata. We do not use Firebase Analytics to log events — that code path exists in our source but is disabled and does not run.
• Superwall receives the pseudonymous identifier described in Section 3.3, Apple's identifier for vendor (IDFV), device and app metadata (model, OS, language, region, time zone, screen size, app version, install date), your IP address, and paywall/placement events with a few non-monetary setup answers (job category, number of jobs, which extras you track, monetization policy id). On the first launch after installation the Superwall software sends this device information once so Superwall can attribute the install to a marketing campaign; we do not currently run such campaigns. Superwall never receives tip amounts, shift notes, earnings, or job names.
• Apple Ads (AdServices framework; renamed from Apple Search Ads in 2025): when you install the App from an Apple Ads campaign, iOS provides us with an attribution token. We pass this token to RevenueCat (our subscription provider) and, if enabled, to Superwall so we can attribute the subscription to the campaign. The token does not include your name, Apple Account, or contact details.

We do not use Apple's App Tracking Transparency framework (ATT), we do not collect the device advertising identifier (IDFA), and we do not use crash-reporting services such as Firebase Crashlytics.

Trial reminder. If you start a free trial, the Superwall software inside the App schedules a local reminder notification on your device shortly before the trial ends, provided you allow notifications. The reminder is created and delivered on your device; its content is set in advance and contains no personal data.

3.3 Purchases and subscription data

TipShark Pro is offered as a monthly or yearly auto-renewable subscription; where offered, the yearly plan may include a free introductory trial. Exact prices, trial length, and currency are shown in the App before you subscribe.

If you subscribe to a paid feature:

• Payments are processed by Apple through In-App Purchase. We never see your payment card details.
• RevenueCat receives a pseudonymous, anonymous app user identifier (not your Apple Account or name), your transaction receipt, Apple's identifier for vendor (IDFV), device model, OS version and App Store country so we can verify your subscription status and restore purchases.
• Superwall receives the same pseudonymous identifier and paywall interaction events (for example which paywall was shown and whether you tapped subscribe) so we can display and configure the paywall.

When you install the App from the App Store, your license to the App as distributed there is also covered by Apple's Standard EULA. How Apple processes personal data in its role as App Store operator, Apple Account provider, and payment processor is described in Apple's Privacy Policy; that processing is not described in this Policy, which only covers our processing as the app developer.

3.4 Support communications

If you email us at support@tipshark.app, we process the email address and the content of your message in order to respond. We keep these emails only as long as needed to answer you and a reasonable period afterward.

3.5 Location

TipShark does not collect precise or background location (no GPS, and we do not request Location Services). TelemetryDeck (and, for configuration requests, Firebase Remote Config) may infer an approximate geographic area (such as country or region) from technical data—primarily the IP address visible when a signal or a configuration request is transmitted—for aggregated purposes only. That inference is not combined with your tip or shift content inside TipShark, and we do not use it to identify your street address or track where you go.

4. Why we process information (purposes)

• Provide and maintain the App (Section 3.1).
• Understand aggregated usage so we can improve features (Section 3.2).
• Deliver runtime configuration such as feature flags and the current monetization policy (Section 3.2).
• Attribute App Store installs and subscriptions to marketing campaigns (Section 3.2).
• Operate subscriptions, paywalls, restore purchases, and prevent fraud (Section 3.3).
• Respond to your support messages (Section 3.4).
• Comply with legal obligations and defend legal rights.

5. Legal bases (GDPR)

We rely on the following legal bases under Art. 6(1) GDPR:

• Contract (Art. 6(1)(b)): to provide the Services you request, including processing your subscription.
• Legitimate interests (Art. 6(1)(f)): to keep the App secure and understand aggregated, anonymous usage so we can improve it. You can object at any time by emailing support@tipshark.app.
• Consent (Art. 6(1)(a)): where we ask for your consent (for example, if we later add features that require it). You can withdraw consent at any time.
• Legal obligation (Art. 6(1)(c)): where we must comply with applicable Austrian or EU law.

6. Who we share information with

TipShark has no servers and no user accounts. The App still relies on a small set of third-party providers that receive limited information related to distribution, subscriptions, analytics, and attribution. Some of them act as our service providers, and some act as independent controllers of their own services.

To make subscription status and paywall targeting work, the same pseudonymous user ID is shared between RevenueCat and Superwall. This identifier is not linked to your name, email, or device advertising identifier, and it is reset when you reinstall the App.

Apple independently determines how it processes App Store, Apple Account, and payment information under its own privacy documentation and is not acting as our processor for that activity.

We may also disclose information if required by law, court order, or to protect rights, safety, and security.

We do not sell your personal information, we do not use it for third-party advertising, and we do not use the App Tracking Transparency framework.

7. International data transfers

Firebase (Google), RevenueCat, and Superwall are based in the United States and may process data there. TelemetryDeck is based in the EU and processes data there. Where personal data is transferred outside the EEA, we rely on:

• The European Commission's Standard Contractual Clauses (SCCs), and/or
• the EU–U.S. Data Privacy Framework where the recipient is certified.

You can request information about the safeguards in place by emailing support@tipshark.app.

8. How long we keep information

• Data you enter in the App: stays on your device — and, if iCloud is on, in your private iCloud — until you delete the entry, delete the App, or remove it from iCloud as described in Section 10. We do not have a copy and cannot delete it for you.
• Analytics events (TelemetryDeck): retained per TelemetryDeck's own retention schedule; see their privacy policy for the current period.
• Subscription records (Apple / RevenueCat): retained as long as needed to validate your subscription and meet tax and accounting obligations under Austrian law (typically 7 years).
• Support emails: typically kept up to 24 months after the conversation ends, then deleted.

9. Security

We rely on Apple's iOS sandbox and device-level encryption to protect data on your device, and on Apple's CloudKit private-database security for the copy in your private iCloud (when iCloud is on). TelemetryDeck, Firebase, RevenueCat, Superwall, and Apple each provide industry-standard security for the limited data they receive. No system is 100% secure.

10. Your rights under GDPR

You have the right to:

• access the personal data we hold about you (Art. 15),
• request correction of inaccurate data (Art. 16),
• request deletion of your data (Art. 17),
• restrict or object to processing (Art. 18, 21),
• receive your data in a portable format (Art. 20),
• withdraw any consent at any time (Art. 7(3)).

Because TipShark does not store your tip/shift content on our own servers, most requests to us only apply to the limited technical and subscription data listed in Section 6, which we handle by emailing us or by using Settings › Data & Privacy › Request Data Deletion in the App (this sends a pre-filled email asking RevenueCat and Superwall to delete your pseudonymous technical records).

Deleting your tip/shift content itself is something only you can do, because it lives on your device and, if iCloud is on, in your own private iCloud account that we cannot access:

• Delete individual entries in the App, or delete the App itself, to remove the data from your device.
• If iCloud is on: deleting the App does not delete the copy in your private iCloud. To remove that copy, go to iOS Settings › [your name] › iCloud › Manage Account Storage (or "Manage Storage") › TipShark, and delete the App's iCloud data — or turn iCloud off for TipShark in iOS Settings › [your name] › iCloud › Apps Using iCloud and then delete the local data.

To exercise rights over the technical/subscription data described in Section 6, email support@tipshark.app. We will respond within one month.

You also have the right to lodge a complaint with the Austrian Datenschutzbehörde (see Section 1).

10.1 Users in California (CCPA / CPRA)

If you are a California resident, you have the right to know what personal information we collect, to request deletion of your information, to correct inaccurate information, and to opt out of any sale or sharing of personal information. We do not sell or share personal information as those terms are defined under California law, and we do not process sensitive personal information beyond what is described in this Policy. To exercise your rights, email support@tipshark.app. We will not discriminate against you for exercising them.

10.2 Users in the United Kingdom

If you are located in the United Kingdom, you have rights equivalent to those in Section 10 under the UK GDPR and the Data Protection Act 2018. You may lodge a complaint with the Information Commissioner's Office (ICO) at ico.org.uk.

10.3 Users in Switzerland

If you are located in Switzerland, you have rights equivalent to those in Section 10 under the Swiss Federal Act on Data Protection (nFADP). You may lodge a complaint with the Federal Data Protection and Information Commissioner (FDPIC) at edoeb.admin.ch.

11. Children

The Services are not directed at children under 16 and must not be used by them. If you believe a child under 16 has provided us with personal data (for example by emailing support), contact us at support@tipshark.app and we will delete it.

12. Changes to this Policy

We may update this Privacy Policy from time to time. The current version will always be available in the App and at https://www.tipshark.app/privacy.html. When we make material changes, we will update the "Last updated" date and, where required by law, provide additional notice in the App.

13. Contact

Istvan Szoke
c/o RA Matutis, Fürstenstraße 5, 5400 Hallein, Austria
Email: support@tipshark.app