Privacy Policy

This policy applies to the yooi.me portal and to any website, app, or other Yooi service that links to it (together, the “Services”). Yee Fei, based in Singapore, is the operator of yooi.me and the controller or organisation responsible for the personal data covered by this policy, except where an app-specific notice identifies another party or role. Yee Fei is also the public privacy contact and person responsible for data-protection matters for the Services.

A linked app may have an additional privacy notice because its data, providers, features, or legal obligations differ. That app-specific notice controls to the extent it conflicts with this general policy. Third-party sites and services reached through links have their own privacy practices.

Questions and privacy requests may be sent to yeefei@yooi.me with “Privacy request” in the subject line. Please identify the Yooi service involved, but do not email passwords, full payment-card numbers, identity documents, or other unnecessary sensitive data.

The data involved depends on which Services and features are used:

• Account and identity data. Clerk provides authentication and session services. This can include an account identifier, email address, name, profile details, sign-in method, session information, and authentication or security events. Where central Yooi account features are enabled, Convex may hold a Clerk authentication identifier (authId), email, name, role, app-access records, service tier, and summary usage records.
• Contact and support data. The contact form collects an email address, message, and opportunity type. Submissions are transmitted through Resend and delivered to a Gmail inbox. Emails, support requests, feedback, and related correspondence are also processed.
• Service and transaction data. A linked app may process app settings, feature activity, plan or entitlement data, usage totals, payment or transaction references, and customer support history. Full card details are generally handled by the payment provider identified in the app-specific notice rather than by the portal.
• User content and AI data. Depending on the linked app, this can include files, text, images, audio, prompts, instructions, configuration, generated outputs, and feedback about those outputs. The app-specific notice describes its content and AI providers.
• Technical, device, and security data. Hosting, authentication, database, and security providers may automatically receive IP address, request and response metadata, date and time, referring and requested URLs, browser and device type, operating system, language, approximate location inferred from IP, cookie or session identifiers, performance diagnostics, and security logs.
• Video interaction data. A YouTube player is loaded only after a visitor selects play. YouTube then receives the IP address, browser/device details, the page and video requested, and interaction data under Google’s own terms. A YouTube-hosted thumbnail may be requested before play, which can reveal ordinary request data such as an IP address, but the embedded player is not loaded then.

Data comes directly from users; from their browser or device; from Clerk and other providers used to sign in or run a selected app; from payment, AI, and integration providers identified by that app; and from security or hosting systems that generate operational records. If someone supplies data about another person, they should have a lawful basis to do so and direct that person to the relevant notice.

• An email address and authentication data are required to create or use an account where sign-in is enabled. Without them, account-only features and cross-app access cannot be provided.
• An email address and message are required for the portal contact form so the enquiry can be understood and answered. The opportunity type has a default value and helps route the enquiry.
• Fields marked required in a linked app are needed to provide the requested feature, complete a transaction, satisfy security or legal checks, or administer an account. If they are omitted, that feature or transaction may not work. Other profile fields, integrations, feedback, and marketing choices are voluntary unless the app says otherwise.
• Browser controls can block strictly necessary cookies, but sign-in, fraud prevention, and account features may then fail. A visitor can decline to play an embedded YouTube video and use the rest of the page.

The grounds below apply where the relevant law requires a lawful basis. More than one ground can apply, and local law may describe the ground differently.

Where processing relies on legitimate interests, those interests are assessed against the nature of the data, reasonable expectations, impact, and available safeguards. Where it relies on consent, consent can be withdrawn prospectively, without affecting processing already lawfully carried out.

Personal data is disclosed only as reasonably needed for the purposes above, subject to appropriate contractual, technical, and organisational controls where required. Recipient classes include:

• Authentication providers: Clerk for account, session, and sign-in services.
• Database and backend providers: Convex where central account, access, tier, or usage features are enabled.
• Communications providers: Resend transmits contact-form email, and Google’s Gmail receives and stores it.
• Infrastructure providers: hosting, content-delivery, domain, monitoring, security, and error-diagnostic providers that process request, device, and operational data.
• Media providers: Google/YouTube after a visitor chooses to play an embedded video, as described above.
• App-specific providers: AI model, storage, analytics, integration, and payment providers identified in the linked app’s notice.
• Professional and institutional recipients: auditors, insurers, accountants, lawyers, and other advisers under duties of confidentiality; courts, regulators, law enforcement, or public authorities where disclosure is reasonably believed to be legally required or necessary to protect rights, safety, and integrity.
• Business-change recipients: a prospective or actual buyer, successor, financing party, or restructuring adviser, subject to confidentiality and applicable law. Users will be notified if a change materially affects how their data is controlled.

Some linked apps may send prompts, files, instructions, or related context to an AI provider and return generated output. The app-specific notice should identify the categories of content and relevant providers, explain any material provider choices, and describe whether content is retained or used for model improvement where applicable.

Do not submit confidential business information, regulated records, special-category or sensitive personal data, another person’s data, or content a user lacks the right to provide unless the app explicitly supports that use and appropriate permissions and safeguards are in place. AI output can be inaccurate, incomplete, or reveal unintended information; it should be reviewed before use or disclosure. Reports of problematic output may be investigated using the relevant prompt, output, account, and technical records where available.

