Privacy notice

How Sine uses your information

Effective 27 September 2026, updated 24 October 2026 for department selection, NHS and HSC accounts, supervisor email eligibility and subscriptions, and 25 October 2026 for campaign measurement. This notice applies to getsine.app and the Sine service.

Who is responsible for your data

Fyllio Ltd (company number 16520641) is the data controller for Sine. Our registered office is 11 Rockwell Road, Bolton, United Kingdom, BL6 4NT.

The data protection contact is Dr Matthew Kneale. You can contact us at sign@getsine.app.

What Sine is for

Sine helps clinical fellows keep workplace learning evidence, private reflections and teaching records. Senior colleagues can assess their work, and colleagues can arrange learning opportunities through pings. It is not a patient record, clinical communication system or substitute for an employer or Royal College portfolio.

Do not enter patient names, NHS numbers, dates of birth, addresses, hospital numbers, bed or cubicle identifiers, or other information that could identify a patient. Sine screens some free text for common identifiers, but the filter is an additional safeguard rather than permission to enter patient data.

Information we process

  • Account and professional identity: email address, name, grade or role, GMC number where supplied, saved trusts or health boards and departments, current site for pings, onboarding status and account identifiers. Changes to your professional details and department are recorded in a private account history.
  • Educational evidence: activity type, title, date, broad setting, notes, assessment or entrustment level, feedback, sign-off status, timestamps, receipt code and record integrity hash.
  • Private reflections and teaching records: the text and broad educational details you choose to save, your name, saved versions, linked records you own, and your approval or delivery declarations. These declarations are separate from a colleague’s clinical assessment.
  • Teaching delivery certificates: the teacher and named organiser accounts, captured names, session title, date, duration, revision, personal attestation, timestamps, issued PDF, integrity hashes and certificate status changes.
  • Signer information: work email, self-declared name, current grade or role and GMC/NMC/HCPC registration details, the route used to sign, any captured personal sign-off declaration and its version, and the status and audit note of any targeted register, identity or seniority check.
  • Collaboration information: practice interests, on-shift status, private groups, pings, recipients, responses and related timestamps.
  • Presentation access uses your email address to send a code through Resend. Sine stores only keyed hashes of the address and code, with request counts for abuse control. A daily cleanup removes records more than 24 hours old, even when no further code is requested. Delayed or failed cleanup can extend retention. This does not create an account.
  • Notification information: optional web-push subscription endpoint, cryptographic push keys and a device label; a push token and platform for the Sine phone app where installed; or email delivery details where email is used.
  • Campaign measurement: counts of visits to Sine’s public pages and sign-in code requests, with the campaign values in the link you followed, the referring website’s name and whether the device was a phone or computer. A new account also keeps the campaign it arrived with, or the phone app platform it started on. See Campaign measurement.
  • Security and administration: hashed invite/code data, pseudonymised device and network identifiers used for rate limiting, failed verification attempts, changes to profile email, name, grade and GMC details, administrative audit events, authentication events and operational logs. Network identifiers are created with a server-side keyed hash rather than storing the raw IP address.

We do not ask you to provide patient information or health information about yourself. If information of that kind is entered accidentally, it is outside Sine's intended purpose and we may remove it where we identify it.

Where the information comes from

Most information comes directly from account holders and signers. Trust, health board and department names and postcodes come from public NHS and HSC directories. New assessment requests, teaching records, reflections and pings retain the workplace selected when they were created. Profile changes do not relabel older records. Pings and colleague searches are limited to your current hospital site and trust. Other saved workplaces do not receive pings until you make them current. Reflections remain private unless you choose to export and share them. You can save several workplaces and choose where each new evidence record took place. These choices are self-declared. Removing a saved workplace does not remove it from existing evidence. We compare organisational email domains to apply the same-trust signing rule, with an exception for NHS.net supervisors. Shared national email domains do not establish a trust match. Work email confirmation establishes access to the mailbox, not independent verification of professional identity or eligibility. We may compare professional registration details with publicly available GMC, NMC or HCPC register information when checking the integrity of a sign-off. These checks are targeted rather than routine approval of every signer. Technical and security information is generated when the service is used.

Why we use it and our lawful bases

Where we rely on legitimate interests, we balance those interests against the impact on the people whose information is used. Sine is designed to minimise data, restrict access and avoid patient information.

Who can see information in Sine

