Legal
Privacy Policy
Effective October 10, 2026
The short version: Seize apps are built to work without your data. We don't run accounts, we don't use advertising SDKs, and we don't sell or share anything. When you buy something in Drip, Anchor, Kover, Tandem, Meso or Grain, Apple tells us about the purchase, without your name or email (see Purchases). Some apps use RevenueCat for purchase analytics only (see Atino, Cycle Timers, GamingHub, Tempo, Roomy, Readably and, from version 0.1.2, Overbit). What you put into an app stays on your device and in your own iCloud unless the app's own section below says otherwise (see GamingHub, Atino, Overbit and Tempo).
Garum is the exception: it has accounts, a server in the EU and user content, so it has its own privacy policy and terms of use.
Atino is another exception: your CV, redacted on your iPhone, is sent to third-party ranking services through a Seize relay when you allow it, and its subscription is reported to RevenueCat for purchase analytics, so it has its own privacy policy.
Overbit is another exception: to send you alerts it registers a random install identifier and your push-notification token with a Seize server and, from version 0.1.2, its purchases are reported to RevenueCat for purchase analytics, so read its section below.
GamingHub is another exception: to run a room it sends your display name, avatar and what you type in a game to a Seize server (Supabase), and its purchases are reported to RevenueCat for purchase analytics, so read its section below.
Tempo is another exception: its purchases are reported to RevenueCat for purchase analytics, so read its section below.
Cycle Timers is another exception: its purchases are reported to RevenueCat for purchase analytics, so read its section below.
Roomy is another exception: from version 0.0.3 its purchases are reported to RevenueCat for purchase analytics, so read its section below.
Readably is another exception: it downloads its natural voices once from Hugging Face when you ask for them, and its use of RevenueCat is for purchase analytics, so read its section below.
Who we are
Seize Apps is an independent app studio run by Izotz Cristobal Mota and Sendoa Sola from the Basque Country, Spain ("we", "us"). This policy covers all Seize apps distributed through the Apple App Store and TestFlight — currently Cycle Timers, Tempo, Drip, Anchor, Kover, Tandem, Meso, Grain, GamingHub, Atino, Overbit, Roomy and Readably. Each app is published on the App Store by one of us: the seller named in its App Store listing is the data controller for that app, and is named in its section below. Where an individual app differs, its section is the authoritative one.
What we collect
Nothing, by default. Our apps do not require an account, do not include advertising or tracking SDKs (the only third-party analytics is RevenueCat's purchase analytics in Atino, Cycle Timers, GamingHub, Tempo, Readably and, from version 0.1.2, Overbit, see their sections), and do not transmit the content you create to us. We cannot see your timers, work sessions, expenses, receipts, routines, or any other content you create in a Seize app.
Purchases are processed entirely by Apple. Where an app sells a one-time "Pro" unlock, the app checks that purchase with Apple's StoreKit on your device and remembers only whether it is active; we never see who bought it (Atino, Cycle Timers, GamingHub, Tempo and, from version 0.1.2, Overbit also report purchases to RevenueCat for analytics; see their sections). We receive aggregated, anonymized sales and crash statistics from Apple's App Store Connect (for example, the number of downloads by country). These statistics contain no personal identifiers.
Purchases. In the apps published by Sendoa Sola (Drip, Anchor, Kover, Tandem, Meso and Grain), when you buy something (a tip, "Pro" or a subscription), start a trial or redeem a code, Apple tells us, and also about its renewals and refunds: which product, when, in which App Store country, the price and currency, and some transaction numbers and a pseudonym that Apple generates for each account and app. It does not include your name, your email or your Apple ID. We keep it on a server of our own, only to keep our accounts and to handle refunds or questions about a purchase. We do not share it with anyone or use it for advertising or analytics. We keep it for six years, the time the law requires for bookkeeping (basis: complying with our legal bookkeeping obligations, and our legitimate interest in handling questions and refunds). Nothing changes for the apps published by Izotz Cristobal Mota: what their sections say about RevenueCat stays the same.
Where your data lives
- On your device. App content is stored locally, in the app's private container (and, for apps with widgets, a shared App Group container that only the app and its own widget can read).
- In your iCloud. Our apps sync through your personal iCloud account under Apple's terms, unless you turn it off in Settings or the app's own section below says otherwise — we never have access to it.
Per-app details
Cycle Timers
Cycle Timers stores your timers on your device, in a private App Group container shared only with the app's own Home Screen and Lock Screen widgets. Notifications are scheduled locally on your device. Cycle Timers has no account system, no advertising SDK and no developer-operated service that receives your timers. Its one third-party library, RevenueCat's, is used for purchase analytics only (see Purchase analytics below).
Purchases. Apple processes the optional one-time Cycle Pro purchase. Cycle Timers uses StoreKit's verified transactions to determine access on your device, including whether your Apple ID bought Cycle when it was a paid app (before version 0.0.20), in which case Pro is already yours. The developer does not receive your payment-card details through Cycle Timers.
Purchase analytics (RevenueCat). Cycle Timers includes RevenueCat's software library, used for analytics only: Apple's StoreKit still handles every purchase and Cycle Timers still decides on your device whether Cycle Pro is active. Whenever Cycle Timers runs, the library gives your install a random anonymous ID and sends RevenueCat, Inc. (United States) that ID, your device's vendor identifier (a number Apple gives the apps of one developer on a device; it is not the advertising identifier), your App Store purchases (product, price, dates and Apple's transaction data), the time you last used Cycle Timers, your device model, operating system and app version, language and App Store country. When the Cycle Pro screen opens, Cycle Timers also tells it that the screen opened (and which limit led you there: the timer limit, a widget size or Settings), and whether you tapped Buy, cancelled, are waiting for approval or restored. Like any server, RevenueCat also sees the internet address of each request. We use it to count purchases and to see how people move through the purchase screen. Cycle Timers never gives RevenueCat your timers (their names, icons, intervals or dates), your name or your email, and we do not enable its advertising integrations: it is not used to track you. RevenueCat is our processor; it keeps this data on Amazon Web Services in the United States, under a data processing addendum that makes the EU standard contractual clauses available for that transfer. It states no fixed retention period, and deleting Cycle Timers does not delete what it already holds: write to hello@seizeapps.com and we will ask it to delete the record.
Published on the App Store by Izotz Cristobal Mota.
Tempo
Tempo stores work sessions, schedules, working-day preferences, work-zone definitions and correction history on your device. A local App Group shares the information needed by Tempo's own widgets. Tempo has no account system, advertising SDK or developer-operated service that receives your work records or location history. Its one third-party library, RevenueCat's, is used for purchase analytics only (see Purchase analytics below).
Storage and backups. This version of Tempo does not implement app-managed iCloud synchronization. Device backups and system services may be governed by your Apple account and device settings; they are separate from synchronization implemented by Tempo.
Location and maps. Manual tracking is available without location permission. When you enable automatic tracking, Tempo uses Apple's Core Location services and local evidence to evaluate arrivals, departures and home-work routines. You control location permissions in iOS Settings. Place search, map display and route estimates use Apple MapKit; requests and relevant coordinates may be processed by Apple under its terms. Saying that the developer does not collect location does not mean that Apple platform services never process it.
Purchases. Apple processes Tempo Pro purchases and subscription renewals. Tempo uses StoreKit's verified transactions to determine access on the device. The developer does not receive your payment-card details through Tempo.
Purchase analytics (RevenueCat). Tempo includes RevenueCat's software library, used for analytics only: Apple's StoreKit still handles every purchase and Tempo still decides on your device whether Pro is active. Whenever Tempo is open, the library gives your install a random anonymous ID and sends RevenueCat, Inc. (United States) that ID, your iPhone's vendor identifier (a number Apple gives the apps of one developer on a device; it is not the advertising identifier), your App Store purchases and subscription status (product, price, dates and Apple's transaction data), the time you last used Tempo, your iPhone model, iOS and app version, language and App Store country. When the Tempo Pro screen opens, Tempo also tells it which screen it was (and, inside the app, which Pro feature led you there), which plan you chose, and whether you bought, cancelled or restored. Like any server, RevenueCat also sees the internet address of each request. We use it to count subscribers, trials and renewals and to see how people move through the purchase screen. Tempo never gives RevenueCat your work sessions, zones, locations, schedules, name or email, and we do not enable its advertising integrations: it is not used to track you. RevenueCat is our processor; it keeps this data on Amazon Web Services in the United States, under a data processing addendum that makes the EU standard contractual clauses available for that transfer. It states no fixed retention period, and deleting Tempo does not delete what it already holds: write to izotz@seizeapps.com and we will ask it to delete the record.
Exports and recap cards. You can export your records or create a recap image. Review exports before sharing them because record and diagnostic files may contain sensitive work or location information. Recap images are composed from a limited snapshot that excludes precise coordinates, workplace names and precise start/finish routines; totals are shown by default and broad location-category breakdowns are optional. Share and Copy do not require Photos access. Save requests add-only Photos permission when needed. A chosen share destination, clipboard service, saved image or external backup has its own handling and retention; erasing Tempo's local data does not delete copies you have already exported or shared.
Your controls. You can edit or remove workplaces, correct records, export data and erase local Tempo data in the app. You can revoke location, notification or Photos permissions in iOS Settings. Restricting a permission may limit automation or saving, while manual tracking and record correction remain available.
Published by Izotz Cristobal Mota. For questions about Tempo's data handling, contact izotz@seizeapps.com.
Drip
Drip stores the services you track — name, cost, billing cycle, payment dates, category, tags, notes and payment-method label — on your device, in a private App Group container shared only with Drip's own Home Screen and Lock Screen widgets and its Siri shortcuts. Drip has no account system, no analytics and no third-party code that receives your data. It offers two optional purchases: a one-time "Drip Pro" unlock that opens the app's extra features (Apple checks the entitlement on your device, including Family Sharing; the app stores only whether it is active), and a tip jar of one-off purchases that unlock nothing and change nothing about the app. Apple processes both; we never see your payment details and the app stores nothing about them beyond that local flag and a local count of how many times you have tipped. What Apple tells us about each purchase is under Purchases.
iCloud sync is on by default: your services sync between your devices through your personal iCloud account, under Apple's terms — we never have access to it. Turning it off in Settings keeps your data on the device only. Payment reminders and the weekly summary are local notifications, scheduled on your device.
Published on the App Store by Sendoa Sola.
Anchor
Anchor is a daily-support tool for people recovering from an eating disorder, meant to accompany professional treatment. Everything you enter — routine blocks and confirmations, emotional check-ins and their optional notes, urge-surfing and breathing sessions, coping-strategy usage, your safety plan (contacts, strategies, warning signs) and plans for disruptions — is stored on your device, in the app's private container. The urge-surfing Live Activity shows only its timer on your Lock Screen; it is drawn on the device and carries none of what you enter. Anchor has no account system, no analytics, no advertising, no AI chat and no third-party code that receives your data. It offers an optional tip jar: one-off purchases that change none of the app's tools — no feature of Anchor is ever behind a payment. As a thank-you, any tip also opens three optional colour themes. Apple processes the purchases; we never see your payment details. To know whether you have tipped, Anchor reads its own tips in your App Store purchase history on your device, with Apple's StoreKit, and keeps only that fact and a local count of how many times you have tipped; the app sends none of it to us. What Apple tells us about each tip is under Purchases. The name you may enter in "About you" is used only in on-device messages.
Health data. Anchor can optionally read sleep analysis, heart-rate variability, step count and exercise time from Apple Health, only after you grant permission (Settings › Health data; off by default). Anchor reads this data to show you qualitative context about rest and movement; it never writes to Health, never reads weight, body mass, body-fat or nutrition data, never uploads Health data anywhere, and never uses it for advertising or shares it with third parties. Health data stays on your device and is excluded from iCloud sync.
iCloud sync is on by default so your routines, check-ins and plans follow you between your devices through your personal iCloud account (Apple's private CloudKit database), under Apple's terms — we never have access to it. You can turn it off in Settings; your data then stays on the device only. Routine reminders, the daily check-in reminder and Live Activities are scheduled and rendered locally on your device. Emergency numbers shown in the safety plan are public helplines for your region; tapping one places a normal phone call.
Anchor is not a medical device and does not replace professional treatment. It deliberately contains no calorie, weight or body-measurement tracking.
Published on the App Store by Sendoa Sola.
Kover
Kover stores the products you add — name, category, store, purchase date and amount, country, warranty dates, serial number, support contact, notes and the receipt photo — on your device, in the app's private container. Kover has no account system, no analytics and no third-party code that receives your data. It offers two optional purchases: a one-time "Kover Pro" unlock that opens the app's extra features (Apple checks the entitlement on your device, including Family Sharing; the app stores only whether it is active), and a tip jar of one-off purchases that unlock nothing and change nothing about the app. Apple processes both; we never see your payment details and the app stores nothing about them beyond that local flag and a local count of how many times you have tipped. What Apple tells us about each purchase is under Purchases.
Receipts and the camera. When you scan a receipt, Kover uses the camera (or a photo or PDF you choose) and reads the text with Apple's on-device Vision framework. The image and the recognised text never leave the phone; the photo is kept only because it is your proof of purchase. Camera and photo-library access are requested only when you use those features.
iCloud sync is on by default so your products and receipt photos follow you between your devices through your personal iCloud account, under Apple's terms — we never have access to it. Turning it off in Settings keeps your data on the device only. Warranty reminders are local notifications, scheduled on your device. The CSV export and the per-product PDF are files you create and share yourself.
Published on the App Store by Sendoa Sola.
Tandem
Tandem stores the two partner names, their monthly incomes, every shared expense (amount, category, date, who paid, how it was split, optional name) and each settlement on your device, in a private App Group container shared only with Tandem's own widgets. Tandem has no account system, no analytics and no third-party code that receives your data. It offers two optional purchases: a one-time "Tandem Pro" unlock that opens the app's extra features (Apple checks the entitlement on your device, including Family Sharing; the app stores only whether it is active), and a tip jar of one-off purchases that unlock nothing and change nothing about the app. Apple processes both; we never see your payment details and the app stores nothing about them beyond that local flag and a local count of how many times you have tipped. What Apple tells us about each purchase is under Purchases. One phone keeps the books for both partners; nothing is sent to the other person's device or to anyone else.
iCloud sync is on by default so your expenses follow you between your own devices through your personal iCloud account, under Apple's terms — we never have access to it. Turning it off in Settings keeps your data on the device only. The weekly and month-end reminders are local notifications.
Published on the App Store by Sendoa Sola.
Meso
Meso stores your training programmes (blocks, sessions, exercises and their prescriptions), every logged session (loads, reps, reps in reserve, notes, the gym you used) and your own exercises and gyms on your device, in the app's private container. Meso has no account system, no analytics and no third-party code that receives your data. It offers two optional purchases: a one-time "Meso Pro" unlock that opens the app's extra features (Apple checks the entitlement on your device, including Family Sharing; the app stores only whether it is active), and a tip jar of one-off purchases that unlock nothing and change nothing about the app. Apple processes both; we never see your payment details and the app stores nothing about them beyond that local flag and a local count of how many times you have tipped. What Apple tells us about each purchase is under Purchases.
Apple Health. Off by default. If you switch it on in Settings, each finished session is written to Health as a strength-training workout (start, end and name) so it counts towards your activity. Meso never reads anything from Health and never uploads Health data anywhere; the permission and the preference live on that device only.
iCloud sync is on by default so your programmes and sessions follow you between your devices through your personal iCloud account, under Apple's terms — we never have access to it. Turning it off in Settings keeps your data on the device only. Meso has no rest timer and sends no notifications. While a session is open, a Live Activity shows the current exercise and the next set on your Lock Screen; it is drawn on the device from what the app hands it and ends with the session. The week text and the block CSV you send to a coach are files you create and share yourself.
Published on the App Store by Sendoa Sola.
Grain
Grain stores what you log — each food with its meal, day, grams and the nutrition values copied from its source — your daily targets, and the foods and recipes you create, correct or scan on your device, in the app's private container and a private App Group container shared only with Grain's own widgets. Grain has no account system, no analytics and no third-party code that receives your data. It offers optional purchases: a one-time "Grain Pro" unlock that opens the app's extra features, with a free 30-day trial you can take once per Apple ID (Apple checks the entitlement on your device, including Family Sharing; the app stores only whether it is active and, during the trial, when it ends), and a tip jar of one-off purchases that unlock nothing and change nothing about the app. Apple processes them; we never see your payment details and the app stores nothing about them beyond that local flag and a local count of how many times you have tipped. What Apple tells us about each purchase is under Purchases.
Barcodes and Open Food Facts. The food catalogue (CIQUAL and BEDCA) ships inside the app and is searched on the device. When you scan or type a barcode that is not among your own foods, Grain sends only that number to Open Food Facts (openfoodfacts.org, an open, non-profit food database) to look the product up; the request names the app, not you, and nothing from your diary is sent. Open Food Facts handles that request under its own terms.
Sending a product to Open Food Facts. When you save a food with a barcode, «Also send to Open Food Facts» is on by default and visible on the same form; you can turn it off, and Grain remembers your choice. While it is on, Grain sends that product — the barcode and its values per 100 g, plus its name and brand when it is new to Open Food Facts — through Grain's own Open Food Facts account, with a random identifier made for this installation so their moderators can tell contributions apart. Nothing from your diary, your targets or your Apple Account is sent. What you send is published there under the Open Database License, for anyone to use, and Grain cannot withdraw it; Open Food Facts handles it under its own terms.
Camera, labels and words. The camera is used only while you scan a barcode or photograph a nutrition label, and nothing is recorded. Labels, from the camera or a photo you choose, are read with Apple's on-device Vision framework; a meal you describe in words is interpreted on the iPhone (with Apple Intelligence where available). Neither the image nor the text leaves the phone.
Apple Health. Off by default. If you switch it on in Settings, each entry is written to Health as food (energy, protein, carbs and fat), and changed or removed there when you edit or delete it in Grain. Grain never reads anything from Health and never uploads Health data anywhere; the permission and the preference live on that device only.
iCloud sync is on by default so your diary, targets and foods follow you between your devices through your personal iCloud account, under Apple's terms — we never have access to it. Turning it off in Settings keeps your data on the device only. Grain sends no notifications.
Published on the App Store by Sendoa Sola.
GamingHub
GamingHub is a party-game app you play in a room with other people. It has no account, no email and no password.
To run a room, the app stores a display name you choose, an avatar, and an anonymous identifier created on your device. Those, and the game state of the room, are sent to our server and shown to the other players in that room. The server is Supabase, our processor, in the EU (Frankfurt, Germany). User content you type for the game — hints, slips, song picks and similar — is part of that game state and is shown to the other players. Secret game data (your role, word or cards) is sent only to your device.
Rooms are deleted when they empty, and in any case are purged after 12 hours. We do not keep a game history.
In Rewind, the words you type to find a song are sent to Apple's iTunes Search service. Each song's 30-second preview and artwork are streamed from Apple, and every revealed song links to Apple Music.
This release has no advertising and no tracking. We do not sell your data.
Purchases are processed by Apple. GamingHub checks with Apple's StoreKit, on your device, which games you have unlocked, and we never see your payment details.
Purchase analytics (RevenueCat). GamingHub includes RevenueCat's software library, used for analytics only: Apple's StoreKit still handles every purchase and GamingHub still decides on your device which games are unlocked. Whenever GamingHub is open, the library gives your install a random anonymous ID and sends RevenueCat, Inc. (United States) that ID, your iPhone's vendor identifier (a number Apple gives the apps of one developer on a device; it is not the advertising identifier), your App Store purchases in GamingHub (product, price, dates and Apple's transaction data), the time you last used GamingHub, your iPhone model, iOS and app version, language and App Store country. When a store sheet opens, GamingHub also tells it which game or bundle it was about and whether you tapped buy, bought, cancelled or restored. Like any server, RevenueCat also sees the internet address of each request. We use it to count purchases and to see how people move through the store sheet. GamingHub never gives RevenueCat your display name, avatar, room code or anything from a room, and we do not enable its advertising integrations: it is not used to track you. RevenueCat is our processor; it keeps this data on Amazon Web Services in the United States, under a data processing addendum that makes the EU standard contractual clauses available for that transfer. It states no fixed retention period, and deleting GamingHub does not delete what it already holds: write to hello@seizeapps.com and we will ask it to delete the record.
If you report a problem or a player, the app opens a message to hello@seizeapps.com. That report is an email you send; it is not stored in the game server.
Deleting the app removes the anonymous identifier and the data kept on the device. Rooms you played in disappear when they expire.
Published on the App Store by Izotz Cristobal Mota.
Atino
Atino ranks job ads against your CV. Your CV stays on your iPhone: Atino never uploads the PDF, and it removes your name and contact details on the phone before any text leaves it. Only after you allow it, the redacted text is sent through the Seize relay to Command Code and TypeSafe AI (Jev) to rank jobs and explain the fit; they may keep it under their own terms. The relay, which runs on Supabase in the EU (Frankfurt, Germany), keeps a small record per install — a random install ID, an App Attest key and the day's search counters — and deletes it after 60 days without activity. There is no account, no advertising and no tracking. Apple processes the subscription; we never see your payment details. Atino also reports your subscription to RevenueCat for purchase analytics (an anonymous ID, your App Store purchases and the time you last used the app); RevenueCat acts on our instructions and receives no CV text.
The full details — what is sent, who receives it, how long it is kept and how to withdraw — are in Atino's privacy policy.
Published on the App Store by Izotz Cristobal Mota.
Overbit
Overbit is a Bitcoin RSI alert app. It has no account, no sign-in and no password, and it does not trade or hold anything for you.
What the app sends to our server. Overbit uses a Seize server (Supabase, Frankfurt, Germany) to push you an alert when RSI crosses a level. Whenever the app is open and refreshes, it registers this install with a random identifier created on your device, your device language and region setting and whether Overbit Pro is unlocked on that install. While the Notifications switch in Settings is on and iOS allows Overbit to notify you, the registration also carries your Apple push-notification token and the timeframes, RSI length and levels you chose. Turning the switch off replaces that registration at once with one that has no token and no timeframes, and turning notifications off for Overbit in iOS does the same the next time you open Overbit, so the server stops sending you pushes. After you use Delete my data (see Your data below), the app does not register this iPhone again until you turn alerts on. The server keeps one record per install and does not delete it when the app is deleted, only when you use Delete my data; when Apple reports that a token is no longer valid, the server clears the token. The log of alerts already sent is deleted after 90 days.
Prices. The price and candles in the app come from our own server, not from an exchange and not from any service you connect to. The app asks our Supabase project for them. Like any server, it receives your IP address with each request; the request carries no identifier, our code does not read or store the address, and Supabase, as our hosting provider, may keep standard request logs under its own terms. The server itself reads public on-chain price data (PancakeSwap and Aerodrome pools on Base, Uniswap pools on Ethereum) through node providers, Alchemy and PublicNode. Those providers see only the server's requests for public blockchain data; they receive nothing from your phone and nothing about you.
Feedback (Overbit Pro). If you use the feedback box, the message you type is sent to the same Supabase project with a reply email (only if you enter one), the app version and build, the iOS version, the device model, your language and region setting, the random identifier above, the Pro flag and the timeframes you had on. We read it to give support; it is not published. We keep it until you ask us to delete it.
Purchases. Overbit Pro is a one-time purchase processed by Apple, which the app reads from StoreKit on your device. The server stores only a yes-or-no Pro flag next to the install identifier, so it can apply the Pro limits to alerts and feedback; we never see your name or payment details. The app also includes RevenueCat's library for purchase analytics: it is switched off in version 0.1.1, so nothing is sent to RevenueCat, and on from version 0.1.2 (see Purchase analytics below).
Purchase analytics (RevenueCat), from version 0.1.2. Version 0.1.1 sends nothing to RevenueCat. From version 0.1.2, Overbit includes RevenueCat's software library, used for analytics only: Apple's StoreKit still handles every purchase and Overbit still decides on your device whether Pro is active. Whenever Overbit is open, the library gives your install a random anonymous ID, separate from the install identifier above, and sends RevenueCat, Inc. (United States) that ID, your iPhone's vendor identifier (a number Apple gives the apps of one developer on a device; it is not the advertising identifier), your App Store purchases (product, price, dates and Apple's transaction data), the time you last used Overbit, your iPhone model, iOS and app version, language and App Store country. When the Overbit Pro screen opens, Overbit also tells it so, and whether you started a purchase or a restore and how it ended (bought, cancelled, pending or failed). Like any server, RevenueCat also sees the internet address of each request. We use it to count purchases and to see how people move through the Overbit Pro screen. Overbit never gives RevenueCat your alert settings, timeframes, push-notification token, install identifier, feedback, name or email, and we do not enable its advertising integrations: it is not used to track you. RevenueCat is our processor; it keeps this data on Amazon Web Services in the United States, under a data processing addendum that makes the EU standard contractual clauses available for that transfer. It states no fixed retention period, and neither deleting Overbit nor Delete my data removes what it already holds: if you bought Overbit Pro, write to hello@seizeapps.com with the Apple order or transaction ID from your receipt and we will look for the record and ask RevenueCat to delete it; without a purchase, nothing identifies the record as yours, so we cannot find it.
Overbit has no advertising and no tracking, and we do not sell your data. Apart from the purchase analytics above (from version 0.1.2), it has no analytics. Your settings, the alert history you see in the app and the random identifier stay on your device as well.
Your data. The server record is tied to a random identifier, not to your name, email or account. In Overbit, Settings › Your data › Delete my data removes at once this install's record on the server (registration, timeframes and alert log) and any feedback you sent from it, and turns alerts off. Your settings on the iPhone stay, and the app does not register this iPhone again until you turn alerts on (it still reads prices from the server, and any feedback you send still goes to it). Deleting the app alone does not remove the server record, so use Delete my data first. If you already deleted the app, write to hello@seizeapps.com: we can only match a record through a feedback message you sent from the app, which carries the identifier, and we will delete what we can match. Delete my data does not remove what RevenueCat holds from version 0.1.2 (see Purchase analytics above). You can stop pushes at any time with the Notifications switch in Overbit's Settings or in iOS Settings › Notifications.
Published on the App Store by Izotz Cristobal Mota.
Roomy
Roomy analyzes your photo library on your iPhone only: your photos, videos and their metadata are never uploaded, shared or sold. It keeps your review progress (which items you kept or marked for deletion), cleanup statistics and preferences on your device; deleting the app removes them. Roomy has no account system, no advertising SDK and no service of ours that receives your photos or what you do with them. Its one third-party library, RevenueCat's, is used for purchase analytics only and is part of the app from version 0.0.3 (see Purchase analytics below). If a photo or video is in iCloud Photos and not on the phone, iOS downloads it from your iCloud when Roomy needs to show or compress it; that transfer is between your iPhone and Apple.
Purchases. Apple processes Roomy Pro subscriptions and purchases; Roomy never sees your payment information.
Purchase analytics (RevenueCat). From version 0.0.3, Roomy includes RevenueCat's software library, used for analytics only: Apple's StoreKit still handles every purchase and Roomy still decides on your iPhone whether Roomy Pro is active. Whenever Roomy is open, the library gives your install a random anonymous ID and sends RevenueCat, Inc. (United States) that ID, your iPhone's vendor identifier (a number Apple gives the apps of one developer on a device; it is not the advertising identifier), your App Store purchases and subscription status (product, price, dates and Apple's transaction data), the time you last used Roomy, your iPhone model, iOS and app version, language and App Store country. When the Roomy Pro screen opens, Roomy also tells it which situation opened it (the onboarding, the daily swipe limit, one-tap cleanup, video compression or the upgrade button in Settings), which plan you chose and how a purchase or restore ended (bought, cancelled, pending, failed or restored). Like any server, RevenueCat also sees the internet address of each request. We use it to count subscribers, trials and renewals and to see how people move through the purchase screen. Roomy never gives RevenueCat your photos, videos or their metadata, what you kept or deleted, your name or your email, and we do not enable its advertising integrations: it is not used to track you. RevenueCat is our processor; it keeps this data on Amazon Web Services in the United States, under a data processing addendum that makes the EU standard contractual clauses available for that transfer. It states no fixed retention period, and deleting Roomy does not delete what it already holds: write to hello@seizeapps.com and we will ask it to delete the record. Versions of Roomy before 0.0.3 do not contain this library and send nothing to RevenueCat. RevenueCat's own policy is at revenuecat.com/privacy.
Emails and reminders. The email drafts the app opens (Suggest a Feature, Report a Bug, and Contact Support when the purchase screen cannot load its plans) go to hello@seizeapps.com only if you send them. Report a Bug and Contact Support fill in your app version, iOS version and iPhone model (Contact Support also your App Store country); you can read and change the draft first. Daily reminders, if you turn them on, are local notifications scheduled on your device.
The full details are in Roomy's privacy policy (English).
Published on the App Store by Izotz Cristobal Mota.
Readably
Readably reads text aloud and highlights the word being spoken. The text you paste and the PDF and text files you import are turned into text on your iPhone and kept in the app's private container, together with your reading position and preferences. They are never uploaded, shared or sold: Readably has no account system, no advertising SDK and no service of ours that receives your documents or what you listen to. They are not synced through iCloud; like other app data they are part of your device backups, under your Apple account settings. Deleting the app removes them. The voices built into iOS run on your iPhone, and Readably asks for no permissions: no location, contacts, photos, camera, microphone or notifications. A file you import is opened through the iOS file picker, which gives the app only the file you choose.
Natural voices (Hugging Face). Readably can download free natural voices to your iPhone (the open-source Kokoro model, between about 90 and 185 MB depending on the language). It does so only when you tap Download in Settings › On-device voices, or when you pick a natural voice whose files are not on the phone yet. The files come straight from Hugging Face (huggingface.co, Hugging Face, Inc., United States) and the content servers it uses. Like any server, Hugging Face sees the internet address of your request and the details iOS adds to every request (the app name and the system version); Readably sends it no text, no account and no identifier of ours. Once downloaded, the voices work offline and what you read is never sent anywhere to be read aloud. You can delete them in Settings at any time. Hugging Face's own policy is at huggingface.co/privacy.
Purchase analytics (RevenueCat). Readably includes RevenueCat's software library, used for analytics only: Apple's StoreKit would still handle any purchase and Readably would still decide on your iPhone what is unlocked. Readably 0.0.1 sells nothing. Whenever Readably is open, the library gives your install a random anonymous ID and sends RevenueCat, Inc. (United States) that ID, your iPhone's vendor identifier (a number Apple gives the apps of one developer on a device; it is not the advertising identifier), your iPhone model, iOS and app version, language and App Store country, and, once Readably has something to buy, your App Store purchases and subscription status (product, price, dates and Apple's transaction data). Like any server, RevenueCat also sees the internet address of each request. We use it to count people who use Readably and, later, subscribers and renewals. Readably never gives RevenueCat your documents, what you listen to, your name or your email, and we do not enable its advertising integrations: it is not used to track you. RevenueCat is our processor; it keeps this data on Amazon Web Services in the United States, under a data processing addendum that makes the EU standard contractual clauses available for that transfer. It states no fixed retention period, and deleting Readably does not delete what it already holds: write to hello@seizeapps.com and we will ask it to delete the record. RevenueCat's own policy is at revenuecat.com/privacy.
Emails. The email drafts the app opens (Suggest a Feature and Report a Bug) go to hello@seizeapps.com only if you send them. Report a Bug fills in your app version, iOS version and iPhone model; you can read and change the draft first.
Published on the App Store by Izotz Cristobal Mota. For questions about Readably's data handling, contact hello@seizeapps.com.
Notifications
Apps that remind you of things use local notifications, scheduled and delivered on your device. We do not operate push-notification servers for these features. Overbit is the exception: it registers with a Seize server so that the server can push its alerts.
Your rights
Because your data lives on your device, you exercise your rights directly: deleting content in an app deletes it; deleting the app deletes its container; turning iCloud sync off and deleting the app removes it from iCloud as well (or manage it under Settings › Apple Account › iCloud). Under the GDPR you also have rights of access, rectification, erasure, and portability — since we hold no personal data about you, there is typically nothing for us to produce, but you can always reach us with questions or requests at hello@seizeapps.com. The exception is Overbit, which keeps a record on our server under a random identifier: delete it in the app (Settings › Your data › Delete my data) or ask us there. For the record RevenueCat holds from version 0.1.2, write to us. Purchase notices (see Purchases) carry no name or email: to find the ones for a purchase we need its order ID, which is on the receipt Apple sends you.
Children
Our apps are general-audience utilities and do not knowingly collect personal information from anyone, including children.
Changes
If a future app or feature changes any of the above (for example, an app that adds an online service), we will update this policy and the app's App Store privacy label before that feature ships.
Contact
Seize Apps · Izotz Cristobal Mota & Sendoa Sola
hello@seizeapps.com