Workr — Privacy Policy

Effective date: 29 July 2026  ·  Last updated: 29 July 2026  ·  Version: 2.5

1. Who we are (Data Controller)

"Workr" (the "App", "we", "our", "us") is an independently developed task-management application for iPhone, iPad, Mac and (where available) Android devices, published by:

• Developer: Asım Can Yağız (sole proprietor / indie developer)
• Jurisdiction: Republic of Türkiye
• Privacy contact: meycasim@icloud.com
• App identifiers: Apple bundle ID com.asimcanyagiz.Workr · iCloud container iCloud.com.asimcanyagiz.Workr

Because Workr does not transmit personal data to any server we operate, we typically act as a data processor of zero personal data. For website visits (see §8) and any direct correspondence you send to us, we act as the data controller.

2. Scope of this Policy

This Policy covers:

• The Workr mobile and desktop application on iOS, iPadOS, macOS, and (where distributed) Android and ChromeOS;
• Any pre-release beta versions distributed through Apple TestFlight or Google Play internal/closed/open testing tracks;
• The website hosted at GitHub Pages under the workr-pages repository (and any future product website).

This Policy does not cover Apple's iCloud, Google's account services, your mobile operating system, your network operator, or any other third party. Their practices are governed by their own privacy policies.

3. Data we collect — and what we don't

Workr is designed to collect as little as possible. Its core — task management and iCloud sync — is zero task-content collection. For advertising measurement, the app includes the AppsFlyer attribution service (install + subscription-event data; advertising identifier only with your App Tracking Transparency consent), and two optional features involve third parties (subscriptions via RevenueCat; cloud AI via OpenAI). All are called out below and in §7. The table is authoritative.

4. Data stored on your device

Workr stores the following on your device only:

• Task records (title, completion status, priority, due date, creation/modification timestamps);
• Project records (name, colour);
• User preferences (selected sidebar item, settings flags);
• Standard UserDefaults / NSUbiquitousKeyValueStore values set by SwiftData / SwiftUI / the system framework you're using.

This data is held in a SwiftData / SQLite-compatible local store inside the app's sandbox. You can erase all of it instantly by deleting the app.

5. Cloud sync (Apple iCloud / Google Drive)

5.1 Apple iCloud (iOS, iPadOS, macOS)

When you are signed into iCloud on your Apple device, Workr uses Apple's CloudKit framework to sync your tasks and projects across your Apple devices. The data is stored in your private CloudKit database inside your personal iCloud account. The CloudKit container identifier is iCloud.com.asimcanyagiz.Workr.

• We — the developers — cannot read the contents of your private CloudKit database. Apple's infrastructure enforces this.
• Apple may store this data on servers in the United States, the European Union, China (for accounts based in mainland China), or other regions, in accordance with Apple's own policies. See Apple's iCloud privacy page and the Apple Privacy Policy.
• If you sign out of iCloud, disable iCloud Drive for Workr (Settings → [your name] → iCloud → Apps Using iCloud), or disable iCloud entirely, sync stops and existing data remains only on the local device.
• If Apple's Advanced Data Protection is enabled on your account, CloudKit data — including Workr data — is end-to-end encrypted such that even Apple cannot read it.

5.2 Google Drive App Folder (Android — future)

