Privacy Policy

Effective 16 September 2026 · Last updated 17 September 2026

1. Who we are

Shrink (“Shrink”, “the app”) is developed and published by RipeSeed (“we”, “us”, “our”), a company organised under the laws of the State of Delaware, United States. This policy covers the Shrink iPhone application and the website at shrink.ripeseed.io.

For anything in this policy, write to shrink@ripeseed.io.

2. What the app sends

Compression runs entirely on your device’s hardware video encoder and never needs a network connection. The app works fully offline and in airplane mode. Starting with version 1.0.5, it also sends the analytics and advertising measurement data described below. Events recorded while you are offline wait on the phone and are sent when there is a connection. Versions before 1.0.5 send nothing.

Analytics data, sent to Google

The app includes Google Analytics for Firebase. Google LLC runs it and processes the data for us. When the app is installed, Firebase creates a random app instance ID, and a new install gets a new one. With that ID, the app sends usage events that record:

• which screens you open;
• how far you get through the three-card walkthrough, or where you skip it;
• your answer to the photo library permission prompt: full, limited or denied;
• how many videos a finished batch compressed;
• when you have used all three free videos in a week, and a count of how many weeks that has happened;
• when you pick more videos than your free week has left;
• which plan you are on: free, One-Month Pass, Monthly or Lifetime;
• when you open the plans screen, and from where in the app;
• when a purchase starts, completes or fails, and the name of the plan;
• when the app asks iOS to show the rating prompt;
• your answer when the app asks whether it may send notifications, and when you tap the reminder about videos still waiting.

Firebase adds details of its own to those events: your device model, iOS version, app version and language, when each session starts and how long you use the app, and an approximate location (country and city) that Google works out from your IP address.

We build the app with Firebase’s FirebaseAnalyticsCore product, which contains no code for Apple’s advertising identifier (IDFA). We turn off collection of the identifier for vendor (IDFV), and we set ad storage, ad user data and ad personalisation consent to denied, so Google gets nothing for advertising use.

If your App Store account is in the EEA, the UK or Switzerland, the app sends none of this until you tap Share on the question it asks after the photo library permission, and nothing at all if you tap Don’t share. Wherever you are, Settings › Share usage data in the app turns it off and resets the app instance ID.

Push notifications, through Google

Starting with version 1.0.5, the app registers with Firebase Cloud Messaging, which Google also runs, so that we can send an occasional notification about new features. Apple gives the app a push token for this, and the app passes it to Firebase. The token lets Firebase deliver a notification to this phone and nothing more. We send these notifications to groups, for example everyone on one app version, never to a person we can identify. Whether any notification appears is your choice in iOS Settings, and “News from Shrink” in the app’s own Settings turns these off.

The reminder about videos still waiting to be compressed does not use Firebase. The app schedules it on the phone from its own count of your library, and that count is never sent.

Apple Ads attribution, sent to Apple

Once per install, the app asks Apple’s AdServices framework for an attribution token and sends the token to Apple’s attribution server. Apple answers whether the install came from an Apple Ads ad and, if it did, with the campaign, ad group and keyword IDs. We keep that answer and those IDs with the analytics data. This needs no tracking prompt and does not use the advertising identifier.

Advertising measurement, sent to Meta

Starting with version 1.0.5, the app includes Meta’s SDK (App Events), so that we can see which of our Facebook and Instagram ads bring people to Shrink and lead to a purchase. Meta Platforms, Inc. receives this data, or Meta Platforms Ireland Limited if you are in the EEA, the UK or Switzerland. The SDK starts only once you have answered Apple’s tracking prompt, which the app shows after the photo library permission. If your App Store account is in the EEA, the UK or Switzerland, it starts only if you tap Allow. Once started, it sends:

• that the app was installed, when it is opened and how long it stays open;
• completed purchases and trial starts, with the plan, price and currency;
• a random ID that the SDK creates on the phone;
• device details: model, iOS version, app version, language, time zone, mobile carrier, screen size and number of processor cores;
• your IP address, which any connection carries;
• crash and error reports about Meta’s own code;
• your device’s advertising identifier (IDFA), only if you allow tracking.

