
NurseryBill AI · Research concept
Confused about your nursery bill?
We’re exploring a tool to help parents make sense of nursery fees. It is a concept currently being researched, and is not available to use yet.
Help shape the ideaTwo months, one clearer picture
- September
- £425
- October
- £510
- Difference
- +£85
Entirely fictional amounts, shown to explain the idea. This is not the result of an actual AI analysis and does not explain why a bill changed.
What could it help with?
- Compare nursery invoices from different months.
- Explain changes in fees and funded childcare hours.
- Highlight unexpected charges or differences.
- Help parents identify questions to ask their nursery.
These are proposed capabilities. No AI analysis, invoice uploads or payment processing are offered here.
Tell us what would help
Four short questions to understand interest. Questions 1–3 are required; email and updates are optional. Please share only your own preferences.
Research privacy notice
AZ Digital Solutions is responsible for this research. Collection stays closed until scheduled cleanup and the privacy arrangements have been verified. When collection opens, we use your questionnaire answers to assess demand for NurseryBill AI, on the basis of our legitimate interests in evaluating the idea. We use limited security data for our legitimate interests in preventing abuse.
Email is optional. Providing it requests early-access contact by email and gives consent for that purpose. Future product updates by email require the separate, unchecked consent box. You can answer without providing an email. We do not request children’s information, invoices or payment details, and this form sends no automated emails.
We store answers separately from optional contact details, linked by a response reference. Contacts include your consent choices, notice version and timestamp. Supabase processes the research data in our London database. Cloudflare Workers serves the static website and runs its API handlers in this deployment. Authorised owner access and server credentials are restricted. A London database does not mean every provider operation, support activity or log stays in the UK: providers may use subprocessors and international processing arrangements.
We retain responses and optional contacts for up to approximately 90 days from submission, deleting them earlier when this research experiment ends or when an applicable deletion request is fulfilled. The planned hourly cleanup normally allows up to one additional hour. We do not keep the early-access list indefinitely or carry consent into a different purpose automatically.
Research visit measurement uses aggregate daily page-view counts and approved campaign codes, without research cookies, browser storage, fingerprinting or persistent visitor identifiers. Page views are not unique people, and are not linked to survey responses. Daily aggregate buckets are kept for approximately 90–91 days. A daily changing hash of your network address is kept separately for rate limiting, normally for approximately 24–26 hours; it is pseudonymous security data. Raw network addresses are not stored in the research tables, but infrastructure providers may process them in request logs.
Scheduled deletion can be delayed by an outage, failed job or paused free database. We review cleanup operation and remove overdue data promptly after recovery. These periods describe the active research database; provider logs, backups and any authorised exports have separate retention and deletion arrangements. We cannot promise immediate removal from every backup. Deleted information must not be reintroduced into use after a restoration.
To withdraw early-access or product-update consent, remove your email, request deletion or object to research processing, email hello@azdigitalsolutions.co.uk. Tell us whether you want to stop updates, remove contact details or delete your response too. We may check your identity proportionately. Withdrawal does not affect earlier lawful processing. An answer submitted without email may not be identifiable later; we do not collect extra identifying details solely to locate it.
Continue with research visit measurement off. This stops subsequent visit counts while that URL is used; we also honour Do Not Track for visit measurement. It does not undo an already aggregated count. For your other rights, contact details and how to complain to the ICO, see our Privacy Policy.