Account holders can see their own requests and evidence. Signers receive only the request they have been invited to review. Pings and directory features expose only the information needed to arrange the selected learning opportunity. Administrators have restricted access where needed to manage accounts, investigate integrity issues and perform professional-register checks.

Anyone who has both a valid Sine receipt code and the matching activity date can see the activity title and type, the resident's name, the activity date, the signer's name and grade, the assessment level where recorded, the sign-off timestamp, the current professional-register check status, the verification route and the record fingerprint. Feedback and private notes are not shown. We do not sell personal information.

Reflections and teaching records are private to their owner in the ordinary service. They do not appear in clinical receipt lookups, colleague directories or opportunity pings. Approving a reflection records your own review. Marking teaching delivered records your own declaration. You choose whether to share an exported copy and are responsible for checking its contents and recipient.

If you request a teaching certificate, the selected organiser can see the captured teacher name and session title, date, duration, location and revision. They confirm delivery personally through their own account. Both parties can access the issued PDF. Sine does not send an invitation or certificate automatically. The organiser cannot see your private objectives, reflection or learner responses through this invitation.

A recipient can check a certificate PDF on the verification page. Its file digest is calculated on their device; the PDF is not uploaded. A matching digest and verification token return the current status, issue date, a generic organiser-attestation label and fingerprint, without names or session details. Copies already shared outside Sine remain with their recipients.

Optional voice dictation

Where available, you can record your own reflection for up to one minute. Recording starts only when you choose it. You can listen and discard locally before choosing Send for transcription. Do not record patients, colleagues or background conversations, and leave out patient identifiers.

Sending shares the recording with OpenAI’s Whisper transcription service through Sine’s server. The configured OpenAI project uses its Global service, so processing may take place outside the UK. UK processing is not assured. OpenAI’s published policy for this transcription endpoint states that audio is not used for training and is not retained as application state or for abuse monitoring. Provider contractual exceptions and infrastructure handling remain subject to the applicable terms. Read OpenAI’s data controls.

Sine processes the audio transiently for transcription and does not save it to portfolio storage or an audio upload queue. A local playback copy remains in the page until it is discarded or the page closes. We do not deliberately log audio or transcript text. The returned transcript is not saved until you check, correct and deliberately save it.

When you save voice-derived text, Sine records the corrected text, its revision, the time and version of your responsibility declaration, and integrity hashes linking it to the source recording and returned transcript. The hashes do not allow playback of the audio. These records support the requested portfolio service and integrity of your review. They remain until the reflection or account is deleted, with infrastructure backups handled separately.

Content-free job, cancellation and usage metadata limits duplicate requests and abuse. Jobs expire after twenty minutes. Daily maintenance removes job and cancellation records more than 48 hours old and usage buckets older than two days. Delayed cleanup can extend retention. These records contain account/session references, source IDs, statuses and hashes, rather than audio or an unsaved transcript. Aggregate usage can remain after account deletion until cleanup.

Optional AI reflection drafting

You can use your typed reflection notes to request a draft. Check the exact notes and approve them for this purpose before choosing Generate. A recording is not required. Leave out patient identifiers. Editing your notes clears this approval and invalidates a pending or returned draft.

Generate sends the approved notes to OpenAI through Sine’s server to organise and rephrase them. The configured service is Global, so UK processing is not assured. OpenAI does not use API content for training by default. Sine requests no stored response, but OpenAI may retain text for up to 30 days for abuse monitoring under its standard controls. Contractual exceptions remain subject to its terms. Read OpenAI’s data controls.

Sine processes the notes and returned draft transiently. It does not save a separate copy of unsaved source notes, deliberately log their content or automatically save a generated reflection. A saved source reflection keeps its existing history. You compare the editable draft with your notes, correct it and confirm responsibility before saving it as a new reflection. Automated checks cannot confirm factual accuracy.

Saved AI assisted reflections show their assistance attribution. Sine records the source and generated text hashes, model and prompt versions, source approval time and a review declaration bound to the corrected saved revision. Hashes do not reproduce the notes. These records remain with the reflection until record or account deletion, with infrastructure backups handled separately. Later edits require a fresh review declaration.

Drafting uses separate content-free jobs, cancellation markers and daily usage counts. Jobs expire after twenty minutes. Daily maintenance removes job and cancellation records more than 48 hours old and usage buckets older than two days. Delayed cleanup can extend retention. Cancellation prevents a pending result being saved but does not prove that OpenAI stopped processing or billing. Writing manually remains available.

Payments and billing records

