Skip to content

Privacy Policy

This policy covers the Overtally website and the Overtally mobile app, both made by Ihor Bezrukavnyk, an independent developer. The short version: there are no accounts, we run no analytics, the website loads Google's advertising tag only if you say yes to it, and what you type stays on your device. In the app, the one thing that ever leaves your phone is the receipt for a Pro subscription, described below. The long version follows, because you should not have to take the short version on faith.

Last updated:

The calculator runs on your device

The rules tables and the pay engine are part of the page your browser downloads. When you enter an hourly rate, hours, or pick a state or province, the arithmetic runs on your own device. None of it — not the rate, not the hours, not the place — is transmitted to us, and there is no server-side calculator for it to reach.

To save you from losing your work, the calculator keeps its current sheet in your browser's local storage, on your device. We cannot read it. The Reset button deletes it. Clearing your browser data also deletes it.

“Copy link” packs your current sheet into the link itself so you can share or reopen it. Anyone you send that link to can see the numbers in it, and it may appear in your own browser history — but it is never sent to us or stored by us.

What the website does not do

To be explicit about what is absent:

  • No accounts or sign-ups. The site has a box where you can ask to be emailed when the iPhone version ships; by default it opens your own mail app, and your address reaches us only if you send that email. If we ever switch it to a form that submits from the page, this policy will say where the address goes and how long we keep it.
  • No analytics scripts, session recorders, or heat maps.
  • No social widgets or third-party embeds. The one outside script the site can load is Google's advertising tag, and only if you allow it — see the next section.
  • No tracking cookies unless you allow ad cookies. The site's own cookie is a single functional one that remembers your language choice if you switch languages. It contains the word “en” or “es”, nothing else, and identifies nobody. Your answer to the ad-cookie question is kept in your browser's local storage, not in a cookie.
  • Typefaces and all other assets are served from this domain, so loading a page does not announce your visit to a font or script CDN. The exception is Google's tag, which loads from Google's servers only after you allow ad cookies.

Advertising cookies, only if you allow them

Overtally advertises its app with Google Ads. To show those ads to people who have already visited, the site can load Google's advertising tag. The first time you visit, a small prompt asks whether Google may set advertising cookies. Until you press Allow, no request goes to Google and no Google cookie is set. If you say no, your browser remembers it and the prompt does not come back.

If you allow it, Google receives what any page load carries — the address of the page, your IP address, browser and device details, and the time — and sets its own advertising cookies, such as _gcl_au, in your browser; it may also keep ad-click details in your browser's local storage. Google uses them to add your browser to a list of site visitors that Overtally ads can be shown to, and to measure how those ads perform. Google handles this data under its own privacy policy (policies.google.com/privacy), and you can manage how Google personalises ads at myadcenter.google.com. We see only list sizes and ad totals, never who is on a list. Google may process and store this data outside Québec and Canada, including in the United States. Nothing you type into the calculator is ever included.

You can change your answer at any time with the “Ad cookies” link at the bottom of every page. Withdrawing deletes the Google cookies and local-storage entries kept for this site and reloads the page, so none of Google's code keeps running; anything Google already received stays under Google's own retention rules.

We do not sell your personal information. Some US state privacy laws treat advertising cookies like these as “sharing” for cross-context behavioural advertising. Because the tag runs only after you opt in, declining — or withdrawing later — is how you opt out.

Hosting and server logs

Like practically every website, the servers that deliver these pages may briefly process technical data — your IP address, browser type, and the page requested — to route the response, defend against abuse, and keep the service running. This is standard infrastructure operated by our hosting provider, it is not used by us to identify or profile you, and we run no tooling on top of it.

The mobile app

The app is built on the same principle: your record belongs to you and lives on your phone. The Overtally Pro subscription is the one thing that involves anyone else, and this section says exactly who.

  • Shifts, rates, breaks, pay settings, contract rules, rotations and everything you log are stored only on your device. There is no account and no sync server, and we cannot see, restore, or delete your data. Deleting the app removes it from the phone; if Android's device backup is turned on, Google may keep a copy in your own Google account and put it back when you reinstall — that copy is between you and Google, and we never have it.
  • Exports and the backup file are created on your phone and handed to the share sheet. Where they go from there — a drive, a message, a printer — is your choice, and we do not receive them.
  • Reminders and notifications are generated locally on your device. Nothing about your schedule is sent anywhere to make them work.
  • Overtally Pro is sold as a subscription or a one-time purchase through Google Play. Google takes the payment under its own terms and privacy policy; we never see your card number, billing address or Google account. To confirm what you bought, the app talks to RevenueCat, a subscription service acting on our behalf. Every time the app starts, whether or not you have bought Pro, it sends RevenueCat a random identifier the app made up on first launch, the purchase token Google Play issues once you buy, and what any internet connection carries: your device model, operating system, app version and IP address. RevenueCat keeps the purchase record so the app can tell a paying user from a free one, restore a purchase on a new phone, and process a refund, and it shows us totals — how many purchases are active, renewed or refunded — never who. It does not receive your name, email, shifts or pay. The connection is encrypted in transit. When the iPhone version ships, Apple's App Store will take the same role as Google Play.
  • To decide when to show a thank-you note, the app keeps a short record on your phone: the day it first ran, which of the last 14 days you opened it, when it showed you the note and whether you asked it to stop, and the last day you saw the Pro screen or a pay stub that came up short; none of it is sent to us or anyone else.
  • The app contains no advertising. It ships with an analytics library, PostHog, that is switched off: the released build has no key for it, so it initialises nothing and sends nothing. If we ever switch it on, this policy will change first and will say what is counted.

Email

If you write to support@overtally.com, we receive your email address and whatever you include. We use it only to reply, we do not add you to any list, and we will delete the correspondence on request.

Children

Overtally is a work tool. It is not directed at children under 13 (or the higher age your jurisdiction sets). We collect no personal data beyond what the subscription mechanics and, if you allow them, the advertising cookies above describe, and we do not knowingly collect anything from children.

Your rights

Privacy laws such as the GDPR and CCPA give you rights over personal data an operator holds about you. Our design answers most of them by default: we hold no account, no profile, and no copy of your entries, so access, portability, and deletion are satisfied on your own device — with Reset on the site, or by deleting the app. If you believe we hold anything about you (for example, an email you sent), write to us and we will confirm, hand it over, or delete it.

In the app, the one record that exists off your phone is the anonymous subscription record at RevenueCat described above. Write to us and we will delete it; because it carries no name, we may ask for the order number from your Google Play receipt to find it. Deleting it does not cancel the subscription — cancelling is done in Google Play.

If you allowed ad cookies on the website, the visitor list lives with Google, not with us, and we cannot pick you out of it. Withdraw with the “Ad cookies” link and use Google's own tools to see or delete what Google holds.

Changes to this policy

If the way Overtally handles data ever changes — for example, if an optional sync service is added — this policy will be updated first, the date at the top of this page will change, and the new behaviour will not apply retroactively to data that never left your device.

Contact

support@overtally.com — privacy questions, deletion requests, or anything unclear above.