Information handling
Know what you are sharing
A practical description of the website and app as they work today. The full organisational privacy notice remains under review.
Who is responsible for the information?
FOUNDATIONS handles platform accounts, business enquiries and administration. A salon, clinic or academy determines the purposes of its own client, treatment, model and learner records. The proposed company name is Foundations Group Ltd; incorporation and the actual legal operator’s identity and address still require confirmation. The final notice must identify each applicable controller and any processor arrangements before commercial rollout.
Purposes and lawful-basis review
Account administration, requested support, billing, security and organisation record keeping have different purposes. Each controller must identify and document the applicable lawful basis, and an additional condition where health or other special-category information is involved. Treatment consent is not automatically a data-protection lawful basis for every use. The final notice must state the bases actually approved; this draft does not invent them.
Private AI drafting
AI drafts are processed by the configured model on the owned server. External AI providers are disabled. A document brief and any source text deliberately supplied are processed for drafting; reply suggestions use the stated conversation context. Drafting audit events retain an input hash and outcome rather than the prompt text. Do not submit client-identifying or health details into a general policy or course brief. Saved output becomes part of the record you explicitly choose to save.
Working documents and cleaning records
Owners and managers can save encrypted working documents, structured answers and version history against their organisation or a named client. Organisation working records are separate from a client’s signed declaration. An explicitly issued client copy may include staff-prepared answers for that client to check and correct. Completed cleaning records identify the recorded person, date, work and exceptions; corrections create a new version.
Your rights and requests
Depending on the processing and applicable law, you may have rights to access, correction, erasure, restriction, objection or portability, and to withdraw consent where consent is relied on. Rights are not absolute: care records, claim holds and other obligations may affect a request. Contact the organisation responsible for the record or the published platform contact. You can raise concerns with the Information Commissioner’s Office. The final notice must specify the confirmed operator contact and complaint route.
Recipients, hosting and transfers
Authorised organisation users and restricted platform administration may access information according to their permissions and support responsibilities. Payment details are handled by the configured payment provider when checkout is enabled. The exact hosting country, suppliers, backup locations, international transfers and safeguards require operator verification and disclosure in the final notice. An owned server alone does not establish the legal location of every processing activity.
Retention and deletion requests
Organisations choose active treatment-media retention based on their jurisdiction, insurer and approved policy. Eligible removals enter the separate six-year restricted recovery process; signed documents and clinical records use withdrawal or correction rather than silent destruction. Account, enquiry, billing and backup schedules still require a documented operator retention policy. A deletion request must be assessed against those purposes and any lawful hold, not answered with a blanket six-year rule.
Council and postcode lookups
Typing a council name searches the supplied council directory. Selecting Find council sends the entered business postcode through this server to Postcodes.io to identify the council; the postcode is not added to your saved assessment. Selecting a council can request public licensing pages from its official website. Council page previews are cached briefly, with retrieval times shown. These lookups do not send your account details, checker answers or client records to the council or postcode provider.
Public enquiries
When website enquiries are open, the form saves your name, email, optional business name, sector, chosen topic, optional business stage and timescale, and message in the private administrator inbox. The team uses those details to review and respond to your enquiry. Submitting it does not sign you up to marketing or create a paid subscription. A submitted business readiness check also records the supplied contact phone number and assessment answers in the administrator inbox for follow-up. Signed-in assessment sharing uses the account email; unfinished browser drafts are not leads.
Complaint referrals and business participation leads
Initial complaint referrals are stored in the private FOUNDATIONS administration inbox with the complainant’s name and reply email, business name and any public contact details supplied, summary, requested outcome and whether the concern has already been raised. Referrals are accepted even when membership is unknown or the business has not enrolled. Public business details may be used to explore participation; no message is sent automatically. A separate optional permission records whether the complainant’s name and summary may be shared with the named business; it is off by default and does not include their email. The notice version and permission choice are retained. Acknowledging storage and business outreach does not sign the complainant up to marketing or authorise sharing clinical records. Do not include health records, images, payment credentials or another person’s private information. A referral does not open an adjudication case. Contact the team with the reference to correct details, change sharing permission or request a retention review before any proposed disclosure.
Member accounts
Invited access is tied to an email address. When online subscription signup opens, a new business account is created only after provider confirmation and is never merged into an existing account by matching email. Account passwords are stored as salted hashes, not readable passwords. Your organisation memberships determine which private records you can access. An assigned package and the permissions granted by the organisation owner or delegated administrator determine access to paid templates.
Subscription signup and billing
When hosted subscription signup is enabled, we keep the business name, website identifier, account email, selected package, accepted recurring terms and provider customer/subscription references. Card details are entered with the configured payment provider, not stored by FOUNDATIONS. Pending signup passwords are held as salted hashes and cleared after activation or expiry; provider states determine trial, payment, grace and suspension access. No client clinical records are sent to the billing provider.
Support requests
Signed-in support requests are saved in the administrator inbox with your account email, support category, subject and message. Administrators can update their status. Your account can view its 25 most recent support requests. Organisation conversations are separate from this support channel.
Internal campaigns and communication choices
An organisation owner or manager can draft and send individual portal messages to active linked client or student accounts within that organisation. Optional promotional campaigns require an explicit in-app marketing preference, off by default; preference versions, notice wording and changes are recorded. Essential service messages must relate to an existing service or learning relationship and must not be used for promotions. Campaign drafts, purpose, audience, delivery references and available read receipts are stored. No email, SMS or WhatsApp provider is used for these messages. Campaigns do not use medical, skin, disability, nationality or other sensitive attributes as targeting filters. Changing a preference prevents future optional sends; it does not erase a message already delivered.
Optional accessibility and skin information
Clients can record preferred language, communication and accessibility needs, disability information they choose to share, skin descriptions and concerns, acne history, consultation goals and recovery commitments in their organisation’s encrypted health profile. These questions are optional and are not shared between organisations or used for campaign targeting. A self-description does not verify a diagnosis, skin classification or treatment suitability. The treatment guide prepares discussion points for human review; using its draft does not save the profile until the client chooses Save.
Private conversations
Team conversations include their current organisation participants. Direct client conversations use the linked client account and authorised business staff; FOUNDATIONS support conversations have their own account permissions. Keep health histories and payment details out of ordinary messages.
Your browser session
Access tokens stay in memory. Choosing Remember this device adds a Secure, HttpOnly cookie that restores sign-in for up to 30 days; browser JavaScript cannot read that cookie. Remembered devices can be removed from account controls. Leave the option off on shared computers.
Private client documents
Organisations can prepare reviewed text declarations, consent documents, agreements and aftercare information for a named client. Issued content is locked. Signing records the account, typed name, document hash, acknowledgement and time. Aftercare read acknowledgements and in-app notices are stored separately. These are operational records, not an independently verified identity or witnessed-signature service.
Private photos and ID requests
Treatment-image uploads require a separately signed photo-consent document. ID and selfie uploads require the named client’s explicit upload acknowledgement and are available only to that client and authorised organisation admins for manual review. Images are encrypted on this server, stripped of location metadata and removed from the active media store after the organisation’s reviewed retention period, subject to any claim hold. Removed files enter restricted master-admin recovery for six calendar years. The recovery period is additional retention, not immediate erasure; organisations must account for it in their lawful basis, notices and agreements. Backup retention is separate and must be managed by the operator. No face-matching, liveness service or external AI receives these files.
Academy learning records
A student portal can hold course enrolments, published text lessons, completion records and supervised model appointment times. A student enrolment does not grant organisation staff access. Lesson completion is a learning record, not proof of a professional qualification.
Assessments and invitation requests
Business check answers stay in session storage in your current browser tab until you save them or request an invitation. An invitation request stores your name, email and business answers on the server, with a request in the administrator inbox. Once signed in with the matching email, you can open the assessment in your account. Saved assessments and reviewed actions belong to the account that saves them.
Template studio
Templates require an account; a free selection is available and paid templates also require an active package and team permission. Work area labels and organisation context are sent to the server to generate a draft. Generated wording remains unsaved until you choose to save an organisation working record. Saved versions and structured answers are retained in the selected private file; downloaded files remain on your device.
Hosting and service records
Website and API hosting can keep technical connection and operational logs. Access changes and selected record changes are recorded in the application's audit history.
Keep sensitive information out of public forms
Do not submit client or patient records, health information, payment details or passwords. If a piece of work needs confidential information, agree an appropriate way to share it with the team first.
A public business contact address is being prepared. Online enquiry collection stays closed until an administrator sets that address and opens the form.
This feature summary is not a completed organisational privacy notice. Operator details, retention arrangements and the full notice must be confirmed before wider customer rollout. Contact and enquiry availability →