Fyllio Ltd is the seller. Stripe processes subscription payments and receives your name, email address, Sine user ID and the payment details you enter on Stripe’s hosted pages. Sine receives subscription status, payment dates, invoices and limited card information such as the brand and last four digits. Sine never receives your card number.

We process subscription information to perform our contract with you and retain billing records to meet legal obligations. Tax records are normally kept for six years, including after account deletion. Stripe’s payment records are retained separately from your portfolio.

Stripe may process data internationally under the safeguards in its Data Processing Agreement. Stripe’s hosted Checkout and customer portal may set cookies on Stripe’s domain for payment and security purposes. Read Stripe’s privacy policy and cookie policy for details.

Campaign measurement

When we advertise Sine or share a link to it, the link can carry campaign labels such as utm_source=instagram or utm_campaign=launch. Sine counts visits to its public pages (the home, sign-in, help, privacy and terms pages) and sign-in code requests, together with those labels, the name of the website that sent you and whether you used a phone or computer. Signed-in pages, sign-off links, certificates, feedback forms and the survey are never counted.

This measurement is built into Sine and stored in its London database. It uses no cookies, browser storage, advertising identifiers or third-party analytics service. Sine does not store your IP address or browser details with these counts, and it cannot follow you between visits. We do not share campaign information with advertising platforms. Your browser’s Global Privacy Control or Do Not Track setting stops these counts.

The campaign labels travel in the page address from the home page to sign-in. If you create an account, Sine keeps the labels you arrived with, or the phone app platform for an account started in the app, linked to your account. This lets us count how many new accounts and subscriptions each campaign produced. Only administrators can see the totals, which are shown by campaign rather than by person. The link is deleted with your account. A separate count of new accounts, without any link to you, is kept for the period below.

The App Store and Google Play can report app downloads by campaign to us as totals under their own privacy policies. The Sine phone app does not read your device’s advertising identifier or ask to track you.

Service providers and transfers

We use specialist providers to run Sine, including Supabase for database and authentication services, Vercel for web hosting and runtime services, Resend for transactional email and OpenAI for optional voice transcription and reflection drafting. If you enable web push, your browser or operating-system push provider also processes the notification endpoint needed to deliver messages. Notifications for the Sine phone app are relayed through Expo's push service to Apple or Google.

Support email sent to sign@getsine.app is received by Resend and forwarded as plain text to a controlled Gmail inbox managed by Dr Matthew Kneale. Attachments remain in the restricted Resend receiving view and are not downloaded or forwarded automatically. Do not send patient details or access codes.

The production Supabase database is hosted in London (UK) and the Sine application runtime is deployed in Vercel's London region. Transactional email is sent using Resend, which processes email delivery data in the United States. Browser or operating-system push providers, and Expo (United States) for the phone app, may process notification delivery data in other countries. Where UK data protection law requires safeguards for an international transfer, we use the applicable contractual safeguards, adequacy arrangements or other lawful transfer mechanism.

How long we keep information

  • Account, profile, requests, groups and collaboration data are normally kept while the account remains active. Removing a resident account deletes that resident's requests and associated sign-offs.
  • Private reflections, teaching records and their saved versions are kept until you delete the record or your account. Deletion removes their live database records and versions. Infrastructure backup retention is separate; this notice does not promise immediate erasure from provider backups.
  • Deleting a teaching record or either certificate party's account removes the associated certificate snapshots, names, issued PDF and status events from the live database. A verification-token hash and PDF digest remain so a recipient checking that file sees withdrawn status, without names, dates or session details.
  • A sign-off given to another person is retained with that person's evidence even if the signer later stops using Sine, because preserving attribution and integrity is part of the purpose of the record.
  • Expired invitations cannot be used after expiry. Related invite metadata may be retained with the underlying request for integrity and audit purposes.
  • Push subscriptions are kept until disabled, invalidated by the push provider or the account is removed.
  • Pseudonymised failed code or receipt attempts are short-lived. A scheduled maintenance task deletes them once they are more than one day old.
  • Administrative, register-check and security records are kept only for as long as reasonably necessary to demonstrate the integrity and security of the service, handle disputes and meet legal obligations.
  • The audit of changes to your profile email, name, grade and GMC details is deleted with your account. A declaration attached to a sign-off remains with the colleague’s evidence under the sign-off retention rule above.
  • We review support correspondence when the query closes and remove personal information that is no longer needed. Resend applies its service retention policy to the original email. Forwarding receipts contain delivery identifiers and times, without message content, and completed receipts are removed after 90 days by the scheduled support check. Provider backups are separate.
  • Campaign counts without identifiers are deleted after 25 months by the scheduled maintenance task. The campaign or platform linked to an account is deleted with the account.
  • Infrastructure logs are retained according to the operational retention settings of our service providers and are not kept by us for longer than needed for security and troubleshooting.

