Closed Beta Privacy Notice
Last updated: 18 August 2026
This notice explains how information is handled for GigJar's closed Android beta cohort study. It supplements the main GigJar Privacy Policy.
1. Controller and contact
The data controller for this study is Keith McKinney, sole trader, trading as GigJar, in the United Kingdom. For privacy questions or to exercise a data-protection right, email privacy@gigjar.co.uk.
2. What the study collects
| Information | Purpose |
|---|---|
| Intake answers, including your name, recruitment source, work pattern, gig platforms, record-keeping approach, accountant/tax experience, broad subscription/spending history and MTD awareness. | Screen eligibility, build the planned cohort mix, establish a baseline and interpret later behaviour. |
| Written weekly and follow-up survey answers, dropout feedback and, if you choose a short call, notes needed to record what you tell us. | Understand use, friction, trust, persistence and what participants ask GigJar to do. |
| The measurement files you deliberately send at the requested study points. | Measure whether records were created during the cohort and when, without collecting the financial content of those records. |
| Contact or delivery information needed to communicate with you and provide the £10 digital voucher if you earn it under the study terms. | Administer participation and provide the promised voucher. |
3. What is in the GigJar measurement file
The study measurement export is intentionally narrow. It contains a cohort-start header and, for eligible cohort-period records, only:
- record type (shift, trip or expense);
- event date; and
- record-created UTC time.
It does not contain earnings, mileage amounts, routes, notes, platform names, hours or expense amounts. If GigJar repairs an older record identifier during the cohort, that record's type and original event date can appear, but no amount or free-text content is added.
The normal app remains local-first. In the current closed-beta build, crash reporting and user accounts are not enabled. Your ordinary GigJar records remain on your device and GigJar does not transmit them to our servers. The study files described above leave your device only when you deliberately share them.
4. Lawful bases
For selecting, running and evaluating the cohort, we rely on legitimate interests: GigJar's interest in testing whether the product is useful, understanding how it is used and improving it using a deliberately minimised study design. We limit the information collected, keep ordinary app records on-device, restrict access to Keith, use a narrow measurement export and set a deletion period to reduce the effect on participants.
Where contact or delivery information is necessary to provide a voucher you have earned under the stated study terms, we rely on contract. Where processing is required to meet a legal obligation, such as responding to applicable data-protection obligations, we rely on the relevant legal obligation.
Your agreement to take part, and your choice to send a measurement file, are voluntary participation choices. They are not being presented as the UK GDPR lawful basis for the study processing above.
5. Who handles the information
- Keith McKinney / GigJar — Keith is the only person who reviews individual study responses.
- Tally — form processor for intake and follow-up surveys. Tally states that form data is encrypted in transit and at rest and stored in Europe, and that the form creator remains controller of respondent data.
- Microsoft 365 — restricted working storage for the response sheet and participant files.
- Digital voucher provider — only the contact/delivery information needed to issue the voucher, when applicable.
We do not sell study information or disclose it to another organisation for that organisation's own marketing or unrelated purposes. Tally and Microsoft may use subprocessors. Where a provider's processing involves a restricted international transfer, we rely on the applicable contractual or other safeguards provided for that service. You can ask privacy@gigjar.co.uk for more information about the safeguards relevant to your information.
6. Retention
Raw named survey responses, identifiable written study responses and raw measurement exports are kept in the live study stores until 90 days after the final GigJar cohort Decision Report, then deleted. Identifiable optional-call notes follow the same study-retention period unless they have already been anonymised.
We may keep anonymised or aggregated findings that no longer identify you. Records needed only to evidence or account for a voucher payment may be retained for the applicable legal/accounting period, but the study answers themselves are not required for that accounting record.
Tally states that when form data is deleted from an account it is permanently deleted from its backups within up to 90 days, unless the Trash is emptied earlier. Provider backup and security logs may therefore age out after deletion from the live study store.
7. Taking part, leaving and your rights
Taking part is voluntary. You may leave the cohort at any time by contacting GigJar. Leaving stops future study requests; it does not remove information that has already been irreversibly anonymised.
Depending on the circumstances, your UK data-protection rights can include access, correction, erasure, restriction and objection. You have the right to object to processing based on legitimate interests. Where the law gives you a right to data portability or another right, we will also honour it. Email privacy@gigjar.co.uk to make a request.
You can also complain to the Information Commissioner's Office (ICO) if you are unhappy with how your personal information is handled.
8. Data minimisation
Please do not put health information, political opinions, religious beliefs, biometric/genetic information, sexual-life/orientation information, criminal-offence information or other unnecessary sensitive personal information into free-text study answers. The study does not need those categories of information.
9. Changes
If the cohort design changes in a way that materially changes the information collected, the purpose, the recipients or the app's off-device processing, this notice and the main privacy policy will be reviewed before the changed processing begins.