If and when an Android version of Workr is distributed via Google Play, the same zero-collection principle will apply. The likely sync mechanism on Android is the Google Drive App Folder (a hidden per-app folder inside the user's own Drive that the app itself can read and write but other apps cannot). This means:

• Your task data, if synced, lives in your own Google Drive — not on our servers.
• The app would request the drive.appdata scope (least-privilege; no access to your other Drive files).
• Google may store this data on servers operated by Google LLC. See the Google Privacy Policy.
• You may disconnect the Google account at any time from within the app or from your Google Account permissions page.

Until the Android version ships publicly, Sections 5.2 and other Android-specific references describe future intent and impose no obligations on you.

6. Device permissions we request

Workr requests the following system prompts, each of which you may decline without losing core task-management functionality:

• App Tracking Transparency (iOS) — shown once, after onboarding, so AppsFlyer can measure which ad led to your install (see §7). Tap "Ask App Not to Track" to decline; the app works fully either way, and no advertising identifier is used unless you allow it.
• Notifications (optional) — requested if you use due-date reminders, so Workr can alert you when a task is due. Decline and your due dates still work silently.
• Camera (optional) — requested only if you attach a photo to a task.
• iCloud (CloudKit) — a declared capability (not a prompt) used solely for cross-device sync of your own task data, as described in §5.1.

If future versions add optional features that require permissions (for example, local notifications for due dates, or Calendar access for due-date import), the corresponding system prompt will appear at the moment you use that feature, and you may decline without losing core functionality. We will update this Policy and the platform store listings before such a feature ships.

7. Third-party services

Workr shows no ads inside the app and contains no social-login SDKs. Its everyday use integrates five third-party services: AppsFlyer (advertising attribution/measurement), Google Firebase Analytics (anonymous product analytics), RevenueCat (subscriptions), OpenAI via AIProxy (cloud AI), and Google Firebase Crashlytics (crash reporting). One further optional, off-by-default feature — "Connect your Claude" — shares task data with additional third parties (Anthropic, Google Firebase, WorkOS) only if you enable it. Each is for a single, user-facing purpose:

• AppsFlyer (AppsFlyer Ltd.) — our mobile measurement / attribution partner, active for all users. It tells us which ad or marketing campaign led you to install Workr and links your Workr Premium subscription events to that source, so we can measure return on ad spend and improve our advertising. AppsFlyer receives app-install/open and purchase events with coarse device, network, and locale signals, and an AppsFlyer-generated device install ID. It uses Apple's advertising identifier (IDFA) only if you tap "Allow" on the App Tracking Transparency prompt shown after onboarding; if you decline, measurement uses Apple's privacy-preserving SKAdNetwork instead and no IDFA is read. AppsFlyer receives no task content, name, or email. Because this measures across the ad that referred you, Apple classifies it as tracking (see §18). To attribute subscription revenue, your anonymous RevenueCat app-user ID is shared with the AppsFlyer event. See the AppsFlyer Services Privacy Policy. You can withdraw consent any time in iOS Settings → Privacy & Security → Tracking.
• RevenueCat (RevenueCat, Inc.) — manages the optional Workr Premium subscription (purchase, entitlement, and Restore Purchases). When you interact with Premium, RevenueCat receives your App Store transaction / receipt and an anonymous, app-generated user ID in order to determine whether your subscription is active. It does not receive your name, email address, or payment-card details — those remain with Apple. RevenueCat performs server-side receipt validation. Its practices are governed by the RevenueCat Privacy Policy.
• OpenAI (OpenAI, L.L.C.), accessed through the AIProxy gateway — powers Workr's optional cloud AI features (for example, cleaning up a task title or suggesting how to group tasks). These run only when you explicitly trigger a cloud-AI action and you are a Premium subscriber. At that moment, the specific text you chose to process — a task title or a selected list of titles — is sent through AIProxy to OpenAI, the suggestion is returned, and you decide whether to apply it. We do not send your full task database; only the item(s) you act on are transmitted. OpenAI does not use data submitted through its API to train its models. AIProxy acts as a privacy-preserving relay (it forwards the request without exposing our service key and applies rate limits) and is not used to profile you. See the OpenAI Privacy Policy and the AIProxy Privacy Policy.
• Firebase Crashlytics (Google LLC) — our crash-reporting service, active for all users. When the app crashes it sends an automatic, anonymous crash report (stack trace, device model, OS version, and a random Firebase installation identifier) so we can diagnose and fix the problem. It receives no task content, name, email, or advertising identifier, does not pull in Apple's advertising identifier (IDFA), and is used solely to improve app stability — never to track you or build a profile. See Firebase Privacy and the Google Privacy Policy.
• Firebase Analytics (Google LLC) — our product-analytics service, active for all users. We use the without-advertising-ID variant, so it does not link or pull in Apple's advertising identifier (IDFA) and triggers no App Tracking Transparency prompt. It records anonymous product-usage events — which screens you view, which features you tap, how far you get in onboarding, and a coarse install-week cohort — tied to a random Firebase installation ID, so we can understand what's used and improve the app. It receives no task content, name, or email, is not linked to your identity, and is not used to track you across other apps or websites (Apple classifies it as "Data Not Linked to You → Usage Data / Product Interaction," not tracking; see §18). It is on by default (anonymous, no advertising-tracking prompt), and you can turn it off any time in Settings → Privacy → Share Anonymous Analytics. See Firebase Privacy and the Google Privacy Policy.
• "Connect your Claude" — Anthropic, Google Firebase, and WorkOS (optional, off by default). Workr offers an optional feature that lets you connect your own Anthropic Claude so it can read and edit your Workr tasks on your behalf. It is off by default and turned on only after you tap through an explicit consent screen that names the recipients below. When you enable it:
  • What is shared: a private copy ("mirror") of your task data — titles, notes, projects (including names and colours), priority, due dates and repeat schedules, reminder timing, pinned/completion status, and any reusable task templates you create. Photos attached to tasks are never shared (only whether a task has an attachment).
  • Anthropic, PBC — the recipient. Your connected Claude reads and edits your tasks through a secured interface (an MCP server we operate on Google Cloud). Anthropic does not use data submitted through its API to train its models by default. See the Anthropic Privacy Policy and Commercial Terms.
  • Google Firebase (Google LLC) — the processor that stores your private task mirror (Cloud Firestore) and runs the connection backend on Google Cloud. See Firebase Privacy and the Google Privacy Policy.
  • WorkOS, Inc. — the identity processor that handles the sign-in (via Sign in with Apple) linking your app to your Claude. See the WorkOS Privacy Policy.
  • Reversible: you can Disconnect at any time (stops sharing and deletes the cloud copy) or Delete Connected Account (removes the mirror and your sign-in identity entirely). Your tasks on your device and in iCloud are never affected.

On-device Apple Intelligence features (on supported devices) run entirely on your device and send nothing to us or any third party. The remaining external services are the platform services provided by Apple (and, on Android when applicable, Google) plus your operating system itself.

For website visits, see §8.

8. This website (workr-pages)

The pages at the GitHub Pages site associated with the workr-pages repository are static HTML. We do not set any first-party cookies, run any analytics, or load any third-party scripts.

However, when you visit the site, GitHub Inc. (as the hosting provider) automatically processes standard server log information (IP address, user-agent, requested URL, timestamp) for security, abuse prevention, and operational purposes. GitHub's practices are governed by the GitHub General Privacy Statement and the GitHub Privacy Statement. We do not receive these logs.

9. Children's privacy (COPPA / GDPR Art. 8)

Workr is rated 4+ on the App Store and is suitable for all ages, including children. Because Workr collects no personal data from any user, no special children's data is collected either. We do not knowingly collect personal data from children under the age of 13 (United States) / 16 (European Economic Area, depending on the Member State) / the equivalent local age threshold. If you are a parent or guardian and believe your child has somehow provided us with personal data (for example by emailing us), please contact meycasim@icloud.com and we will delete it immediately.

10. International data transfers

Because we collect no personal data ourselves, no international transfer is performed by us. The cloud sync providers (Apple, optionally Google) may transfer your own data internationally in line with their own policies. Apple relies on the EU Standard Contractual Clauses for EU-to-US transfers; Google relies on the EU-US Data Privacy Framework and SCCs. We are not a party to those transfers.

11. Security

• Local storage uses your operating system's standard file-system protections (App Sandbox / Data Protection class) and the encryption that your device's lock screen provides.
• Sync uses TLS in transit and the platform-provided encryption at rest (CloudKit / Google Drive).
• No service accounts or developer credentials grant us access to your private cloud database.
• If you lose your device, you should remotely lock or erase it via Find My / Find Hub — this is the most effective protection for your data.

No system is perfectly secure. By using Workr, you acknowledge that no method of electronic storage or transmission is 100% secure, and we cannot guarantee absolute security.

12. Data retention

• On your device: until you delete the task / project / app.
• In your private iCloud / Drive: until you delete the task / project, delete the app from all your devices, or terminate the cloud account. Apple and Google may retain backups according to their own retention windows.
• On our servers: not applicable — we operate none.
• Email correspondence: if you email us, we retain that thread for as long as needed to handle your request and for up to 24 months thereafter for support continuity, unless you ask us to delete it sooner.

13. Your rights

You have the following rights with respect to any personal data you provide to us by emailing us, or that may exist about you in our records (which is typically nothing more than the email thread itself):

• Access — request a copy of any personal data we hold about you.
• Rectification — ask us to correct inaccurate data.
• Erasure ("right to be forgotten") — ask us to delete data.
• Restriction — ask us to stop processing your data in certain ways.
• Portability — receive your data in a structured, machine-readable format.
• Objection — object to processing based on legitimate interests.
• Withdraw consent — where processing is based on consent.
• Lodge a complaint — with your local data protection authority (see §14 / §16).
• Non-discrimination — we will not deny service for exercising any right.

To exercise any right, email meycasim@icloud.com from the address you originally used. We respond within 30 days, extendable by a further 60 days for complex requests as permitted by GDPR Art. 12(3).

14. European Economic Area & United Kingdom (GDPR / UK GDPR)

If you are in the EEA, the United Kingdom, or Switzerland, the following applies.

• Legal basis for processing: as we collect no personal data through the app, no Art. 6 legal basis is needed for app use. Where we do process data (email correspondence, optional crash diagnostics shared by Apple/Google), our legal basis is your consent (Art. 6(1)(a)) and / or our legitimate interest in providing customer support and improving stability (Art. 6(1)(f)).
• Automated decision-making: none. No profiling. No Art. 22 decisions.
• Supervisory authority: you may lodge a complaint with the data protection authority of your habitual residence, place of work, or place of the alleged infringement. A directory is available at edpb.europa.eu.
• EU representative: as a non-EU-established controller that does not regularly process data of EU subjects on a large scale, we are not required to appoint an EU representative under GDPR Art. 27. We will appoint one if our processing becomes regular and material.

15. California residents (CCPA / CPRA)

If you are a California resident, the California Consumer Privacy Act (as amended by CPRA) gives you specific rights. In the 12 months preceding the effective date of this Policy:

• We have not collected personal information through the App, beyond what is described in §3.
• We have not sold any personal information.
• We have not shared personal information for cross-context behavioural advertising.
• We have not used or disclosed sensitive personal information for inferring characteristics about a consumer.

You have the right to know, delete, correct, and limit the use of any personal information, and the right to non-discrimination for exercising these rights. Authorised agents may submit requests on your behalf with appropriate proof. Contact meycasim@icloud.com.

16. Türkiye residents (KVKK)

6698 sayılı Kişisel Verilerin Korunması Kanunu ("KVKK") kapsamında veri sorumlusu sıfatıyla yukarıda belirtilen geliştirici görev yapmaktadır. Workr uygulaması, KVKK madde 3 anlamında bir kişisel veri işleme faaliyeti yürütmemektedir; yalnızca cihazınızda yerel olarak veri saklanmakta ve seçtiğiniz takdirde Apple iCloud veya Google Drive üzerinden senkronize edilmektedir.

KVKK madde 11 uyarınca, kişisel verilerinizin işlenip işlenmediğini öğrenme, işlenmişse buna ilişkin bilgi talep etme, amacına uygun kullanılıp kullanılmadığını öğrenme, yurt içi / yurt dışı aktarımlardan haberdar olma, düzeltilmesini isteme, silinmesini / yok edilmesini isteme, aktarıldığı üçüncü kişilere bildirilmesini isteme, otomatik sistemlerle analiz edilmesine itiraz etme ve kanuna aykırı işleme nedeniyle uğradığınız zararın giderilmesini talep etme haklarına sahipsiniz. Başvurularınızı meycasim@icloud.com adresine iletebilirsiniz. KVK Kuruluna şikâyet hakkınız saklıdır.

17. Other jurisdictions (LGPD, PIPEDA, APP, PIPL, etc.)

If you reside in Brazil (LGPD), Canada (PIPEDA), Australia (Australian Privacy Principles), India (DPDP Act), Japan (APPI), South Korea (PIPA), South Africa (POPIA), or mainland China (PIPL), this Policy is intended to satisfy the substantive transparency and data-subject-rights requirements of your local regime. Where local law affords you a stronger right than this Policy describes, that local right prevails. Contact us to exercise it.

18. Apple App Store & Google Play disclosures

18.1 Apple App Store — "Privacy Nutrition Labels"

Workr's App Store privacy label reflects the data the app and its measurement/optional features involve, and nothing more:

• Data Used to Track You — for advertising measurement via AppsFlyer (see §7): your Identifiers (advertising identifier / IDFA, used only with your ATT consent, plus an AppsFlyer device install ID), Purchase History (subscription events), and Usage Data (app install/opens). This is the "Data Used to Track You" category. Task content is never included.
• Purchases — subscription status, linked to an anonymous app-user ID, processed by RevenueCat for App Functionality (unlocking cloud AI), and subscription events linked to attribution by AppsFlyer (tracking, above).
• User Content — for users who use cloud AI only: the task text you choose to process is sent to OpenAI to deliver the feature you requested (App Functionality). Not linked to your identity and not used for tracking.
• "Connect your Claude" (only if you enable it) — User Content (task titles, notes, projects), Email Address, and User ID are linked to you and used for App Functionality (letting your own Anthropic Claude read and edit your tasks). Not used for tracking; removed when you Disconnect or Delete. See §7.
• Diagnostics — Crash Data — for all users: anonymous crash reports (stack trace, device model, OS version, and a random installation identifier) collected by Firebase Crashlytics for App Functionality (fixing crashes). Not linked to your identity and not used for tracking. See §7.
• Usage Data — Product Interaction — for all users: anonymous product-usage events (screen views, feature taps, onboarding progress, and a coarse install-week cohort) collected by Firebase Analytics (without-advertising-ID variant) for Analytics (understanding what's used to improve the app). Not linked to your identity and not used for tracking — this is the "Data Not Linked to You" category, not the tracking section. No advertising identifier is used. See §7.

For users who do not enable "Connect your Claude," core task data remains "Data Not Collected" — it never leaves your own iCloud. For all users, the app collects anonymous Crash Data (above) and, for advertising measurement, the attribution data in the "Data Used to Track You" bullet — which uses your advertising identifier only if you grant Apple's tracking permission. If any of this changes, we will update the label and this Policy before the affected build is reviewed.

18.2 Google Play — "Data Safety" section

When Workr is distributed on Google Play, the Data Safety section will declare: no data collected, no data shared with third parties, data encrypted in transit, and (subject to platform support) users can request data deletion by deleting the app or contacting us. We will update the disclosure if any of these change.

19. Do-Not-Track & Global Privacy Control

The only cross-app tracking Workr performs is AppsFlyer advertising attribution (§7), and it is gated entirely by Apple's App Tracking Transparency prompt: decline it (or withdraw consent in iOS Settings → Privacy & Security → Tracking) and no advertising identifier is used. Browser DNT / GPC signals do not apply to native app tracking, so ATT is the control that governs it. This website (§8) deploys no tracking, so DNT / GPC signals received here produce no behavioural change — there is nothing to suppress.

20. Data breach notification

In the unlikely event of a personal data breach affecting any data we hold about you (typically: an unauthorised disclosure of an email thread you sent us), we will notify the relevant supervisory authority within 72 hours where required by GDPR Art. 33, and we will notify you without undue delay where required by Art. 34, by the equivalent CCPA / CPRA provisions, by KVKK madde 12/5, or by any other applicable law.

21. Changes to this Policy

We may update this Policy from time to time. The "Last updated" and "Version" fields above will always reflect the current revision. Material changes (any change that broadens our data collection, narrows your rights, or changes the legal basis for processing) will be highlighted at the top of this document for at least 30 days and noted in the next App Store / Google Play release notes. Continued use of Workr after a material change becomes effective constitutes acceptance of the revised Policy.

A change log of all previous versions is maintained in the git history of the workr-pages public repository.

22. Contact

Privacy questions, data subject requests, supervisory-authority enquiries, or general feedback:

• Email: meycasim@icloud.com
• Subject line guidance: please include "Privacy", "GDPR", "CCPA", "KVKK", or your jurisdiction to help us route your request quickly.