This is how information from Shrink, as from other apps and websites that use Meta’s technologies, reaches Meta. Meta uses it to provide measurement services and to target and deliver ads, including ours. If you allow tracking, Meta can match these events with what it knows from those other apps and websites to tell us which ads led to an install or a purchase. That is tracking as Apple defines it. If you ask the app not to track, iOS gives the SDK no advertising identifier and blocks Meta’s tracking server, and Meta can count installs from its ads only in aggregate, through Apple’s SKAdNetwork. Meta processes this data under its own privacy policy, at facebook.com/privacy/policy.

To opt out of this collection and its use for ad targeting:

• on your iPhone, turn tracking off for Shrink, or turn off Allow Apps to Request to Track, in Settings › Privacy & Security › Tracking. You can do this at any time, and the app works the same;
• if you have a Facebook or Instagram account, disconnect your activity from other apps and websites in Meta’s Accounts Center, under Your information and permissions › Your activity off Meta technologies, and change how ads are chosen for you under Ad preferences, at accountscenter.facebook.com.

What the app never sends

• your videos, or their frames, thumbnails or file names;
• photo identifiers, or the contents of your photo library;
• the location stored in your videos;
• your contacts;
• your name or email address;
• Apple’s advertising identifier (IDFA), unless you allow tracking, in which case Meta receives it as described above.

How we use it

There is no account, and we never set a user ID. The analytics data sent to Google is not linked to your identity and is not used for tracking. The data sent to Meta measures our Facebook and Instagram ads, and if you allow tracking, that measurement is tracking as Apple defines it. We do not sell any of it, and the app shows no ads. We use the data to see where people get stuck in the app, and which Apple Ads, Facebook and Instagram campaigns bring people who go on to use Shrink.

Because of Meta’s SDK, our App Store privacy label for version 1.0.5 lists Identifiers (Device ID), Usage Data (Product Interaction, Advertising Data) and Purchases (Purchase History) as Data Used to Track You and Data Linked to You. Location (Coarse Location), Diagnostics and Other Data are listed as Data Not Linked to You.

3. What stays on your device

The app does store things — it just stores them on your iPhone, inside its own sandboxed container, where they are readable only by the app itself:

The app does not send these records anywhere, and deleting the app removes all of them. Some analytics events in section 2 overlap with them, such as how many videos a batch compressed or the plan name on a purchase. Compressed video files that you chose to save are written into your Photos library and belong to you and to iOS from that point on — deleting Shrink does not delete them.

4. Permissions the app asks for

iOS will prompt you for these. Each one is used for exactly the purpose stated, and for nothing else. You can revoke any of them at any time in Settings › Shrink.

• Photo library access (read). To list your videos, show their sizes and thumbnails, and read a clip in order to compress it. The library is read on device; nothing read from it is transmitted. The app does send an analytics event with your answer to the permission prompt: full, limited or denied.
• Photo library access (add). To save the compressed copy back into your library. Without this the app can compress but has nowhere to put the result.
• Tracking. Apple’s tracking prompt, shown after the photo library permission. Your answer decides whether Meta receives your device’s advertising identifier, as section 2 describes, and in the EEA, the UK and Switzerland whether Meta’s SDK runs at all. The app works the same either way.
• Notifications. Batch progress while you are in another app, a completion notice, a note if a Pass has expired, the reminder about videos still waiting, and the occasional news notification described in section 2. All but the news notification are generated on your device.
• Background processing. On iOS 26 and later, a batch you start on a paid plan keeps running after you leave the app or lock the phone, and iOS shows its progress on the Lock Screen. On the free plan and on earlier versions it continues only for the short window iOS grants a backgrounded app. Background app refresh is also used to check for new large videos if you turn monitoring on. Nothing the app reads from your library leaves the device during any of this.

The app also reads your device’s thermal state so it can pause itself when the phone gets warm. That reading never leaves the device.

5. Purchases and Apple

