Privacy Policy

Effective date: November 9, 2026
Who we are: Clockpay is made by Abdirahman Hassan (an individual developer; this is the App Store seller name) ("we", "us").
Contact: vetfile.support@gmail.com · https://clockpay.pages.dev/support · Minnesota, United States

The short version

• Clockpay has no account and no servers. We never ask for your name, email, or phone number to use the app.
• Everything you add, including jobs, shifts, rates, overtime rules, breaks, notes, and your optional name for PDF timesheets, is stored only on your device. We can't see it, and we don't have a copy.
• Purchases go through Apple. Our subscription provider, RevenueCat, receives purchase information so Pro works. It doesn't receive your shift or job data.
• Clockpay may send anonymous usage analytics (via PostHog) and crash diagnostics (via Sentry). These do not include your name, email, job names, pay rates, shift times, or notes. No ads. No tracking across other companies' apps or websites.
• We don't sell or share personal information. No location.

1. What stays on your device (we don't collect it)

When you use Clockpay, the information you enter is saved in a database inside the app on your iPhone. This includes:

• Jobs: name, hourly rate, currency, color, pay period, overtime rules, and archived status.
• Shifts: clock-in and clock-out times, breaks (paid or unpaid), notes, and optional rate overrides.
• Settings: optional worker name for PDF timesheets, first day of the week, 12/24-hour time, reminder preferences, and similar preferences.

This data isn't sent to us or to anyone else, except when you choose to send it (see section 3). Under Apple's App Privacy definitions, data that stays on your device and isn't sent off it is not "collected" (Apple: App privacy details).

iCloud Backup. Because the data is in the app's storage on your device, it's included in your device's iCloud Backup if you've turned that on in iOS Settings (Apple: Back up iPhone with iCloud). Apple handles that backup under Apple's Privacy Policy. We can't access it. Clockpay doesn't sync to iCloud or between devices.

2. Permissions Clockpay asks for

All of these are optional, and you can change them anytime in iOS Settings.

• Notifications: to remind you if you're still clocked in after a set number of hours. Reminders are local notifications scheduled on your device. They don't go through a server, and they work offline.

Clockpay doesn't use your location, contacts, camera, microphone, photo library, or health data from Apple Health. There is no GPS or geofence clock-in.

3. When you choose to share or export

Clockpay lets you take your data out at any time, and only when you tap to do so:

• Spreadsheet (CSV) (free), PDF timesheet (Pro), and backup file (free).

These files are created on your device and handed to the iOS share sheet. You choose where they go, for example AirDrop, Messages, Mail, Files, or a printer. After that, the app or person you send them to handles them under their own policies. We never receive a copy. When you restore from a backup file, it's read on your device only.

4. What is sent off your device

4a. Purchases (Apple and RevenueCat)

If you buy or restore Clockpay Pro, Apple processes the payment. We never see your card or payment details. Apple's handling is covered by Apple's Privacy Policy.

We use RevenueCat, Inc. to check your purchase and unlock Pro. To do that, the RevenueCat software in the app sends RevenueCat your purchase history with an anonymous ID that the app creates. It isn't linked to your name or email. RevenueCat also receives basic technical details such as country/locale, currency, app version, and device type (see RevenueCat's documentation for the current field list). RevenueCat's own documentation says it doesn't collect payment information, health data, contacts, or precise location (RevenueCat: Apple App Privacy). We use this data to:

• provide Pro features and restore purchases (app functionality), and
• see totals of trials, purchases, and renewals (analytics).

In Apple's App Privacy terms, we declare this as Purchase History, used for app functionality and analytics, not linked to you, and not used for tracking.

See RevenueCat's Privacy Policy. RevenueCat keeps purchase records as described in RevenueCat's privacy policy and data processing terms.

4b. Analytics (PostHog)

We use PostHog (PostHog Inc.) to understand how Clockpay is used at a high level — for example whether onboarding finished, whether a first shift was logged, when the paywall appears, and whether a trial or purchase completed.

What we send:

• An anonymous device/install ID created by the PostHog SDK (not your name or email; we never call identify with personal data).
• Event names such as onboarding_completed, first_shift_logged, paywall_shown, trial_started, and purchase_completed, plus limited properties (for example paywall source, product id, plan type, price, and currency for purchases).
• A fixed app tag (app = clockpay) so our shared analytics project can separate Clockpay from other apps.

What we do not send:

• Names, emails, phone numbers.
• Job names, hourly rates, shift times, notes, or worker name for PDFs.
• Ads identifiers for cross-app tracking. We do not use this for advertising.

