In short
- No account. No sign-up, no email, no password, no name. The App never asks who you are.
- No servers of ours. We operate no backend, no database and no cloud storage. Nothing is sent to us, ever. We could not look up your data if we wanted to.
- No advertising. No ad networks, no ad identifiers, no IDFA, no tracking prompt.
- No analytics. No crash SDKs, no usage tracking, no telemetry, no fingerprinting. The App contains zero third-party SDKs - every framework it uses is Apple’s own.
- No tracking and no profiling. We do not build profiles, make automated decisions about you, or sell or share your data with anyone. Not now, and not planned.
- Your data stays on your iPhone. Settings, saved cities and cached forecasts live in the App’s own storage on your device.
- Notifications are local. Severe weather alerts are composed on your device. There are no push tokens and no push server.
- Location leaves your device only as rounded coordinates, sent to Apple to fetch a forecast - never to us.
The rest of this policy explains the detail, including the Apple services the App relies on.
1. Who is responsible for your data
The data controller for the limited processing described here is:
- Controller
- CodeTech (NIP 7631936648)
- Country
- Poland
- Address
- Wrocław, Poland
- hello@cutthefluff.eu
- Website
- https://www.cutthefluff.eu
- App
- Kaisei Weather
We have not appointed a Data Protection Officer; the App’s processing does not require one. Please write to the email above with any privacy question.
Apple is a separate controller for the data it processes when the App calls its services (WeatherKit, Apple Maps, the App Store, iCloud). Apple’s handling of that data is governed by the Apple Privacy Policy, not by this one.
This policy covers the Kaisei Weather iPhone app and its Home Screen widgets. It does not cover our website, which is described separately in the website privacy policy.
2. What the App processes, and why
2.1 Your location
- What
- Your device’s geographic coordinates, from Core Location.
- Why
- To show the forecast where you are, and - only if you turn it on - to check for severe weather alerts where you are.
- Legal basis
- Your consent, Art. 6(1)(a) GDPR, given through the iOS location permission prompt. Withdrawable at any time.
- Shared with
- Apple, as rounded coordinates, to fetch the forecast and to look up the place name. Never with us.
- Stored
- The precise fix is never stored. Only a rounded coordinate is kept, on your device.
How this works in practice:
- The App asks for “When in use” location access the first time it needs a forecast for where you are. You may decline; the App then works with cities you add yourself.
- Before any request leaves your device, coordinates are rounded to two decimal places - about 1 km of precision. This is what is sent to Apple’s weather service, and it is what is cached on your device. Your exact position is never written to storage and never transmitted.
- To avoid repeated place-name lookups, the App reuses the last place name while your device stays within about 3 km of where that name was found. Standing still therefore costs no lookups at all.
- You can turn the whole thing off with Use Current Location in the App’s Settings, or in iOS Settings › Privacy & Security › Location Services.
2.2 Background location - only for severe weather alerts
- What
- Your device’s approximate location while the App is closed.
- Why
- To check whether a severe or extreme weather alert has been issued where you are.
- Legal basis
- Your consent, Art. 6(1)(a) GDPR - asked for separately and only if you enable alert notifications.
- Shared with
- Apple, as rounded coordinates, to fetch alerts. Never with us.
This happens only if you turn on severe weather alert notifications in Settings. Doing so asks for “Always” location access, because the check has to run when the App is not open.
While it is on, two things can trigger a check: an iOS Background App Refresh (requested no more often than every 30 minutes, though iOS decides when it actually runs), and iOS waking the App because your device moved roughly 500 m or more. Each check reads your device’s last known position, rounds it, asks Apple’s weather service for active alerts, and - if there is a new severe one - posts a notification on your device.
Turning the setting off stops the background monitoring and releases the “Always” permission. You can also revoke it in iOS Settings at any time.
2.3 City search
- What
- The text you type when searching for a city, and the city you pick.
- Why
- To offer autocomplete suggestions and to resolve a chosen city to coordinates and a time zone.
- Legal basis
- Performance of the contract, Art. 6(1)(b) GDPR - you asked the App to find a city.
- Shared with
- Apple Maps (MapKit), which performs the search. Never with us.
- Stored
- Your query is not stored. A city you add is saved on your device.
Search results are restricted to cities and other populated places, and searching makes no weather request - a forecast is fetched only once you actually add a city.
2.4 Weather data requests
- What
- A rounded coordinate and a time zone, sent to Apple’s WeatherKit service.
- Why
- To retrieve the forecast, alerts and climate averages the App displays.
- Legal basis
- Performance of the contract, Art. 6(1)(b) GDPR.
- Shared with
- Apple. Never with us.
Apple is the controller for these requests and describes its own handling in the Apple Weather privacy notice and the Apple Privacy Policy. Apple states that it does not use WeatherKit requests to build a user profile. We receive no copy, log or report of any request.
To limit requests, the App caches forecasts on your device and refetches only when the data is over 30 minutes old (60 minutes for the Locations list).
2.5 Purchases - Buy a Coffee
- What
- Which of the three coffees your Apple Account has bought.
- Why
- To unlock the themes you paid for, and to restore them on your other devices.
- Legal basis
- Performance of the contract, Art. 6(1)(b) GDPR.
- Shared with
- Apple processes the payment. We receive no personal data.
- Stored
- Nothing. Ownership is read from Apple on each launch and never written to the App’s storage.
All purchases go through Apple and StoreKit. We never see and never receive your payment card details, billing address, Apple Account email or Apple Account identifier. Apple is the merchant of record and the controller for payment data; see the Apple Privacy Policy and the Apple Media Services Terms and Conditions.
Because the App keeps no record of what you bought, a refund automatically re-locks the themes, and Restore Purchases simply re-reads your entitlements from Apple.
We do receive aggregated, anonymised sales reports from Apple through App Store Connect - totals by country and date. These contain no information identifying any individual purchaser.
2.6 Notifications
- What
- The notifications the App shows you about severe weather alerts.
- Why
- To warn you about severe and extreme weather where your device is.
- Legal basis
- Your consent, Art. 6(1)(a) GDPR, given through the iOS notification prompt.
- Shared with
- No one.
All notifications are local. They are composed on your device by the App and handed to iOS. There is no push notification service, no device token, no APNs registration and no server involved. Nobody - including us - can send you a notification through this App.
Alert notifications reproduce the issuing agency’s own text, unchanged, together with the agency’s name, as Apple’s WeatherKit terms require.
To avoid notifying you twice about the same alert, the App keeps a small list on your device of which alerts it has already shown. It records only each alert’s reference link and the time it was last seen, and forgets entries after 3 days.
You can turn notifications off in the App’s Settings or in iOS Settings › Notifications.
2.7 What is stored on your device
The App keeps the following in its own storage on your iPhone. None of it is transmitted to us.
| Where | What it holds |
|---|---|
| App database (SwiftData) | Your settings - temperature, wind, pressure and distance units; chosen theme and any custom theme colours; whether Use Current Location and alert notifications are on - plus your saved cities (name, region, rounded coordinates, time zone, order, date added), and a record of which Terms version you accepted and when. |
Recovery file (PreferencesBackup.json) | A plain-text copy of the same settings and saved cities, so your setup survives a failed database upgrade. Written whenever your settings change; read only during recovery. Your Terms acceptance is deliberately not copied here - after a recovery you are asked to accept again rather than assumed to have agreed. |
Widget cache (WidgetCache.json, in a shared App Group) | What the Home Screen widgets need: your units and theme, your saved cities, the last rounded device location, and recent forecasts (about 24 hours of hours and 7 days of days). |
Alert list (AlertLedger.json) | Which alerts have already been shown, as described in 2.6. Entries older than 3 days are discarded. |
Note on recovery: if the App’s database cannot be opened after an update, the App moves the old database into a StoreQuarantine folder inside its own container rather than deleting it, so a later version can still recover it. The three most recent quarantined copies are kept and older ones are removed. These files stay on your device, inside the App’s private container, and are deleted when you delete the App.
2.8 Diagnostics
The App writes a small number of technical messages to the Apple system log on your device - for example, that a purchase failed or that the database was recovered. These stay on your device and are not collected by us.
Separately, if you have opted in to sharing analytics and crash data with app developers in iOS Settings › Privacy & Security › Analytics & Improvements, Apple may provide us with crash reports and aggregate performance statistics through App Store Connect. These come from Apple, are aggregated or pseudonymised by Apple, and contain no information we can link to you. You control this in iOS Settings; it is off unless you turned it on.
3. What the App does not collect
To be explicit, the App does not collect, request, access or process:
- your name, email address, phone number, postal address or date of birth;
- any account, username or password - there are none;
- your contacts, calendar, photos, camera, microphone, files, Health data or HomeKit data;
- your Apple Account identifier, email or payment details;
- any advertising identifier (IDFA), device identifier, IP-based identifier or fingerprint;
- your browsing history, app usage, screen views, taps or session length;
- your precise position in stored or transmitted form (coordinates are always rounded first).
The App shows no advertising, performs no tracking across apps or websites (and therefore never shows the App Tracking Transparency prompt), contains no third-party SDK of any kind, and does no profiling or automated decision-making within the meaning of Art. 22 GDPR. We do not sell, rent, trade or share your personal data, and we have never done so.
4. iCloud and device backups
The App does not sync your data to iCloud. There is no CloudKit integration and no cross-device synchronisation: your settings and saved cities live on each device separately.
However, like any iOS app, the App’s storage is included in your device backup if you have one enabled. So:
- With iCloud Backup on, a copy of the App’s local data forms part of your encrypted iCloud backup, held in your iCloud account under your control and governed by Apple’s terms and privacy policy. We have no access to it.
- With backups to a Mac or PC, the same data is included in that local backup.
- With backups off, the App’s data exists only on your device.
You can manage this in iOS Settings › [your name] › iCloud › Backup.
5. Who your data is shared with
We share your personal data with no one, because we never receive it.
The App communicates only with Apple, which acts as an independent controller for:
| Apple service | What it receives | Reference |
|---|---|---|
| WeatherKit (Apple Weather) | A rounded coordinate and time zone, to return a forecast or alerts | Apple Weather & Privacy |
| Apple Maps (MapKit) | Your search text; a coordinate for reverse geocoding | Apple Maps & Privacy |
| App Store / StoreKit | Your purchase and entitlement information | Apple Privacy Policy |
| iCloud | Your device backup, only if you enable it | Apple Privacy Policy |
There are no other processors, no sub-processors of ours, no hosting provider, no database provider and no third-party service of any kind. We use no external backend - not Supabase, Firebase, AWS, or anything comparable.
We may disclose information if we are legally required to - but in practice we hold no personal data about you to disclose.
6. International transfers
Because we receive no personal data, we make no international transfers.
Apple may process the data described in section 5 on servers outside the European Economic Area, including in the United States. Apple is responsible for the legal safeguards covering those transfers - such as the European Commission’s Standard Contractual Clauses and the EU–U.S. Data Privacy Framework - as described in the Apple Privacy Policy.
7. How long data is kept
| Data | Retention |
|---|---|
| Settings, saved cities, Terms acceptance | Until you change or delete them, or delete the App |
| Recovery file | Overwritten whenever settings change; deleted with the App |
| Cached forecasts | Replaced on refresh; roughly 24 hours of hourly and 7 days of daily data |
| Alert list | 3 days after an alert is last seen |
| Quarantined database copies | The 3 most recent are kept; deleted with the App |
| Anything on our systems | We hold nothing |
Deleting the App deletes all of it. Removing Kaisei Weather from your iPhone removes its entire container, including every file named above. Nothing survives except your purchases, which remain with your Apple Account so you can restore them.
8. Legal bases, summarised
| Processing | Legal basis (GDPR) |
|---|---|
| Location for forecasts | Consent, Art. 6(1)(a) |
| Background location for alerts | Consent, Art. 6(1)(a) |
| Notifications | Consent, Art. 6(1)(a) |
| City search, weather requests, local settings storage | Contract, Art. 6(1)(b) |
| Purchases and entitlement checks | Contract, Art. 6(1)(b) |
| Keeping records of Terms acceptance | Legitimate interest, Art. 6(1)(f) - demonstrating consent to the Terms |
Where we rely on consent, you can withdraw it at any time, with no effect on processing already carried out. Withdrawing consent will disable the related feature.
9. Your rights
Under the GDPR you have the right to request access to, rectification of, erasure of, or restriction of processing of your personal data; the right to data portability; the right to object to processing; and the right to withdraw consent.
Because the App stores your data only on your device and sends us nothing, these rights are mostly exercised directly, by you, without needing to contact us:
| Right | How to exercise it |
|---|---|
| Access / portability | All your data is in the App - Settings and Locations show everything it holds. A full copy is also available in your device backup. |
| Rectification | Edit your settings or saved cities in the App at any time. |
| Erasure | Delete a saved city by swiping it, reset a setting, or delete the App to erase everything at once. |
| Withdraw consent / object | Turn off Use Current Location or alert notifications in the App’s Settings, or revoke location and notification permissions in iOS Settings. |
| Restriction | Turn off Use Current Location; the App then only uses cities you chose. |
If you would like to make a request to us anyway, write to hello@cutthefluff.eu. We will respond within one month. Please note that we will usually have to tell you that we hold no personal data about you - this is not an evasion, it is the consequence of the App’s design. We cannot identify you from the App, so we may not be able to act on a request beyond explaining the above.
For Apple’s processing - forecast requests, map searches, purchases and iCloud backups - please contact Apple, which is the controller for that data.
Right to complain. You can lodge a complaint with a data protection supervisory authority, in particular in Poland:
Prezes Urzędu Ochrony Danych Osobowych (UODO)
ul. Stawki 2, 00-193 Warszawa, Poland
https://uodo.gov.pl
You may also complain to the supervisory authority of your own EU/EEA country of residence or workplace.
10. Children
Kaisei Weather is not directed at children and we do not knowingly process the data of children. Given how little data the App handles - and that it never asks for identifying information - it holds nothing that could identify a child. In line with Polish law, the App is intended for people aged 16 or over. If you believe a child has used the App in a way that concerns you, deleting the App removes all of its local data.
11. Security
The App relies on the security of iOS:
- Its data sits in the App’s private container, protected by iOS sandboxing and by your device’s hardware encryption when the device is locked with a passcode.
- All network traffic goes to Apple’s services over encrypted HTTPS connections, using Apple’s own frameworks.
- The App has no login, so there is no credential to steal, and no server, so there is no backend to breach.
- Purchases are verified cryptographically by StoreKit; an unverified transaction unlocks nothing.
Please help by keeping iOS up to date and protecting your device with a passcode, Face ID or Touch ID. No method of electronic storage or transmission is completely secure, and we cannot guarantee absolute security.
12. Changes to this policy
We may update this policy as the App changes. The current version always lives at https://www.cutthefluff.eu/portfolio/kaisei-weather-app/privacy, with its effective date at the top.
If a change materially affects how your data is handled, we will raise the Terms version so the App asks you to review and accept on the next launch, and we will note the change here. Minor edits - clarifications, corrected links, updated contact details - may be made by updating the date above.
13. Contact
CodeTech
Wrocław, Poland
Email: hello@cutthefluff.eu
Web: https://www.cutthefluff.eu
Our Terms of Service accompany this policy.
Appendix - App Store privacy label
For reference, this is how the App maps to Apple’s App Privacy questions in App Store Connect. It is informational and not part of the policy.
| Apple data category | Collected? | Detail |
|---|---|---|
| Location - precise | No | The precise fix stays on the device; only rounded coordinates are used. |
| Location - coarse | Yes | App Functionality. Not linked to identity. Not used for tracking. |
| Purchases | Yes | App Functionality. Handled by Apple; not linked to identity by us. |
| Identifiers | No | No user ID, no device ID, no advertising identifier. |
| Contact info | No | - |
| User content | No | Saved cities and custom themes never leave the device. |
| Search history | No | City search text is passed to Apple Maps and not retained. |
| Usage data | No | No analytics of any kind. |
| Diagnostics | No | Only Apple’s own opt-in crash reporting, which we do not collect. |
| Health, Financial, Contacts, Browsing, Sensitive info | No | - |
| Used for tracking | No | No ATT prompt; no data shared with data brokers or ad networks. |
| Third-party SDKs | None | Apple frameworks only. |
| Account deletion required | N/A | The App has no accounts, so Apple’s in-app account deletion requirement does not apply. |
Kaisei (快晴) - Japanese for a clear, cloudless sky.