Privacy Policy

Effective date: 2026-08-01 · Version 1

JobRig ("the app") is a set of calculation tools for tradespeople, published by the developer ("we", "us"). This policy explains what data the app and the jobrig.app website do and do not handle. It is written to satisfy the Google Play and Apple App Store privacy requirements and the transparency duties of the GDPR (and it voluntarily follows the CCPA's standards), in plain language, because you should be able to read it.

What the app stores on your device

The app saves your settings and display preferences (for example whether you last used basic or advanced mode, light or dark theme, and degrees or percent slope), two housekeeping values (the date the app was first installed and a settings-format version number), a set of one-time markers recording which first-run tips you have already been shown, and a few running counts of your own use, such as how many times the app has been opened and how many days you have used it. Those counts are only kept if usage analytics is switched on. All of this:

• is stored locally on your device (using the device's standard app storage),
• stays on your device, except as described under Usage analytics: on Android the app opts out of Google device backups entirely; on iOS a copy may exist inside your own device backup (iCloud or local), which only you control,
• contains no personal information, and
• is removed when you uninstall the app (on iOS, a copy may persist inside your own backup until that backup rotates).

Two more things live on your device: your analytics consent choice (a setting like any other), and the random per-install identifiers used by crash reporting and usage analytics. Those two are described in their own sections, and unlike everything above, an identifier travels with the report or event it marks.

The app does not store or transmit your calculation values. The numbers you type live in the app's working memory while you use it, and nothing carries them off the device.

If you reset the app's settings, your preferences return to their defaults. Your privacy choices, the install date, the settings-format version, the running counts described above and the one-time markers are kept, because they are not preferences you chose.

Crash reports

To fix problems, the app sends exactly one kind of diagnostic: a crash report, sent when the app stops unexpectedly, or when a part of it stops working in a way we need to know about. The app reports nothing else.

A report contains the error details and technical information about the device and the app at the moment it happened, such as your device model, your operating-system version, the app version and similar diagnostic details, plus a random identifier created when the app is installed, an industry-standard way to count how many devices a bug affects. That identifier is not linked to you and we cannot use it to identify you. Reports never contain your name, because the app never asks for it and has no accounts. They are not built from what is on your screen either: the numbers you type stay in the app's working memory, nothing in the app puts them into a report, and what a report carries instead is the technical description of the fault, written by the app's own code. Your IP address is used transiently to deliver the report over the internet (as with any internet request), and is not stored with the report.

Reports are processed for us by Sentry, our crash-reporting processor, with EU data residency: they are ingested and stored on servers in the European Union. They are used solely to diagnose and fix bugs, are never sold, are never shared with anyone for their own use except where the law compels us to disclose them, and expire automatically (see How long data is kept). Sentry's own privacy terms are at sentry.io/privacy.

You can turn crash reports off at any time, in Settings, under Privacy, with the row called Crash reports. With it off, the app builds no reporting connection at all, so nothing is collected and nothing is sent from that device. Your choice is recorded on your device only, and it survives resetting the app's settings.

Why we are allowed to do this (GDPR legal basis): legitimate interest (Article 6(1)(f)): keeping a working app working. The balance is straightforward: the data is minimal, not linked to your identity, limited to technical fault details, and auto-expiring, so our interest in fixing bugs does not override your rights or freedoms. And because you can switch it off, our interest never has the last word.

Separately from all of the above, the app stores themselves give us reports about how the app behaves, such as crash logs and performance summaries that Apple and Google collect from the devices they run on. That collection is theirs, not ours: we do not choose what it gathers, we cannot switch it off on your behalf, and it is governed by Apple's and Google's own privacy policies rather than this one. What reaches us is diagnostics about the app, never anything that identifies you.

Usage analytics (only if you say yes)

To improve the app, we ask whether we may collect usage information that is not linked to your identity: which tools you open, which features you tap, the settings you choose, how you move through the app, how long things take, and coarse metadata about the numbers you work with, such as how many digits a number has or which fraction denominator you picked, but never the measurements themselves. What "asking" means here:

• Freely given. It is a real question: nothing is pre-ticked, and declining never blocks or limits the app in any way.
• Withdrawable. You can turn analytics off at any time in Settings, under Privacy, with the row called Analytics; it takes effect immediately. Switching it off is itself recorded and sent, as the last usage event that installation sends unless you turn analytics back on, so that we can tell a withdrawal from a device that simply stopped being used; switching it back on is recorded the same way.
• No values. Events never contain your measurements: not the numbers you type, and not the answers the app works out for you. What they do contain is feature names, the options you have chosen, counts, coarse descriptions (for example a rough band for how steep a triangle is), how long things took, and a random per-install identifier of its own (the same kind crash reports use, but a separate one; the two datasets share no key; it exists so we can count devices, not identify people). Each event also carries the same technical device context as a crash report, plus your screen size, and your language, region and time zone settings, which are read from the phone's own settings and are not your location. Once per session it also carries a few coarse characteristics of the device itself, such as a rough memory band, roughly how old the model is, and how long the app took to start.
• Not linked to you, rather than anonymous. Because that per-install identifier stays the same until you uninstall, events from one installation can be grouped together, so calling them anonymous would overstate it. We hold nothing that names you, and nothing that lets us reach you.
• Screenshots, on iPhone and iPad only. If you take a screenshot while a result is on screen, we record that it happened, and nothing else. Never the image, never what was on it. Apple's system tells the app that a screenshot was taken; it does not hand the app the picture.
• No means no. If you decline, that choice is recorded on your device only, and nothing is ever sent from that installation: with no consent on record the app does not even start the analytics software, so there is nothing to send and nowhere to send it from.
• Looking back at the setup. If you do say yes, the first events include a short summary of the setup you just went through, such as which options you chose along the way. Nothing was sent while you were choosing; it is gathered on your device and only travels once you have said yes.
• Your IP address, like any internet request, is used to deliver each event. The location lookup that services usually apply to it is switched off, so the country we see comes from your phone's region setting rather than from where you are.

Analytics are processed for us by PostHog (EU cloud) as our processor; see posthog.com/privacy. Legal basis: consent (GDPR Article 6(1)(a)), and withdrawing it is as easy as giving it.

What the app does not do

The app does not:

• collect your name, email, phone number, or anything that identifies you as a person (the random per-install identifier used by crash reporting, described under Crash reports, is not tied to your name or account; if you write to us yourself, see When you email us);
• read or access your contacts, photos, location, microphone, or camera;
• track you for advertising: the app reads no advertising identifier on either platform, contains no advertising or ad-measurement code, and belongs to no ad network. Nothing it collects is ever used to profile you or follow you across apps or sites. Usage analytics, if you said yes to it, is a separate thing and is described under Usage analytics.

Permissions

The app requests these permissions:

• Vibrate: used only to provide haptic feedback (a small vibration) when you tap keys and buttons. It accesses no data.

The app also has standard system capabilities that never prompt you: internet access (used to deliver crash reports and, if you consented, usage events; see Crash reports and Usage analytics), a check of whether the device is currently online, and keeping the screen awake (used only while the keep-screen-awake setting is on; it touches no data). Two more are declared by the software libraries the app is built on rather than by us: one that Android requires for the app to receive its own internal messages, and one for reading how the app was installed from Google Play, which JobRig never asks for. None of them can reach what you type.

When you email us

If you write to support@jobrig.app, we receive your email address, whatever you choose to put in the message, and anything you attach, which for a support request is often a screenshot. That is the one place where information capable of identifying you reaches us, and it reaches us because you sent it, not because the app collected it. We use it to answer you and to fix what you reported, and for nothing else.

Why we are allowed to do this (GDPR legal basis): legitimate interest (Article 6(1)(f)): answering someone who has written to us for help.

Your rights

If you are in the EU/EEA or UK (GDPR): you have the rights of access, rectification, erasure, restriction, objection, and portability, and the right to withdraw any consent at any time (usage analytics is currently the only consent-based thing here; withdrawing is the Analytics row in Settings, under Privacy, and takes effect immediately). To exercise any of them, email us (see Contact). One honest caveat: because nothing we receive is linked to your identity, we usually cannot connect any report or event to you, and the GDPR (Article 11) says we do not have to collect extra data about you just to be able to. If we cannot act on a request for that reason, we will say so plainly. You can also complain to us directly, at support@jobrig.app, and we will look into it and tell you what we found. You always have the right to complain to a supervisory authority as well: your national data-protection authority in the EU/UK, or the Privacy Protection Authority in Israel.

Right to object, specifically: because crash reporting relies on our legitimate interest, GDPR Article 21 gives you the right to object to it. You do not have to write to us to do that: Settings, under Privacy, has a row called Crash reports, and switching it off stops the reporting on that device immediately and completely. Nothing else about the app changes when it is off. We have also kept that processing as light as possible either way: limited to technical fault details, auto-expiring, and not linked to your identity.

If you are in California (CCPA/CPRA): as with everyone, everywhere, we do not sell personal information and do not share it for cross-context behavioral advertising (as the CCPA defines those terms), and never have; California law simply asks us to say it in its own words. You have the rights to know, correct, and delete; because we cannot tell which installation belongs to which person, we usually cannot look anything up or delete it for one individual, and California law does not require us to collect more information in order to reidentify you. Ask and we will answer honestly. We will never discriminate against you for exercising any privacy right.

If you are in Israel (Privacy Protection Law): the developer is based in Israel, so Israeli law applies to us directly. You have the right to ask what information about you we hold, to ask us to correct it if it is wrong or out of date, and to ask us to delete it. The same honest limit applies as everywhere else: nothing we receive is linked to your identity, so in most cases we cannot find a particular person's data to show or delete. Ask us at support@jobrig.app and we will tell you plainly what we can and cannot do. You can also complain to the Privacy Protection Authority.

Everyone, everywhere: the same standard applies. JobRig is available in almost every country, and many of them have privacy laws of their own, among them Brazil's LGPD, Canada's PIPEDA, Switzerland's FADP and India's DPDP Act. We have not written a separate section for each, because we do not run the app to a different standard depending on where you opened it. If your local law gives you a right this policy does not name, write to us and we will honour it where it applies to you. Email us with any privacy question or request and we will do what we can, honestly.

How long data is kept

• Crash reports: set to expire on Sentry's servers after about 90 days (Sentry's current setting).
• Usage events (only if you consented): kept on PostHog's EU servers for about one year (PostHog's current setting). Your consent choice itself is stored on your device only.
• Emails you send us: kept while we deal with your question and for a short while afterwards, then deleted. They are never added to any mailing list.
• What stays on your device: your settings and display preferences, the date you installed the app, the markers recording which first-run tips you have seen, the running counts described at the top of this policy, and your privacy choices. All of it until you uninstall the app.