We review retention as Sine develops and will update this notice before materially changing how information is kept.

Cookies and local storage

Sine uses a small number of browser storage items needed to provide and secure the service. These do not require an advertising-consent banner because they are strictly necessary or are created when you choose a preference. Campaign measurement uses no cookies or browser storage.

  • Authentication cookies: Supabase session cookies keep signed-in users authenticated and refresh the session securely.
  • sine_device: a random 90-day HTTP-only cookie used to bind short-lived sign-off invitations to the browser that opened them.
  • sine_rate_client: a random 90-day HTTP-only cookie used with a keyed network identifier to limit repeated receipt and invitation guesses without treating everyone on a hospital network as the same browser.
  • Theme and tutorial preferences: browser local or session storage remembers the appearance setting and whether the optional walkthrough has been completed or skipped.
  • Teaching invitations: when you open an organiser invitation, tab session storage preserves its token through sign-in. The phone app keeps a pending invitation in memory rather than persistent storage. The invitation expires after 72 hours and still requires the selected organiser's account.

Security

Sine uses access controls, row-level security, short-lived and single-use invitation mechanisms, cryptographic hashes, rate limiting, restricted administrative functions and encrypted network transport. No online service can promise absolute security, so please report suspected misuse or disclosure promptly.

Your rights

Depending on the circumstances, UK data protection law gives you rights to access your personal information, correct it, have it erased, restrict its use, object to processing, and receive certain information in a portable format. Where processing is based on consent, you can withdraw that consent without affecting earlier lawful processing.

You can permanently delete a non-administrator Sine account yourself from Your details after typing your email address to confirm. Export evidence first if you want to keep a copy. Sign-offs you gave to other people remain on their records to preserve attribution. For other rights requests, contact sign@getsine.app. We may need to verify your identity before acting on a request.

You can also complain to the Information Commissioner's Office. See ico.org.uk/make-a-complaint.

Automated decisions and marketing

Sine does not use personal information to make solely automated decisions that produce legal or similarly significant effects. We do not use Sine account data for third-party advertising and we do not sell it. Campaign measurement tells us which of our own adverts and links bring people to Sine. We do not upload account lists to advertising platforms or use advertising pixels.

Teaching session feedback

If you receive a teaching feedback link, the form offers optional ratings about the session. It does not require a Sine account, name, email address or professional registration number. Participation is optional. We use ratings to help the teacher review and improve the session, under the legitimate interest described above. There are no written comments or attendee lists. The teacher sees one fixed summary after closing the form. A total or question score is withheld unless at least five accepted responses support it. Responses are not verified unique people, and this threshold does not guarantee anonymity or prove attendance.

Sine uses an expiring submission nonce to prevent replay and short-lived keyed network rate controls to limit abuse. Network rate keys are kept separately from answers. Closing or revoking a form deletes its individual answers and submission nonces from the live database. A scheduled maintenance task also removes answers from open forms more than 30 days after expiry and clears expired rate controls. Timing depends on that task completing. Hosting providers may retain request URLs, IP addresses and times under their operational policies, so an account-free form is not a promise of anonymous infrastructure logs.

Clinical fellow sign-off survey

The voluntary survey at getsine.app/survey asks about workplace sign-off experiences and views on a proposed approach. It does not require an account or ask for a name, email address or GMC number. Responses are stored separately from Sine accounts and sign-off records, with a random submission identifier and submission time. We do not attach an account identifier, browser identifier or IP address to the answers.

Sine administrators can review and export responses to understand the current process and inform development of the service. Please do not identify yourself, patients or colleagues in optional written answers. Answers are saved only when you submit the form. The hosting providers may keep separate technical logs of visits under the operational arrangements described above.

Because we do not collect your identity with a response, we may be unable to identify which response is yours after submission. If you accidentally include identifying information, contact sign@getsine.app so we can investigate and remove it.

Changes to this notice

We may update this notice when the service or law changes. The effective date at the top tells you which version applies. If a change materially affects how existing personal information is used, we will take reasonable steps to bring it to users' attention.