Buying a One-Month Pass, a Monthly subscription or the Lifetime unlock is a transaction between you and Apple, handled entirely inside Apple’s App Store using StoreKit. We never see, receive or store your name, billing address, card details or Apple Account. There is no payment processor, subscription-management service or purchase middleware between you and Apple; the app verifies your entitlement locally against the signed receipt Apple places on the device. When a purchase starts, completes or fails, the app sends an analytics event with the plan name, as section 2 describes. Meta’s SDK also records completed purchases and trial starts, with the price, to measure our ads.

Apple processes that transaction under its own privacy policy, which we do not control. See apple.com/legal/privacy.

Separately, Apple may provide us with aggregated, anonymised reports through App Store Connect — for example how many people downloaded the app, sales totals, and crash counts. These reports are produced by Apple, are subject to your device’s Share iPhone Analytics and Share with App Developers settings, and never identify you to us. You can switch that sharing off in Settings › Privacy & Security › Analytics & Improvements.

6. If you email us for support

Emailing shrink@ripeseed.io is the one situation in which we hold data that identifies you, for the obvious reason that we cannot reply otherwise. In that case we process your email address and whatever you choose to put in your message, solely to answer you. We do not add you to a mailing list, use your address for marketing, or pass it to anyone else.

Under the GDPR, our legal basis is legitimate interest (responding to a request you made of us). We keep support correspondence for up to 24 months and then delete it. Ask us to delete it sooner and we will.

Please do not send us videos, screenshots containing personal information, or anything else sensitive. We do not need them, and we would rather not hold them.

7. This website

shrink.ripeseed.io sets no cookies, runs no analytics, embeds no tracking pixels, and loads no third-party resources — no external fonts, no CDN scripts, no social widgets, no embedded video. Every font, image and stylesheet is served from this domain. There is nothing here to consent to, which is why you were not asked.

Like any website, it is served by hosting infrastructure (Amazon Web Services) that may write standard technical request logs — IP address, timestamp, requested file, user agent — for security, abuse prevention and keeping the site up. Those logs are not used to profile you, are not combined with anything else, are not sold or shared, and are retained for no longer than is necessary for those purposes.

8. Third parties and data sharing

We do not sell your personal information, and we do not work with data brokers. We send the data in section 2 to Meta to measure our advertising, and some privacy laws, California’s among them, may treat that as sharing for cross-context behavioural advertising. Section 10 covers what you can do about it.

Four third parties are involved:

• Google LLC runs Google Analytics for Firebase and processes the analytics data in section 2 for us. It receives the app instance ID, the usage events, the details Firebase adds, the Apple Ads campaign, ad group and keyword IDs, and the push token that Firebase Cloud Messaging uses to deliver notifications. It works out your country and city from your IP address. The app sets Google’s advertising consent to denied, so Google gets nothing for advertising use. Google’s privacy policy is at policies.google.com/privacy.
• Meta Platforms, Inc., or Meta Platforms Ireland Limited for people in the EEA, the UK and Switzerland, receives the app events described in section 2 through Meta’s SDK, and your device’s advertising identifier if you allow tracking. Meta uses them to provide measurement services and to target and deliver ads, including ours, under its own terms and privacy policy, at facebook.com/privacy/policy.
• Apple distributes the app and processes purchases, as section 5 describes. For Apple Ads attribution, Apple’s attribution server receives a token from the app once per install. Apple answers whether the install came from an Apple Ads ad and, if it did, with the campaign, ad group and keyword IDs.
• Amazon Web Services hosts this website, as section 7 describes, and receives nothing from the app.

Google and Meta each receive this data under terms that require them to keep it secure and to protect it to at least the standard this policy describes. Apple and Amazon Web Services handle only what sections 5 and 7 describe.

If we were ever legally compelled to hand over data, we would have no videos to give, and nothing that links the analytics data to a person’s identity. Meta holds the advertising measurement data under its own policy.

9. Children

Shrink is a general-audience utility. It is not directed at children under 13 (or the equivalent minimum age in your country), and we do not knowingly collect personal information from children. If you believe a child has somehow provided us with personal data, write to shrink@ripeseed.io and we will delete it.

10. Your rights

Privacy law gives you rights over personal data a company holds about you. The analytics data from the app carries a random app instance ID and no name, email address or account, so we generally cannot find the records that belong to one person. You can still write to shrink@ripeseed.io with any request, and we will reply.