International transfers

Crash reports are ingested and stored in the European Union. Sentry is operated by a US company, so limited access from outside the EU can occur in operating the service; that processing is governed by a data-processing agreement incorporating the EU Standard Contractual Clauses (with the UK Addendum for UK users). Usage events (only if you consented) are likewise stored in the European Union, on PostHog's EU cloud; PostHog is likewise operated by a US company, under its own DPA with the EU Standard Contractual Clauses (with the UK Addendum for UK users). Cloudflare, which serves the jobrig.app website and logs visitor IP addresses in the ordinary course of doing so (see Our website), handles that data under its own data-processing addendum, which its standard terms incorporate wherever European personal data is involved. We are based in Israel, a country the European Commission currently recognizes as providing adequate data protection.

The Standard Contractual Clauses named above are the European Commission's published standard text, so anyone can read them in full. If you want to know which safeguards cover a particular transfer, email support@jobrig.app and we will tell you.

Children's privacy

JobRig is a work tool and is not directed at children under 13. If where you live sets a higher minimum age for agreeing to this kind of data collection on your own, our terms ask you to use JobRig with a parent's or guardian's consent. That applies in particular to Usage analytics, which is the one thing here that runs on your agreement: if you are under that age, please leave it switched off unless a parent or guardian says otherwise. Nothing else in the app depends on it, and declining changes nothing. Beyond the limited data described above (which is about how the app is used, not about who is using it), we do not knowingly collect personal data from anyone, including children: the app has no accounts, no messaging, and no data entry that leaves the device. If you are a parent or guardian and believe a child has somehow sent us personal data, contact us and we will delete whatever we can identify. As explained under Your rights, we usually cannot connect a report or an event to a particular person; where that is the case we will say so plainly rather than pretend otherwise. Uninstalling the app stops any further reports and removes the identifier from that device, and anything already sent expires on the schedule under How long data is kept.