IP addresses are anonymized in our PostHog project settings. Session replay is off. Analytics is off entirely if the PostHog key is not configured in a build.

See PostHog's Privacy Policy.

4c. Crash reports (Sentry)

We use Sentry (Functional Software, Inc. d/b/a Sentry) to learn when the app crashes so we can fix bugs. Crash reports may include stack traces, device/OS/app version, and similar technical diagnostics. We configure Sentry with no default PII, no user identity, and no session replay. We strip shift and pay-related fields from breadcrumbs and extras when present.

Crash reporting is off if the Sentry DSN is not configured, and it stays off in developer builds unless explicitly forced for testing. If you've chosen to share analytics with app developers in iOS Settings, Apple may also share anonymous crash reports with us.

See Sentry's Privacy Policy.

4d. When you email us

If you contact support, we receive your email address and whatever you write (Clockpay's Contact support button pre-fills the app version, iOS version, iPhone model, and whether you have Pro; it includes no job or shift data). We use it only to answer you and delete it 12 months after the conversation ends. Our support inbox is a Gmail account, so Google stores and processes these emails under the Google Privacy Policy.

4e. Our App Store privacy label, in full

This is what we declare on Clockpay's App Store page, in Apple's terms:

• Purchases > Purchase History (RevenueCat): used for app functionality and analytics. Not linked to you. Not used for tracking.
• Usage Data > Product Interaction (PostHog): used for analytics. Not linked to you. Not used for tracking.
• Identifiers > Device ID (PostHog's anonymous SDK ID; not the advertising identifier / IDFA): used for analytics. Not linked to you. Not used for tracking.
• Diagnostics > Crash Data (Sentry): used for app functionality. Not linked to you. Not used for tracking.
• Not collected: your jobs, shifts, rates, overtime rules, notes, reminders, and worker name. They stay on your device.

5. What we don't do

• No accounts, sign-in, or social login.
• No advertising and no ad SDKs. No tracking as Apple defines it, so Clockpay doesn't show the "Allow tracking" prompt.
• We don't sell or "share" (for cross-context behavioral advertising) personal information.
• No location, GPS, or geofencing.
• No employer, payroll, bank, or tax-authority connections.

6. Keeping and deleting your data

• Data on your device: you control it. Delete a shift or job inside the app, or delete the app to remove everything. Copies may remain in your iCloud or computer device backups and in any files you exported or sent, until you delete those.
• Important: we have no copy, so we can't recover your data if you delete the app without a backup. Use Settings > YOUR DATA > Back up to a file or your device's iCloud Backup.
• Purchase data at RevenueCat: this is tied to an anonymous ID, not your name. To ask us to delete it, email vetfile.support@gmail.com. Because the ID is anonymous, include your Apple order ID from your App Store receipt (or other purchase details) so we can find the record. We'll delete what we can in RevenueCat. Apple keeps its own purchase records. Ask Apple about those.

7. Children

Clockpay is a general-audience app for tracking work hours. It isn't directed to children under 13 and isn't in the App Store Kids category. We don't knowingly collect personal information from anyone, including children. The jobs and shifts a child might enter stay on the device and aren't sent to us. If you believe a child has sent us personal information (for example by email), contact us and we'll delete it.

8. Your rights

Depending on where you live (for example the EU/UK, or US states such as California), you may have rights to access, correct, delete, or port personal information, or to object to its use. Because we don't hold your records, most of these are handled directly in the app: edit, delete, or export anytime. For the limited purchase data described in section 4, email vetfile.support@gmail.com and we'll respond within 30 days. We process purchase data to provide the app (our contract with you via Apple). The data controller is Abdirahman Hassan, Minnesota, United States. RevenueCat is based in the United States; data may be processed outside your country. You may have the right to complain to a data protection regulator where you live.

9. Security

Your records are protected by your device's security (passcode, Face ID/Touch ID, and iOS data protection). Data sent to RevenueCat, PostHog, and Sentry is sent over encrypted HTTPS connections. No method is perfect, so keep your device locked and backed up.

10. Changes

If we change how Clockpay handles data, for example by adding analytics, sync, or a new service, we'll update this policy and the "Effective date" above before the change ships, and update the App Store privacy label. For material changes, we'll also note them in the app when practical.

11. Contact

Abdirahman Hassan · vetfile.support@gmail.com · https://clockpay.pages.dev/support · Terms of Use · Minnesota, United States