1. Who is responsible and how to contact us
Unifind Global Ltd, company number SC897549, operates UniFindChina and is responsible for the applicant and support information it decides to collect and use. Our address is 1 Glenogle Court, Crieff, Perthshire, PH7 4EF, United Kingdom. Contact gregor@unifindglobal.com about privacy, your information or a complaint. Our company domain is unifindglobal.com.
The payment seller/provider and other organisations may have separate legal responsibilities for information they process for their own purposes. We identify those roles below; paying does not make an applicant's information public.
2. The short version
- We use your account and profile information to run your account and compare your answers with published university, programme and scholarship requirements.
- We do not submit applications or send your profile to universities on your behalf.
- Matching requires a separate choice. Withdrawing it clears active matching answers and pauses matching, but keeps account/privacy access and the original paid expiry. Regrant and answer re-entry before expiry do not require repayment.
- We do not sell applicant information or use profiles or bug reports for targeted advertising. Non-essential analytics and advertising tracking are outside the initial launch design.
- Parents, payers and referral creators do not automatically receive access to your profile or matches.
- Support and privacy requests are handled by our operator through the business mailbox, with necessary privacy-case evidence kept in a restricted business Drive folder. Automated report intake, model review and support digests are not used for this launch. Do not include passwords, identity documents, payment details or other people's personal information in ordinary correspondence.
- Personal information is not anonymous merely because it is hashed, encrypted, separated from an account or submitted through a form without login.
3. Who the service is for
Applicants aged 18 or older can register directly on our website. Applicants sign in to access their own accounts and profiles. General public and legal pages do not require registration. We use a self-declared date of birth for the age boundary; we do not require passports, selfies, biometrics or documentary age proof for that purpose.
We do not knowingly admit under-18s to new accounts, matching or purchases. If an existing account needs age review, those covered functions pause, while account/privacy access and a correction route remain available. We do not automatically disclose an applicant's information to a parent or payer.
If you think an under-18 account has been created, contact us. We will assess the report using a proportionate process; do not send a child's identity documents in an ordinary email. Public pages may still be visited by younger people. Our minimum age is not proof that every visitor is an adult, and we do not use it to dismiss protections that apply to children.
4. Information we collect and where it comes from
| Category | Information and source | Main use |
|---|---|---|
| Account and identity | Information you submit: name, email, self-declared date of birth, and password through the authentication flow; provider verification/session state and internal account identifiers | Account creation, login, age boundary, ownership and security |
| Gender response — disclosure is optional | Male, female or “Prefer not to say”; no choice is preselected, and you can change it in account settings | The current matcher does not use gender. “Prefer not to say” does not reduce access or change results. We will explain any proposed new use before it begins; an optional answer does not by itself give permission for another use. |
| Matching profile | Your controlled citizenship choices, residence where the flow asks for it, education, qualifications and grading facts, subjects, study level, language evidence, study timing and preferences; limited fields where the implemented form permits them | Deterministic published-rule comparisons and profile continuity |
| Legal acknowledgements | Versions and timestamps of the notices/terms presented and recorded acknowledgements; separately recorded specific permissions where applicable | Demonstrating the actual information and permissions relevant to the service |
| Purchase service confirmation | The verified applicant-account contact used for sending; original order, payment and access facts; recorded Terms/Privacy document references and acceptance times; your separate request to start access and the wording shown for it; and minimal preparation and sending-outcome records | Providing your original service and legal-document copy and recording the actual request and sending outcome; separate from the payment provider's transaction receipt |
| Referral and access | A supplied referral candidate/code and valid attached attribution, order-beneficiary relationship, entitlement start/expiry/state | Correct price, access, fraud prevention and commission accounting |
| Payment events | Limited provider references, amount/currency and status facts, timestamps, refunds/disputes and associated audit facts received from the payment provider | Confirming payment, supplying or restricting access, support and financial records |
| Account security | Temporary verification/recovery claims, encrypted short-lived provider material, session state and narrowly scoped anti-abuse records | Safe authentication, single-use recovery, rate limiting and cleanup |
| Technical access | Requests inherently processed by hosting/authentication providers, such as network address, request time and browser/protocol information; our application uses separately keyed network buckets for specified anti-abuse purposes | Delivering and protecting the website; not advertising profiles |
| Manual support correspondence | Your sender address, message and necessary technical details you choose to provide, together with our replies and handling record | Investigating the issue and communicating an outcome; not automated model review |
| Privacy requests | What you ask us to do, original receipt date, proportionate ownership/identity evidence, actions taken, responses and outstanding obligations | Meeting applicable rights, protecting your information and recording actual fulfilment |
We do not store your raw card number in UniFindChina. The payment provider collects payment and billing information through its own checkout. We retain only the normalized facts and references needed for our responsibilities; a payer's billing information is not copied into the applicant profile.
We do not ask for admissions documents, passports, immigration records or family nationality documents. Citizenship is not inferred from residence or website language. Gender is not used by the current matcher; any future rule-specific use requires separate assessment and notice. Whether each field is necessary is assessed separately; its presence in a form is not, by itself, a legal justification for collecting it.
The automated bug form is outside this launch. Ordinary email exposes your sender address and message to the business mailbox and its provider. Send only necessary information; screenshots and copied URLs can contain private material. Information you type can identify you or someone else; a warning cannot make that content anonymous.
5. Why we use information
The table below describes the purposes and legal bases where UK/EU data-protection law applies. Other applicable laws can require additional notices or specific consent. Accepting Terms or acknowledging this notice is not a substitute for that consent.
| Purpose | Basis where UK/EU GDPR applies |
|---|---|
| Create the account you request and administer paid access | Steps you request before a contract and performance of a valid contract, only for information necessary for that purpose |
| Compare your matching answers with published rules, tailor relevant questions and keep the requested matching profile | Contract/pre-contract necessity for that requested service where applicable; additionally, our global separate matching-permission control and any legally required sensitive-data consent. Terms acceptance is not that permission. |
| Verify identity and ownership; prevent abuse; protect sessions, recovery and service availability | Our ordinary legitimate interests in a secure, reliable service, with a documented necessity/balancing assessment; contract where a particular operation is necessary to provide the requested service |
| Correct price/referral treatment and maintain the necessary access/order record | Contract for the purchase and promised discount; separately assessed legitimate interests for preventing abuse and keeping defensible records |
| Handle support correspondence and technical reports manually | Contract where necessary to support the requested service; otherwise assessed ordinary legitimate interests in resolving defects, with limited disclosure, safeguards and a way to object |
| Respond to legal rights, applicable accounting duties and lawful regulatory demands | The particular legal obligation that applies; record that obligation rather than inventing a generic requirement to retain everything |
| Resolve disputes and establish or defend claims | Necessary and proportionate legitimate interests, subject to applicable rules and safeguards |
| Uses requiring consent in your jurisdiction | Specific informed consent before that use, with a usable way to withdraw it; no inferred permission from unrelated activity |
If information is necessary to create or protect an account or calculate a particular match, not providing it may prevent that function. Optional or unknown answers are treated as such; we do not convert unknown evidence into a fabricated qualification or a rejection.
We do not choose consent for a purpose and then secretly switch to another basis when you withdraw it. Where we must retain a limited record independently by law, we will explain that distinct purpose and restriction.
Some laws classify information differently. For example, citizenship can be sensitive data under applicable US state law. Free text can also contain health, ethnicity or other sensitive information. We do not claim that our service processes no sensitive information merely because it is a study-discovery site.
6. Matching and automated processing
Your matching permission
Before covered profile use or matching, we ask separately whether you allow Unifind Global Ltd to store and use your matching answers, including current citizenship, for published-rule comparisons and relevant profile questions. This is not a marketing permission, university submission or permission for unrelated analytics. Account registration, Terms acceptance and payment do not grant it. The same control is offered globally without adding jurisdiction tracking solely to decide who sees it.
You can withdraw using the privacy controls. Successful withdrawal clears active matching answers and stops covered reads, writes, counts, new Checkout and result delivery. Account/privacy access, identity correction and necessary payment reconciliation remain available. Separately justified identity, financial and rights records are not silently relabelled as matching data. Retained copies are handled under section 11, not returned to matching use.
Your original entitlement expiry continues during a pause. Withdrawal does not automatically refund, extend or revoke it. Giving valid permission again and re-entering the necessary answers before expiry permits matching to resume without another payment, subject to other valid access conditions. This does not reduce statutory remedies. We cannot recall information already delivered to you. Contact us separately if you also want account closure or cancellation of a purchase.
How comparisons work
We compare the profile facts you supply against published programme and scholarship rules to show relevant opportunities and explain known requirements. This is automated processing and can constitute profiling. It does not decide admission, scholarship awards, visas or a university application. Those decisions are made by the relevant institutions, not by UniFindChina.
Known requirement failures can exclude an opportunity from personalised included results. Missing applicant or official information remains a check. Programme and scholarship requirements, preferences, lifecycle and source completeness remain separate. You can correct profile facts through the supported process and contact us about an apparent matching error.
No automated support QA model receives your reports under this launch. That deferred capability is separate from deterministic matching and cannot be introduced merely by accepting this notice.
Automated payment/access and security controls also operate. Contact us to challenge an apparent error. We do not represent every automated operation as exempt from applicable profiling or automated-decision rights.
7. Manual support and privacy requests
Email gregor@unifindglobal.com with the minimum information needed to explain your issue or request. Our operator handles this correspondence in the business mailbox and uses a restricted business Drive folder for necessary privacy-case evidence and handling records. Do not send passwords, recovery links, card details, identity documents or other people's information. We will arrange proportionate verification when needed rather than ask you to disclose credentials.
We check the business mailbox each working day and initially review privacy requests on the first check after receipt, with a backstop of seven elapsed days from the original receipt. If we received your request earlier through another route, that earlier date counts. This is an initial review, not a completion deadline; applicable legal response deadlines still apply.
We record the original receipt date, scope, verification outcome, actions and unresolved work. An acknowledgement means that the request was received, not that an export, correction or deletion is complete. We distinguish active-system actions, necessary retained records and provider copies still awaiting action or expiry. A later internal transfer does not restart the request.
Messages are not sent to an automated support-review model or copied into a consolidated support digest in this launch. Relevant details may be shared with an affected provider only where needed for your issue and under the applicable processing arrangements. Credentials and unnecessary profile content must not be included. Unexpected sensitive content is restricted and assessed, not freely forwarded. Retention and rights are described in sections 11 and 13.
8. Who receives information
| Recipient or service | Role and information |
|---|---|
| Authorised UniFindChina operator | Only the information needed for account/product support, security, reporting and lawful administration; access is not granted to every tester or creator |
| Vercel | Website hosting and request/security infrastructure; server-side request handling may involve information needed for the requested operation |
| Supabase | Account authentication and protected operational database; authentication-email processing and a protected forwarding component where that setup is used |
| Resend | Account/authentication email and separate purchase service confirmations, including the recipient address and content needed to send them. Service confirmations use the verified applicant-account contact and include the original recorded service information, Terms and Privacy Notice; no consolidated support digest or marketing email in this launch |
| Google Workspace (Gmail and Drive) | The operator's business mailbox for manual support/privacy correspondence and a restricted business Drive folder for necessary privacy-case evidence and handling records; provider-retained and recoverable copies are separate from active company-controlled working copies |
| Stripe Managed Payments | Checkout and related payment-status, fraud, tax, receipt, refund and transaction-support information under the applicable payment-provider arrangement; applicable provider notices describe information used for the provider's own purposes |
| Authorities or professional recipients where necessary | Only where a lawful requirement, necessary claim or properly assessed legal purpose justifies the specific disclosure |
GitHub is used for source and build workflows, not as the applicant, commerce or manual privacy-case store. Applicant correspondence is not sent to OpenAI for support QA in this launch. This is a boundary for customer data, not a claim that no development tools exist.
A provider may use some information for its own purposes, as described in its applicable notices, as well as handling information for us. We do not sell access to applicant profiles, give creators customer information or send applications to universities. Clicking an external link takes you to that organisation's service and privacy practices; ordinary web requests may reveal information to it.
9. International processing
The primary operational database region is London, United Kingdom. That does not mean all hosting, authentication, email, support, network or administrative processing stays in the UK. Providers and subprocessors can process information in other countries, including the United States.
Before a transfer is made, the applicable parties, locations and lawful transfer arrangements must be identified. Where required, these may include an applicable adequacy decision or approved contractual safeguards with the required assessment and supplementary measures. We do not claim that signing a template alone verifies every transfer or that every provider is certified under a particular framework. Contact us for information about the safeguards actually used and how to obtain an appropriate copy.
10. Cookies and similar information
The website uses cookies for account sessions, security, short-lived account workflows, your language choice and a referral candidate. We do not use advertising or non-essential analytics. Referral handling is limited to the creator-discount mechanism, not general browsing or cross-site tracking.
The language cookie can last up to 365 days, the referral-candidate cookie up to 30 minutes, the recovery handoff cookie up to 15 minutes and the pending-signup cancellation cookie up to 24 hours. Authentication cookies can have a browser-storage maximum of 400 days. That does not mean your login or paid access remains valid for 400 days: server-side expiry, sign-out and access checks apply separately. A browser cookie cannot extend the recovery action or retention limits in section 11.
Calling a cookie useful or essential does not by itself exempt it from consent. We ask for any consent required before information is stored or read. This notice does not authorise additional tracking. Payment and other provider pages operate separately under their own notices. Contact us about the storage used for your account.
11. How long information is kept
Different records have different purposes and clocks. Two years of access does not justify retaining every record for two years, and a new copy or retry must not restart a retention period. Retention limits below are maximum periods for the stated purpose, not a requirement to keep every record for the full time. We remove or minimise information sooner when it is no longer needed.
| Record | Retention period or criterion |
|---|---|
| Active matching answers | While needed for requested matching with valid permission. Successful withdrawal clears these answers and completion state; regrant needs re-entry. This is separate from provider copies and necessary account records. |
| Account identity | While needed to provide your requested account, security and rights access. Closure triggers removal or minimisation of unnecessary identity fields, preserving only a documented separate need. Expiry of paid access or withdrawal alone is not account closure. No automatic inactivity-deletion deadline is promised. |
| Payment, refund and commission records | Only the accounting/reconciliation information needed for the company's duties and unresolved transactions. Applicable UK company accounting records are normally kept for six years from the end of the last company financial year they relate to, with specified longer cases. This is not six years from signup, and does not apply wholesale to matching profiles, provider payloads or all correspondence. Provider records follow their own applicable duties. |
| Minimal matching-permission evidence | Up to 1096 elapsed days from the original permission event for the limited record of who made the choice, when, its purpose and the wording/version/locale shown. This does not include matching-profile answers. We remove unnecessary evidence sooner and rely on permission only while its original supporting evidence remains valid. Current permission or withdrawal state is kept as needed to enforce your choice; it is separate from the proof record. |
| Full privacy-request working case | Up to 120 elapsed days from the earliest evidenced original receipt, subject to earlier removal or minimisation and any shorter applicable limit. We remove irrelevant attachments and duplicates and minimise the case when its purpose ends. We do not keep the full file solely because a provider duty remains unresolved. A receipt expiry does not mean that your request has been fulfilled. |
| Minimal outstanding-duty records | Only the details still necessary for a specifically identified outstanding duty, with its reason and disposal or review trigger. We review these records within 30 elapsed days, or sooner when evidence, an earlier applicable date or a response requires it. Review does not restart the full-case period or prove that a provider has erased information. |
| External-retention cleanup acknowledgements | Up to 30 elapsed days from the original recorded result for the small status and reference record of the action, with earlier removal when no longer needed. This is not a copy of your profile, email or full privacy case, and is not a general period for all technical logs. An acknowledgement is not proof of deletion everywhere. |
| Initial automated service-confirmation work | No later than seven elapsed days after we first record your purchase agreement for Checkout, or sooner if its processing window ends. Unresolved work is escalated to our operator. This stops automation; it does not permit delaying the initial confirmation, guarantee a fix within seven days, or authorise automatically repeating an uncertain send. |
| Minimal original purchase agreement, start request and outcome evidence | Only while still necessary for the original purchase, normally ending no later than that order's original paid-access expiry: two UTC calendar years from its original verified successful-payment time. There is no routine later grace period. The record preserves the original agreement/request and outcome; retries, reviews, restoration or sending delays do not restart its clock. It is not a duplicate full email, the customer's own saved copy, the payment ledger or all provider-held copies. Specifically justified exceptions are handled as restricted records as explained below. |
| Incomplete signup reconciliation | Existing maximum of 24 hours from original creation; first terminal transition removes linkable fields, with the resulting non-identifying terminal row removed within seven days. This is not the account's lifetime. |
| Account-email verification/recovery material | Verification material has an original maximum lifetime of 30 minutes, subject to earlier expiry. A recovery action must be completed within seven minutes after verification starts and may expire sooner. Active recovery material is due for removal within eleven minutes of that same start, also subject to earlier expiry. The separate browser handoff cookie in section 10 does not extend either limit. Successful supported retirement removes remaining active custody; a stated expiry alone does not prove deletion from all retained copies. |
| Network abuse buckets | Separate, fixed one-hour expiry; retries do not extend the original period. Infrastructure providers' request records are separate. |
| Manual support correspondence and company-controlled copies | While necessary to investigate and respond to the issue. At resolution, review originals, attachments and duplicate copies; remove content no longer needed and retain only necessary evidence for a documented outstanding duty, dispute or claim, with its reason and review/disposal trigger. An unresolved issue is reviewed for continuing necessity, not kept indefinitely without review. Copying does not restart a clock. These criteria apply to manual correspondence and its necessary working copies. |
| Provider-held copies and recovery data | Use the provider's applicable period where established; otherwise record the particular retained category, purpose, role, reason for retention, restriction, review trigger and disposal route. Explain whether maximum expiry is unknown. A review date is not an erasure date. Unknown timing alone neither proves unlawful retention nor authorises indefinite use. |
We review retained information against its purpose, record category and necessary disposal or review trigger. An actual legal duty or unresolved case may justify a separately restricted minimum record. We identify that specific reason, limit access and use, and record when it must be removed or reviewed. A possible future problem is not automatically a reason to keep everything.
A review, retry, copy or later internal transfer does not create a new original retention period. Provider-held information with an unknown expiry remains an outstanding duty to assess, not a reason to renew our full working file. These criteria do not by themselves prove that deletion has been completed.
The accounting criterion above follows GOV.UK company-record guidance. The relevant financial year and category of record determine which period applies. This does not justify retaining unrelated information for the same period.
Resend's published standard window is 30 days for ordinary message content, metadata, delivery events and logs/metrics. Its separately described backup window does not establish a universal 37-day erasure promise; security and other provider purposes need separate treatment. Account-specific exceptions and other providers' copies are recorded separately, not covered by that number. See Resend's standard retention information for the provider's published description. Contact us about the arrangements relevant to your information.
When deletion is appropriate, active copies must be removed or irreversibly anonymised through the approved process. Restricted backups must not be reused to revive deleted information; restoration requires reapplying deletion and expiry controls. Expired authentication material must not be decrypted or restored into operational use. Provider acceptance, a configured expiry or a success message is not by itself evidence of physical deletion everywhere.
12. Security and limitations
Our design separates applicant information from the public-source catalogue, checks account ownership and entitlement on the server, limits privileged access, and protects short-lived authentication material. Provider credentials are not intended for the browser or support correspondence. The application does not automatically attach credentials to matching profiles or support reports. People can nevertheless type sensitive material into free text; that requires restricted incident handling rather than a claim that the report is harmless.
No service can promise absolute security, uninterrupted availability or instantaneous revocation of every previously issued token. Previously delivered information cannot be recalled from a person's memory or their own copies. If a verification or password-change outcome is unknown, we do not pretend it is confirmed or automatically repeat an irreversible operation. Contact us about suspected misuse without sending secrets.
13. Your choices and rights
Depending on the applicable law and processing, you can ask to access or correct your information, obtain an appropriate portable copy, erase or restrict it, object to uses based on legitimate interests, or withdraw specific consent. Where available, you can challenge qualifying automated decisions or appeal a rights refusal. We will explain any applicable limitation rather than treat the absence of a self-service button as the absence of a right.
When enabled, account/privacy controls provide access to your own bounded account export after a verified session and fresh current-password login. The download is a JSON file, not a public link or an emailed archive. It is not password-encrypted; protect any copy you save. It excludes other people's information, secrets and protected catalogue content. Provider-held material, support ownership questions or information beyond the download's supported scope require follow-up rather than a claim that the download fulfils every access request. Any lawful limits will be explained individually.
You can correct supported identity fields separately from matching permission. Correcting covered matching answers needs valid matching permission. A deletion request can require coordinated account retirement, support-copy restrictions and provider follow-up. Required financial reconciliation and justified records are preserved without leaving the profile available for matching. Account retirement, authentication-user removal and backup deletion are distinct steps.
A request receipt records receipt, not fulfilment. We preserve the original request date and explain actions completed, retained exceptions and work still outstanding. Before retirement, arrange a verified follow-up route with us: closed accounts cannot continue using signed-in case access. A technical refusal or pending payment does not by itself decide whether your legal request is valid.
Contact gregor@unifindglobal.com. We may use proportionate verification to avoid giving your information to someone else. Do not send passwords, full card numbers or identity documents as a first step. Requests made by an authorised representative need appropriate authority; paying for another applicant is not such authority. Neither an age-review restriction nor a payment by someone else automatically authorises disclosure to that person.
We will respond within the applicable legal time limit, explain a lawful extension or refusal where permitted, and identify an available complaint or appeal route. You do not have to waive a right to continue receiving unrelated service functions. The exact effect of a request on necessary account data or an unresolved purchase will be explained.
You can complain to us and to the appropriate data-protection authority. In the UK this is the Information Commissioner's Office. Other locations may provide a local supervisory authority, attorney general or other regulator. Contacting us first does not remove those rights.
14. International notices and changes
This notice is written for an internationally available service, including the US, with mainland China outside the launch scope and unsupported payment locations excluded from purchases. Payment location is handled through the provider's transaction boundary; matching citizenship and website language do not establish it. This does not authorise additional profile-based location tracking. Payment availability is not a declaration that one country's law overrides protections you have elsewhere. Additional local notices, permissions, representatives or rights procedures must be supplied where required. Contact us for information about any representative or registration that applies to your location.
We will identify the published version and date and notify material changes as appropriate. A new purpose or additional tracking requires its own assessment and any required permission; it is not silently authorised by a wording change. A language preference does not establish citizenship or residence.