The portal and account-enabled Services may use strictly necessary cookies or browser storage for Clerk authentication, session continuity, security, fraud prevention, and user-requested settings. These technologies are needed for the requested account service and are not used here for cross-context behavioural advertising.

The YouTube embed uses privacy-enhanced mode and is click-to-load: the player and its associated cookies or storage are not loaded until the visitor chooses play. As noted above, a thumbnail image may still generate a normal image request before play. Once the player loads, Google/YouTube may use cookies or similar technologies under its own policies, particularly if the visitor is signed in to Google.

Browser settings can remove or block cookies and storage, but doing so may break sign-in or requested features. If non-essential analytics, personalisation, or advertising technologies are introduced later, this notice will be updated and a consent or opt-out choice will be provided before use where applicable law requires it.

Yee Fei operates from Singapore. Providers and users may be located in other countries, so data can be processed outside the user’s state, province, or country, including in Singapore, the United States, and locations where the relevant provider maintains personnel or systems. Those places may have different privacy laws.

Where required, reasonable steps and recognised transfer mechanisms are used to protect transferred data. Depending on the route and law, these may include adequacy decisions, contractual commitments, Singapore PDPA comparable-protection obligations, the EU Standard Contractual Clauses, the UK International Data Transfer Addendum or Agreement, and supplementary technical or organisational measures. Details of the mechanism relevant to a user may be requested, subject to redaction of confidential and security-sensitive terms.

Data is kept only for as long as reasonably needed for the purposes in this policy, then deleted or de-identified where practicable. No single period applies to every record. Retention decisions consider:

• whether an account or requested service remains active and the data is needed to provide it;
• the amount, nature, and sensitivity of the data and the risk of harm from unauthorised use;
• the time needed to answer an enquiry, provide support, investigate abuse, maintain security, or resolve a dispute;
• legal, tax, accounting, contractual, recordkeeping, limitation-period, and regulatory requirements;
• app settings, user deletion requests, and the retention practices described in an app-specific notice; and
• whether the purpose can instead be met with aggregated or de-identified data.

In practice, account and access records are generally needed while an account is active; app content is tied to the life of the requested feature and applicable app settings; contact correspondence is kept while an enquiry and reasonable follow-up remain relevant; and request, diagnostic, and security logs are kept for an operationally useful period based on security and troubleshooting needs. Transaction and legal records may need to remain longer. Deletion from live systems may not immediately remove restricted backup copies, and limited data may be retained to document a request, prevent fraud, meet law, or establish, exercise, or defend claims.

Reasonable administrative, technical, and organisational measures are used according to the nature of the Service and data. These can include managed authentication, access controls, provider due diligence, encrypted transport, logging, data minimisation, software maintenance, and incident response. Users should protect their sign-in methods, use strong unique credentials, and report suspected misuse.

No internet transmission, software, or storage system is completely secure, so absolute security cannot be promised. If a personal-data breach occurs, it will be investigated, contained, and documented, and affected people and regulators will be notified when and within the time required by applicable law. Notices may describe the event, likely consequences, response measures, and practical protective steps, subject to security and law-enforcement constraints.

Depending on applicable law, a person may have rights to ask for access to or a copy of personal data; correction; deletion; restriction or objection; portability; withdrawal of consent; information about processing and recipients; or review of certain solely automated decisions. A person may also complain to a privacy regulator. These rights are not universal or absolute: identity, legal exceptions, other people’s rights, technical feasibility, and retention duties can affect the response.

Submit a request using the contact in section 1 and state the country or region, relevant Service, account email, right being exercised, and enough detail to locate the data. To protect users, reasonable verification may be requested—for example, signing in, replying from the account email, confirming recent non-sensitive account details, or providing limited additional evidence. Identity documents should not be sent unless specifically requested through an appropriate channel. An authorised agent may be asked for proof of authority and the user may be asked to verify directly, where allowed.

Requests will be answered within the period and without a fee required by applicable law. A reasonable fee or refusal may apply to manifestly unfounded, excessive, repetitive, or legally exempt requests where the law permits. If a request is denied, the response will explain the reason and any available internal appeal or regulatory complaint path. To appeal where applicable, reply to the decision with “Privacy appeal” and explain why it should be reconsidered. No one will be unlawfully discriminated against for exercising a privacy right.

The contact form does not by itself enrol a person in marketing. If optional promotional email is offered, it will be sent only as permitted by applicable law and will include a way to unsubscribe. Consent-based marketing can also be stopped by contacting the address in section 1. Opting out of marketing does not stop necessary account, transaction, security, support, or policy messages.

The Services are intended for people aged 18 or older and are not directed to children. Personal data is not knowingly collected from a child through the Services. A parent or guardian who believes a child has provided personal data should contact the address in section 1 so the circumstances can be reviewed and appropriate action taken.

This policy may change as the Services, providers, or law change. The version and effective date at the top will be updated. Material changes will receive additional notice appropriate to their significance—for example, an in-service notice or email where contact details are available and the law requires it. Consent will be requested before a new use where required; continued use will not be treated as consent when consent must be express.

Questions, complaints, rights requests, and requests for information about transfer safeguards can be emailed to yeefei@yooi.me.