If you are in the EEA, the UK or Switzerland (GDPR / UK GDPR)

RipeSeed is the controller of the personal data this policy describes. The legal bases we rely on are:

• for Meta’s SDK, your consent, which you give by tapping Allow on Apple’s tracking prompt. In these countries the SDK does not run unless you do. You can withdraw consent at any time in Settings › Privacy & Security › Tracking;
• for the analytics sent to Google and Apple Ads attribution, your consent, which you give by tapping Share on the question the app asks. You can withdraw it at any time with Settings › Share usage data in the app;
• for push notifications, our legitimate interest in telling you about new features, within the notification permission you give iOS. You can object by turning off News from Shrink in the app’s Settings;
• for support emails, our legitimate interest in answering you, as section 6 describes.

RipeSeed and Meta Platforms Ireland Limited are joint controllers for collecting data through Meta’s SDK and sending it to Meta, under Meta’s Controller Addendum. Meta Platforms Ireland is responsible for what happens to the data once it has it, and you can exercise your rights over that data with Meta directly, as its privacy policy explains.

Google LLC and Meta Platforms, Inc. are in the United States. Personal data sent to them from the EEA, the UK or Switzerland is transferred under the EU-U.S. Data Privacy Framework, its UK Extension and the Swiss-U.S. Data Privacy Framework, under which both companies are certified, or under the European Commission’s Standard Contractual Clauses.

You have the right to access, rectify, erase, restrict and port your personal data, to object to processing, to withdraw consent, and to lodge a complaint with your supervisory authority. If you have emailed us for support, section 6 applies and you may exercise all of the above rights over that correspondence by writing to shrink@ripeseed.io.

If you are in California (CCPA / CPRA)

Starting with version 1.0.5, the app collects the data described in section 2. We do not sell it, and we do not collect sensitive personal information. Sending app events to Meta for ad measurement, with your advertising identifier if you allow tracking, may count as sharing under the CPRA. Choosing Ask App Not to Track, or turning tracking off for Shrink in Settings › Privacy & Security › Tracking, stops Meta receiving the advertising identifier. Meta still receives the app events without it. You retain the rights to know, delete, correct, opt out of sale or sharing, and to non-discrimination for exercising them. Write to shrink@ripeseed.io to use any of them.

Other jurisdictions

Equivalent rights under other privacy laws are honoured on the same basis. Contact us and we will help.

11. Retention and deletion

App data lives on your device for as long as you keep the app, and is destroyed when you delete it. To remove it immediately, delete Shrink from your iPhone. Compressed videos you chose to keep remain in your Photos library, and originals you replaced remain in Recently Deleted for 30 days, both under your control rather than ours.

Google Analytics keeps event data from the app for up to 14 months. Once you delete the app it sends nothing more, and a new install gets a new app instance ID. Because the analytics data is not linked to your identity, we generally cannot find your records to delete them sooner. The push token stops working once you delete the app. Meta keeps the events it receives under its own policy; to have Meta delete what it holds about you, use the tools in its Accounts Center or contact Meta as its privacy policy explains. There is no account to close.

12. Security

Your videos, thumbnails and file names are never transmitted, so no one can intercept them in transit and no server holds a copy that a breach could expose. The analytics data in section 2 goes to Google and is stored in Google Analytics, and the advertising measurement data goes to Meta. On the device, app data sits in the standard iOS application sandbox and is protected by the device encryption and passcode you already use.

13. Changes to this policy

If we change this policy we will update the Last updated date at the top and post the new version here. The 14 September 2026 update describes the analytics and Apple Ads attribution added in version 1.0.5 of the app. The 16 September 2026 update adds Meta’s SDK and Apple’s tracking prompt, also new in version 1.0.5, and the legal bases for people in the EEA, the UK and Switzerland. The 17 September 2026 update adds the question about usage data asked there, and the Share usage data switch. If a later version changes what the app sends, we will update this page and our App Store privacy label.

14. Contact

Questions, corrections and complaints about privacy:
shrink@ripeseed.io

RipeSeed — publisher of Shrink: Video Size Compressor.