Our website (jobrig.app)

The website is a static informational site: it uses no cookies, no analytics, no tracking, and no sign-in or data-entry forms, so the site itself collects nothing about you, by design. It is hosted by Cloudflare, whose infrastructure logs visitor IP addresses and standard browser error reports in the ordinary course of serving any website (for security and delivery), as every web host does. We use Cloudflare only to serve the site and do not use those logs to identify visitors. Cloudflare acts as our processor for the site; its privacy policy is at cloudflare.com/privacypolicy. Why this is allowed (GDPR legal basis): legitimate interest (Article 6(1)(f)): securely delivering the site, the same routine logging every web host performs. These logs are kept by Cloudflare under its own short retention schedule for security operations; we never receive, store, or use them ourselves.

Security

Today, there is no JobRig server, no user database, and no account system. The little that can travel (the crash reports and, only with your consent, the usage events) is encrypted in transit (HTTPS/TLS), minimized by design, and handled by reputable processors under data-processing agreements. No system is perfectly secure, but there is very little here to attack. If a security incident ever affected the limited data described here, we would act promptly to contain it, tell the relevant authorities where the law requires, and announce it the same way we announce a change to this policy (see Changes to this policy), because we hold nothing that would let us message you directly.

If you believe you have found a security problem in the app or on the website, please tell us at support@jobrig.app and we will look into it.

