Privacy Policy

Last updated 23 October 2026.

1. Who is responsible

Skin Clinicians Ltd (company number 17492865, 101 Harley Street, London W1G 6AH) operates ruxi.ai, the Ruxi Vision API and the embedded scanner. For account holders and website visitors we are the data controller. For people who use a scanner embedded on a customer’s website, that customer is the controller and we act as their processor. Questions and requests: [email protected]. ICO registration number: [VERIFY: to be inserted once issued].

2. What we process and why

Account holders (developers, clinics, brands)

• Account data: name, email address, password hash or Google sign-in identifier. Basis: contract. Kept while the account exists.
• Billing data: handled by Stripe. We store Stripe customer and subscription identifiers, not card details. Basis: contract and legal obligation (accounting records, six years).
• API usage records: API key used, analysis type, model, success or failure, response time, token count, timestamp, and the embed through which a call came. We do not store the images or the analysis results sent through the API. Basis: contract (quotas, billing) and legitimate interest (security, abuse prevention). Kept for the life of the account plus twelve months.
• Embed configuration: clinic name, logo, colours, wording, allowed websites. This is published by design: the scanner needs it.

Images submitted for analysis

Images sent to the API, or captured in an embedded scanner, are processed to produce the analysis and are not retained by ruxi.ai after the response is returned. They are passed to our model-hosting sub-processors (see section 4) for the duration of the request. A photograph of a face is personal data; the clinical scores derived from it describe skin appearance and are not a medical record. Where a scanner is embedded on a customer’s site, any storage of images or results on that customer’s own systems is governed by that customer’s privacy notice.

Website visitors

ruxi.ai does not set analytics or marketing cookies without consent. Sign-in uses a session cookie that is strictly necessary. The sign-in form uses Cloudflare Turnstile to block automated sign-ups, which processes your IP address and browser signals for that purpose.

3. The dataset behind the model

Ruxi Vision was trained on a clinician-annotated dataset of facial photographs collected with UK GDPR-compliant consent, as described in our published methodology (Gilleard et al., European Journal of Plastic Surgery, 2026). Images submitted to the API or an embedded scanner are not added to the training dataset.

4. Sub-processors and transfers

• Cloudflare (hosting, database, object storage, bot protection). Data at rest is held in Cloudflare’s infrastructure; some processing may occur outside the UK under Cloudflare’s standard contractual safeguards.
• Google Cloud (Vertex AI and the Gemini API) for model inference. Images are sent to Google for the duration of a request. Processing may take place in the United States under the UK Addendum to the EU Standard Contractual Clauses.
• Stripe for payments.
• Google for optional “Sign in with Google”.

5. Security

All traffic is encrypted in transit. API keys are shown once at creation. Embedded scanners never receive the API key; requests are proxied through our servers and checked against the websites the customer has authorised. Access to production systems is limited to named staff.

6. Your rights

Under UK GDPR you can ask for access to your data, correction, erasure, restriction, portability, and you can object to processing based on legitimate interest. Account holders can delete their account from the settings page, which removes account data, API keys and usage logs (billing records are retained as required by law). If you used a scanner on a customer’s website, please contact that customer first; we will help them respond. You can also complain to the Information Commissioner’s Office (ico.org.uk).

7. Children

The Service is not intended for anyone under 18. Customers embedding the scanner must not direct it at children.

8. Changes

We will post any changes here and update the date at the top of this page.