UC Planner Founding Tester programme
Founding Tester privacy notice.
This notice explains the information used for the application and testing programme, why it is used and the choices available to participants.
Last updated: 9 October 2026
A short version first
The programme needs limited application details and useful feedback—not claim evidence.
We need a small amount of information to invite and manage people taking part in the UC Planner Founding Tester programme. We also use feedback that testers choose to provide to find and fix problems before the app launches.
UC Planner asks for the information needed to make its own estimate and planning calculation. It does not ask you to upload, photograph, paste in or store your official UC statement, and it does not create a copy or record of that statement.
If we ask you to compare an estimate, you read your own next UC statement separately when it arrives and compare it with the app’s estimate yourself. If you used historical information to model a past period, you may instead compare the estimate with the matching historical statement. Both are optional, and the app does not receive or see the official statement as part of the comparison.
Sending feedback through TestFlight or email is an optional, deliberate action. If you choose to report an apparent problem, start with a general description. Statements, payslips, claim references, National Insurance numbers, bank details, addresses, employer or workplace names, children’s details, diagnoses, medical information and other documents are not required and should not be sent. Useful feedback and the tester benefit do not depend on sending evidence.
If you choose to send free text or a screenshot, personal details can be included accidentally despite this guidance. We aim to remove direct identifiers before using feedback with development tools, including AI-assisted tools, but cannot guarantee that every personal detail will be spotted.
This notice does not reduce your legal rights.
1 · Who we are
The programme is operated by Barry Collins trading as Organised & Co for UC Planner.
Programme and privacy contact: app-feedback@organisedandco.comFull legal and business information: Organised & Co legal and privacy
UC Planner information and support: UC Planner app information
2 · Information we collect
Different stages involve different information.
When you apply
We collect your name or preferred name, email address, whether you can use a compatible iPhone and TestFlight, and your acknowledgement of the programme and this notice. This first testing wave is for iPhone only. iPad testing may be considered separately in a later wave.
We also ask optional broad questions about the kind of Universal Credit circumstances you could help test—for example claim type, work and payday pattern, children or childcare, housing and whether particular UC elements may be relevant. These categories help avoid recruiting only one type of claim. Exact income, rent, benefit award, employer or workplace name, address, claim reference, National Insurance number and documents are not required for the application and should not be entered.
Optional questions about health or disability-related UC elements, caring information or accessibility needs may reveal sensitive personal information. You can choose “prefer not to say”. Do not include a diagnosis or detailed medical information.
How the app makes its estimate
UC Planner asks for the information needed to make its own estimate and planning calculation on your device. It does not ask you to upload, photograph, paste in or store your official UC statement. The estimate is not a copy or record of an official statement.
During testing
TestFlight can supply technical information such as the app build, device and operating-system version, and crash information. Comments and screenshots are sent only when you deliberately choose to submit them through TestFlight. Email feedback is also something you choose to send. We may additionally hold the tester reference allocated to you and mission or entitlement progress records.
A requested comparison means reading your own next UC statement separately when it arrives and comparing it yourself with the app’s estimate. If you used historical information to model a past period, you may instead compare the estimate with the matching historical statement. The app does not receive or see the official statement as part of that comparison.
If a result appears wrong, start by describing the problem in general terms. Statements, payslips, identity documents, claim references, National Insurance numbers, bank details, addresses, employer or workplace names, children’s details and medical details are not required and should not be sent. Sending evidence is not required to report a problem or qualify for the Founding Tester benefit.
3 · Why we use it
Recruitment, testing, support and improvement.
We use information to select and manage a varied tester group; invite and support testers through TestFlight; assign missions; investigate and fix usability, accessibility, technical and possible calculation problems; respond to withdrawal or support requests; and manage the Founding Tester benefit.
We do not use tester circumstances to target advertising, sell personal information or make an automated decision with legal or similarly significant effect.
4 · AI-assisted development tools and confidentiality limits
References and redaction reduce risk, but do not guarantee anonymity.
Development tools used to investigate and improve UC Planner may include AI-assisted tools, including Codex or ChatGPT where used in the development workflow.
Contact details are kept in a private tester register. A tester reference is used in working material where practical, and direct identifiers are removed or redacted before voluntarily supplied feedback is shared with a development tool.
You choose whether to send feedback and what to write or attach. A free-text message or screenshot can accidentally include a name, email address or other personal detail despite the guidance above. We aim to spot and remove those details before using feedback with development tools, but cannot guarantee every detail will be identified. The app does not automatically submit feedback on your behalf.
Using these tools does not remove participants’ UK data-protection rights or Organised & Co’s responsibility to handle information carefully.
5 · TestFlight and Apple
Apple provides the beta-testing service.
TestFlight is Apple’s beta-testing service. Apple processes TestFlight information under its own terms and privacy policy. When TestFlight is used, Apple may provide Organised & Co with technical or tester information available in App Store Connect, including crash information and feedback that a tester chooses to submit.
You may use TestFlight for in-app comments or an optional screenshot because it can keep useful technical context with the report. Begin with a general description and check any screenshot carefully before sending it. Questions can also be sent to the programme email address without attaching documents or sensitive information.
6 · Legal basis
Legitimate interests and explicit consent.
For ordinary application, administration and feedback information, Organised & Co relies on legitimate interests in recruiting a suitable tester panel, improving the app and honouring the Founding Tester benefit. This is balanced against participants’ rights and supported by collecting only the information needed.
Where optional information may reveal health, disability, caring or accessibility information, explicit consent is requested before it is collected. Refusing or withdrawing this consent will not prevent an application, except where the information is genuinely needed for an optional mission the tester has asked to join.
7 · Who can access it
Access is limited to what is needed to run the programme.
Access is limited to Barry Collins or Organised & Co personnel who need it to run the programme and investigate feedback. Information may also be processed by Apple through TestFlight and App Store Connect; IONOS for website hosting and email; Cloudflare for the Turnstile anti-spam check; and carefully used development or AI-assisted tool providers described above.
Information is not sold or given to advertisers.
8 · How long we keep it
Different records have different retention periods.
| Information | Retention period |
|---|---|
| Application and contact information for people not accepted | Three months after recruitment closes, then delete it. |
| Accepted tester application profile, correspondence, raw feedback and screenshots | Until six months after public launch or the formal end of beta testing, whichever is later, then delete it unless a specific unresolved support or legal need is documented. |
| Founding Tester entitlement ledger | For as long as the lifetime ad-free entitlement exists. Keep only the minimum needed to honour or support it: tester reference, necessary contact details, entitlement status or redemption information, and necessary support history. |
The entitlement ledger does not retain the detailed UC coverage profile, raw feedback or screenshots.
9 · Your choices and rights
Participation is voluntary.
Participants can leave at any time and may ask Organised & Co to confirm whether their information is held, provide a copy, correct it, delete it where applicable, restrict or object to certain processing, or withdraw consent for optional sensitive information.
Requests can be emailed to app-feedback@organisedandco.com. Enough information will be needed to locate the record safely. Participants may also complain to the Information Commissioner’s Office.
Leaving stops future testing contact. It may mean an entitlement cannot be provided or continued where a minimum record is needed to identify or support it; the position should be explained before deleting an entitlement record.
10 · Security
Minimise what is sent.
The application form uses server-side validation, anti-spam measures and Cloudflare Turnstile. Access to the private tester register is limited, with identity records separated from reference-labelled working feedback where practical.
No online system can be guaranteed completely secure. The safest approach is not to send the sensitive information listed in this notice.
11 · Changes to this notice
The notice follows the programme.
This notice may change if the tester programme, form, TestFlight setup, feedback process, development tools or benefit process changes. The updated date at the top of this page will show when it was last revised.