Who processes data for us

• Sentry receives and stores the crash reports (EU data residency).
• PostHog receives and stores the usage events, only if you consented (EU cloud hosting).
• Cloudflare hosts the jobrig.app website (a global network, with standard infrastructure logs).

All three are US companies acting as our processors under a data-processing agreement; the transfer safeguards are described under International transfers. Each is bound by a written agreement that requires it to handle the data only on our instructions, to give it the same protection this policy describes, and to use it for nothing else.

No one else, except where the law compels us to disclose something. If this list ever grows, this policy changes first (see Changes).

If JobRig is ever taken over by someone else, or moves into a company, the data described here would move with the app so it keeps working. That is a change of who runs JobRig, not a sale of your data: we do not sell it now and a handover is not a way around that. You would be told through this policy first, on the same terms as any other material change (see Changes).

Changes to this policy

If anything material changes (what data is handled, why, or by whom), this policy will be updated with a new effective date before the change ships, the store privacy declarations will be updated to match in the same release, and we will give notice via the app's store listing (and, where sensible, in the app) before it takes effect. Minor clarifications that do not change substance may be made at any time.

Who is responsible for your data

The data controller for JobRig and jobrig.app is Raz Sharabi, an individual developer based in Israel, who is also the person responsible for protecting personal data here and can be reached at support@jobrig.app.

Contact

Questions or requests about this policy: support@jobrig.app