Privacy Policy
Effective date: 3 August 2026 Last updated: 3 August 2026
This Privacy Policy explains how Slash Code Limited collects, holds, processes, uses, discloses, transfers and protects personal data in connection with Motivo and the related websites, applications, communications and services operated by us.
In this Privacy Policy:
- “Slash Code,” “we,” “us” or “our” means Slash Code Limited, a private company limited by shares incorporated in Hong Kong.
- “Service” means Motivo, including our website at https://withmotivo.com, the Motivo application at https://app.withmotivo.com, applications, teacher-matching service, account features, payment services, support services and any related services that link to this Privacy Policy.
- “User” or “you” includes students, parents, guardians, teachers, teacher applicants, website visitors and other individuals who communicate or interact with us.
- “Personal data” means information relating directly or indirectly to an identifiable living individual from which it is practicable for the individual’s identity to be directly or indirectly ascertained.
Slash Code Limited is the data user responsible for personal data processed under this Privacy Policy.
Our contact details are:
Slash Code Limited Address: Redacted for public display Privacy email: privacy@withmotivo.com General support email: support@withmotivo.com
1. Scope of this Privacy Policy
This Privacy Policy applies to personal data that we process in connection with:
- student, parent and guardian accounts;
- teacher accounts and teacher applications;
- teacher identity, qualification and safeguarding verification;
- student–teacher matching requests;
- lesson arrangements and related administration;
- payments, refunds and transaction records;
- mock-exam, performance-review or other recording services;
- customer support, complaints and dispute resolution;
- our websites, applications and technical infrastructure; and
- marketing communications where a person has agreed to receive them.
This Privacy Policy does not govern an independent third-party service merely because it may be linked to or used alongside our Service. For example, a payment provider, social-login provider or external messaging application may process information under its own privacy policy.
We may provide a shorter Personal Information Collection Statement at the point where particular personal data is collected. That statement should be read together with this Privacy Policy.
2. Users under 18
Our Service may be used to arrange music lessons for children and young people.
Where a student is under 18:
- the account and matching request should ordinarily be created and managed by the student’s parent or legal guardian;
- the parent or guardian is responsible for providing the student’s personal data and confirming that they have authority to do so;
- payment and final matching decisions should ordinarily be handled by the parent or guardian;
- we may require the parent or guardian to verify their identity or relationship to the student;
- we may limit direct communications between a teacher and the student or require the parent or guardian to be included in those communications; and
- we will seek to collect only the student information reasonably required to arrange and administer the lessons.
A user must not submit personal data about a child unless the user has the legal authority to provide that information.
Where we reasonably believe that a child has provided personal data without appropriate parental or guardian involvement, we may suspend the relevant account, request confirmation from a parent or guardian, restrict access to the information or delete it where appropriate.
3. Personal data we collect
The personal data we collect depends on how you use the Service.
3.1 Account and contact information
We may collect:
- full name;
- preferred name;
- email address;
- telephone number;
- country or region;
- preferred language;
- account role;
- profile photograph;
- password hash;
- email and telephone verification status;
- social-login provider identifier;
- account creation, login and activity records; and
- communication preferences.
Where you register through Google, Apple or another supported authentication provider, we may receive information such as your name, email address, profile image and provider-specific account identifier. We do not receive the password used for your account with that provider.
3.2 Student and matching information
For a student or parent requesting a teacher, we may collect:
- the student’s name or preferred name;
- age, date of birth or age range;
- instrument or subject;
- current level, qualifications or examination grade;
- learning objectives;
- examination board or examination preparation needs;
- preferred lesson format;
- preferred lesson duration and frequency;
- preferred teaching language;
- availability;
- approximate location, district or preferred lesson area;
- budget or expected lesson rate;
- accessibility, learning-support or accommodation requirements;
- teacher preferences;
- information supplied in free-text descriptions;
- matching history;
- teacher shortlists;
- match acceptance or rejection decisions;
- reasons for declining or requesting clarification; and
- administrative notes concerning the matching request.
We should not normally require a complete residential address during the initial matching stage. A precise lesson address may be collected or disclosed after a match is confirmed and where it is necessary to arrange an in-person lesson.
Information concerning a disability, medical condition, behavioural need or learning accommodation should only be supplied where relevant to the lessons. Where the student is under 18, this information should be supplied by the parent or guardian.
3.3 Parent and guardian information
We may collect:
- full name;
- relationship to the student;
- contact details;
- billing information;
- communication preferences;
- account verification information;
- matching and payment decisions; and
- communications relating to the student or lessons.
3.4 Teacher profile information
For teachers and teacher applicants, we may collect:
- legal and preferred names;
- profile photograph;
- biography;
- instruments and subjects taught;
- specialist teaching areas;
- teaching languages;
- qualifications;
- professional memberships;
- teaching experience;
- examination preparation experience;
- performance experience;
- education and employment history;
- lesson formats and service areas;
- rates;
- availability;
- age groups taught;
- teaching preferences;
- portfolio materials;
- audio, video or other demonstration materials;
- references;
- tax, invoicing or payment information where applicable; and
- public-profile information selected by the teacher.
A teacher’s public or parent-facing profile will not ordinarily contain the teacher’s identity-document number, raw identity documents, private address, internal verification notes or other information that we classify as private.
3.5 Teacher verification information
To assess teacher applications and promote trust and safety, we may collect or review:
- legal name;
- date of birth;
- identity-document type;
- a masked or limited copy of an identity document where reasonably necessary;
- qualification certificates;
- transcripts;
- professional membership evidence;
- proof of teaching or professional experience;
- reference details;
- declarations concerning suitability to teach;
- safeguarding or screening information supplied by the teacher;
- information relating to relevant background-check processes where legally and operationally available;
- verification dates and outcomes;
- records of discrepancies or follow-up requests; and
- internal fraud, impersonation, safeguarding or risk-review notes.
We will seek to collect no more identity information than is reasonably necessary for the relevant verification purpose. We may ask a teacher to mask information that is not required for verification.
Unless required for a dispute, investigation or legal obligation, a raw identity-document image will normally be deleted within 30 days after the relevant verification process is completed. We may retain a limited verification record, such as the type of document reviewed, the date of review, the result and the authorised reviewer.
Identity documents and confidential verification materials will not ordinarily be disclosed to students, parents or other teachers. We may instead display a limited verification status or badge.
A teacher who provides a referee’s personal data must inform the referee that their information has been supplied to us and must have an appropriate basis for doing so.
3.6 Payment and transaction information
Where payments are processed through a third-party payment provider, we may collect or receive:
- customer and payment-account identifiers;
- payment-intent or transaction identifiers;
- payment amount;
- currency;
- payment status;
- invoice details;
- receipt information;
- refund amount and status;
- payment date;
- limited payment-method information, such as card type and last four digits;
- billing name and address where required;
- chargeback or dispute information; and
- fraud-prevention indicators.
Complete card numbers and card security codes are generally submitted directly to the payment provider and are not stored by us.
3.7 Lesson and service administration information
Depending on the features available, we may collect:
- lesson dates and times;
- attendance records;
- cancellation or rescheduling records;
- lesson status;
- teacher and student confirmations;
- trial-lesson outcomes;
- refund or replacement-teacher requests;
- administrative service fees;
- complaints;
- service-quality feedback; and
- information relevant to resolving a disagreement or service issue.
We do not require teachers to provide us with detailed pedagogical notes about a student unless such information is necessary for a specific Service feature or a complaint, safeguarding matter or support request.
3.8 Communications
We may collect communications sent through or in connection with the Service, including:
- support enquiries;
- emails;
- contact-form submissions;
- in-app messages;
- matching clarification messages;
- complaints;
- feedback;
- refund requests;
- records of telephone or video calls where the user has been appropriately informed; and
- communications required for trust, safety, fraud prevention or dispute resolution.
Where users communicate through an independent service such as WhatsApp, Signal, WeChat or another third-party application, that provider will process the communication under its own terms and privacy policy. We do not automatically receive the contents of those communications unless a user submits them to us.
3.9 Recordings and uploaded content
Where we offer mock-exam review, performance feedback or another recording-based service, we may collect:
- audio recordings;
- video recordings;
- photographs;
- performance details;
- examination programme information;
- teacher comments;
- assessment reports;
- playback and access logs; and
- associated technical metadata.
The person uploading a recording must have permission from all identifiable people appearing or speaking in it. For a student under 18, the upload must be authorised by the student’s parent or legal guardian.
Recordings must not contain unrelated personal data, confidential materials or images of other people who have not agreed to the upload.
Unless a longer period is clearly disclosed for a particular service, mock-exam and performance-review recordings will normally be deleted from active systems within 60 days after the review is completed or the review period expires. Residual backup copies may remain temporarily until overwritten or securely deleted through our normal backup cycle.
3.10 Technical, device and usage information
When you access the Service, we may automatically collect:
- IP address;
- browser type and version;
- device type;
- operating system;
- device or browser identifiers;
- language settings;
- time zone;
- approximate location derived from an IP address;
- referring website;
- pages and features accessed;
- dates and times of access;
- application errors;
- server logs;
- session information;
- cookie and similar-technology identifiers;
- security and authentication events; and
- performance and diagnostic information.
3.11 Security and fraud-prevention information
We may collect or generate information concerning:
- verification attempts;
- one-time password requests;
- failed login attempts;
- rate limits;
- account restrictions;
- suspected duplicate or fraudulent accounts;
- suspicious transactions;
- impersonation;
- misuse of identity or qualification documents;
- prohibited scraping or unauthorised access;
- safeguarding concerns; and
- actions taken by authorised administrators.
4. How we collect personal data
We may collect personal data:
- directly from you;
- from a parent or guardian acting for a student;
- from a teacher or teacher applicant;
- from referees or professional contacts;
- from another user involved in a matching request;
- through forms, account settings and uploaded documents;
- through payments and transactions;
- through communications with our support team;
- automatically through the use of our websites and applications;
- from social-login or authentication providers;
- from payment, fraud-prevention, hosting, communication and security providers;
- from publicly available professional sources where verification is reasonably required; and
- where permitted, from professional bodies or verification providers.
We will not use publicly available personal data for an unrelated purpose merely because it is publicly accessible.
5. Why we use personal data
We may use personal data for the following purposes.
5.1 Providing and operating the Service
This includes:
- creating and administering accounts;
- authenticating users;
- verifying email addresses and telephone numbers;
- processing matching requests;
- preparing teacher shortlists;
- contacting teachers about matching opportunities;
- allowing teachers to accept, decline or clarify requests;
- presenting teacher profiles to students or parents;
- confirming matches;
- facilitating lesson arrangements;
- administering payments and refunds;
- providing mock-exam or performance-review services;
- communicating service updates; and
- providing customer support.
5.2 Teacher assessment and verification
This includes:
- reviewing teacher applications;
- verifying identity;
- reviewing qualifications and professional experience;
- contacting referees;
- assessing application completeness;
- detecting false or misleading information;
- conducting appropriate safeguarding and suitability checks;
- issuing or removing verification status; and
- periodically requesting updated information.
Verification status means only that we have completed the checks described by us at the relevant time. It is not a guarantee of a teacher’s future conduct, teaching quality or suitability for every student.
5.3 Trust, safety and safeguarding
This includes:
- preventing fraud, impersonation and account misuse;
- protecting students, parents, teachers and staff;
- reviewing safeguarding reports;
- investigating misconduct;
- enforcing our Terms of Service;
- restricting or suspending accounts;
- preventing unauthorised access;
- preserving evidence relevant to a complaint or dispute; and
- cooperating with lawful regulatory or law-enforcement requests.
5.4 Payments, accounting and business administration
This includes:
- collecting payments;
- processing deposits, service fees and refunds;
- issuing invoices and receipts;
- handling chargebacks;
- reconciling financial records;
- preventing payment fraud;
- maintaining accounting and tax records; and
- obtaining professional advice.
5.5 Service improvement and analytics
This includes:
- understanding how the Service is used;
- diagnosing errors;
- improving usability;
- measuring feature performance;
- developing new features;
- assessing general matching outcomes;
- performing aggregated analysis; and
- conducting internal planning and reporting.
Where reasonably practicable, we use aggregated or de-identified information for analysis.
5.6 Communications
This includes:
- sending verification messages;
- sending security alerts;
- providing matching and booking notifications;
- responding to enquiries;
- communicating policy or service changes;
- requesting information required to complete an application or transaction; and
- sending administrative messages that are necessary to operate the Service.
Users cannot opt out of communications that are strictly necessary to operate an account, complete a requested transaction or protect the security of the Service.
5.7 Direct marketing
Where permitted and where the required consent or indication of no objection has been obtained, we may use your name and contact details to send information about:
- music-learning services;
- teacher-matching services;
- mock-exam and performance-review services;
- events, workshops and courses;
- promotions and service updates; and
- related services offered by Slash Code Limited.
We will identify the types of personal data and classes of services involved when requesting direct-marketing consent.
We will not treat acceptance of our Terms of Service as automatic consent to direct marketing.
You may withdraw your direct-marketing consent or unsubscribe at any time without charge by:
- using the unsubscribe link in a marketing email;
- changing available account preferences; or
- contacting us at privacy@withmotivo.com.
Withdrawing marketing consent will not affect necessary account, security, transaction or service communications.
We do not sell personal data to third parties for their independent direct-marketing use.
5.8 Legal and regulatory purposes
We may use personal data where reasonably necessary to:
- comply with applicable law;
- respond to a court order, warrant, regulator or lawful government request;
- establish, exercise or defend legal claims;
- obtain legal, accounting, insurance or professional advice;
- conduct or respond to an investigation; and
- protect the rights, property or safety of Slash Code, our users or other people.
6. Mandatory and optional information
Some personal data is required in order to:
- create or secure an account;
- verify contact information;
- assess a teacher application;
- submit or process a matching request;
- process a payment;
- comply with a legal requirement; or
- provide a requested feature.
Required fields will normally be identified in the relevant form or collection statement.
Where required personal data is not provided, we may be unable to:
- create or verify the account;
- approve a teacher;
- process a matching request;
- confirm a lesson arrangement;
- process a payment or refund;
- provide a recording review;
- resolve a complaint; or
- provide another requested part of the Service.
Optional information may help us provide a more suitable match or improve the Service, but a user may choose not to provide it.
7. How matching information is disclosed
We aim to disclose matching information progressively rather than disclosing all personal data at the beginning of the matching process.
7.1 Before a teacher responds
A teacher being considered for a request may receive information reasonably necessary to assess the opportunity, such as:
- the student’s age range;
- instrument and level;
- learning goals;
- preferred language;
- approximate district;
- availability;
- lesson format;
- relevant learning requirements; and
- proposed rate or budget.
We will not ordinarily disclose the student’s complete residential address, identity documents, payment information or unrelated personal data at this stage.
7.2 Teacher profile information disclosed to a student or parent
A student or parent may receive:
- the teacher’s profile name;
- photograph;
- biography;
- qualifications;
- teaching experience;
- specialisms;
- languages;
- rates;
- general availability;
- service area;
- verification status; and
- other profile information authorised for disclosure.
We will not ordinarily disclose the teacher’s identity-document copy, complete identity-document number, confidential verification materials, private residential address, internal risk information or private administrative notes.
7.3 After mutual confirmation
After the teacher and student or parent have confirmed the match, we may disclose information reasonably required to arrange the lesson, such as:
- full or preferred names;
- telephone numbers;
- email addresses;
- precise lesson address where relevant;
- agreed lesson details; and
- necessary access or arrival instructions.
Users must only use another user’s information for the agreed lesson arrangement and must not use it for unrelated marketing, harassment, publication, scraping, profiling or other unauthorised purposes.
8. When we disclose personal data
We may disclose personal data to the following classes of recipients.
8.1 Other users
We may disclose information between students, parents and teachers as described in this Privacy Policy and as necessary to operate the matching and lesson service.
8.2 Our personnel
Personal data may be accessed by authorised directors, employees, contractors and administrators who require access for their work and are subject to appropriate confidentiality and access restrictions.
8.3 Service providers
We may engage service providers for:
- website and application hosting;
- cloud infrastructure and storage;
- database services;
- payment processing;
- identity or qualification verification;
- email delivery;
- telephone or SMS delivery;
- social login;
- CAPTCHA and bot prevention;
- fraud detection;
- analytics;
- customer support;
- document management;
- backup and disaster recovery;
- security monitoring;
- accounting;
- legal advice; and
- insurance.
These providers may process personal data only to the extent required to provide their services to us, subject to their contractual obligations and applicable law.
8.4 Professional advisers
We may disclose information to lawyers, accountants, auditors, insurers, consultants and other professional advisers where reasonably necessary.
8.5 Authorities and legal recipients
We may disclose information to a court, regulator, government authority, law-enforcement agency or other person where:
- required or permitted by law;
- necessary to respond to a lawful request;
- necessary to investigate suspected unlawful activity;
- necessary to protect a person from serious harm; or
- necessary to establish, exercise or defend legal rights.
8.6 Corporate transactions
If Slash Code or part of its business is involved in a proposed or completed merger, restructuring, financing, investment, acquisition, sale, transfer or insolvency process, personal data may be disclosed to relevant advisers and counterparties subject to appropriate confidentiality measures.
Any successor that receives personal data will be required to handle it consistently with applicable privacy law and any notices given to users.
9. Payments
Payments may be processed by an independent payment provider such as Stripe or another provider identified during the payment process.
Payment information submitted directly through the provider’s interface is processed under that provider’s privacy terms. We may receive transaction records and limited payment-method information, but we do not ordinarily receive or store the complete payment-card number or card security code.
We may retain payment, invoice, refund and accounting records for the period required for taxation, accounting, fraud prevention, dispute resolution and legal compliance.
10. Cookies and similar technologies
We may use cookies, local storage, pixels, software development kits and similar technologies.
These technologies may be used for:
- account authentication;
- maintaining sessions;
- remembering settings;
- security and fraud prevention;
- load balancing;
- saving user preferences;
- measuring traffic and performance;
- diagnosing errors;
- analytics; and
- marketing, where separately permitted.
Strictly necessary technologies may be used because they are required for the Service to function securely.
Where required by applicable law, non-essential analytics or marketing technologies will not be activated until the required user choice has been obtained.
You may be able to control cookies through your browser or device. Blocking necessary cookies may prevent parts of the Service from working correctly.
Further information may be provided in a separate Cookie Notice.
11. Automated processing and matching decisions
Our teacher-matching process is currently administered by authorised personnel and is not based solely on an automated decision that confirms or rejects a match without human involvement.
We may use software to organise applications, apply filters, detect incomplete information, identify potential fraud, rank administrative work or suggest possible matches. Final matching and teacher-approval decisions may involve human assessment.
If we introduce materially different automated decision-making, we will update this Privacy Policy and provide any additional information required by applicable law.
12. International transfers
Our company is based in Hong Kong, but some service providers, technical systems, personnel or storage facilities may be located in other jurisdictions.
As a result, personal data may be transferred to, accessed from or stored in places outside Hong Kong. Those jurisdictions may have privacy laws that differ from the laws of Hong Kong.
Where we transfer personal data outside Hong Kong, we will take reasonably practicable steps appropriate to the circumstances, which may include:
- conducting service-provider due diligence;
- limiting the data transferred;
- using contractual privacy and security obligations;
- implementing access controls and encryption;
- using recognised data-transfer terms where appropriate; and
- reviewing the recipient’s security arrangements.
Users should not assume that all personal data is stored exclusively in Hong Kong unless we expressly state this for a particular Service.
13. Data retention
We retain personal data only for as long as reasonably necessary for the purposes for which it was collected and for legitimate operational, safety, accounting, dispute-resolution and legal requirements.
Our normal retention periods are set out below. A longer or shorter period may apply where reasonably required by the circumstances or applicable law.
| Record type | Normal retention period |
|---|---|
| Incomplete or unverified account | Up to 30 days after the account becomes inactive |
| Expired one-time verification code | Deleted or rendered unusable after expiry or replacement |
| Authentication and verification logs | Normally up to 12 months |
| Active account information | For the duration of the account |
| Closed account profile information | Normally up to 90 days after closure, except information subject to another retention requirement |
| Rejected or withdrawn teacher application | Normally 12 months after closure |
| Raw identity-document image | Normally deleted within 30 days after verification is completed |
| Limited teacher verification record | While the teacher remains active and normally up to 3 years afterwards |
| Closed matching request | Normally up to 3 years after closure |
| Lesson administration records | Normally up to 3 years after the relevant lesson or match ends |
| Support enquiry | Normally up to 2 years after resolution |
| Complaint, safeguarding report or dispute | For the duration of the matter and an appropriate period afterwards based on legal and safety considerations |
| Mock-exam or performance recording | Normally deleted from active systems within 60 days after completion or expiry of the review |
| Security and fraud investigation records | For as long as reasonably necessary to protect the Service and establish or defend legal claims |
| Payment, invoice, refund and accounting records | Normally at least 7 years where required as business or tax records |
| Marketing preference and opt-out record | For as long as reasonably necessary to respect the user’s preference |
| Server and application logs | Normally between 30 days and 12 months, depending on the log and security purpose |
| Backup copies | Until overwritten or securely removed through the normal backup cycle |
When determining the appropriate retention period, we may consider:
- the nature and sensitivity of the information;
- the purpose for which it was collected;
- whether the purpose can be achieved with aggregated or de-identified data;
- security and fraud risks;
- safeguarding considerations;
- complaint and dispute history;
- limitation periods;
- tax and accounting obligations; and
- legal or regulatory requirements.
When personal data is no longer required, we will take reasonably practicable steps to delete, destroy, anonymise or restrict further use of it.
Account deletion does not necessarily result in immediate deletion of every record. We may retain information required for payments, taxation, fraud prevention, safeguarding, dispute resolution, legal compliance and enforcement of our agreements.
14. Data accuracy
We take reasonably practicable steps to maintain the accuracy of personal data used by us.
Users should keep their account, contact, availability, rate and profile information current. Teachers must promptly notify us if:
- a qualification or professional status has changed;
- information used for verification is no longer accurate;
- a safeguarding declaration becomes inaccurate;
- their contact details change; or
- they are no longer available to provide lessons.
We may request updated documents or re-verification where reasonably necessary.
15. Security
We use technical and organisational measures designed to protect personal data against unauthorised or accidental access, processing, erasure, loss or use.
Depending on the nature of the information and system, these measures may include:
- encrypted transmission;
- password hashing;
- role-based access controls;
- multi-factor authentication for selected administrative functions;
- restricted access to identity documents;
- separation of public-profile and verification information;
- logging and monitoring;
- rate limiting and bot prevention;
- vulnerability and dependency management;
- secure cloud-storage controls;
- backup and recovery processes;
- staff and contractor confidentiality obligations;
- service-provider review; and
- incident-response procedures.
No website, application, transmission or storage system can be guaranteed to be completely secure. Users are responsible for:
- choosing a strong and unique password;
- protecting verification codes;
- securing their email and telephone accounts;
- signing out on shared devices;
- not sharing account credentials; and
- notifying us promptly of suspected unauthorised access.
16. Personal-data incidents
If we become aware of unauthorised access to, loss of or another incident involving personal data, we may:
- investigate the incident;
- contain and remediate it;
- preserve relevant evidence;
- assess the risk to affected individuals;
- notify affected users where appropriate;
- notify the Privacy Commissioner or another authority where appropriate or required; and
- take steps to reduce the risk of recurrence.
Any notification may describe the nature of the incident, the information affected, steps taken by us and recommended protective actions.
17. Your rights and choices
Subject to applicable law and appropriate identity verification, you may contact us to:
- ask whether we hold personal data about you;
- request access to personal data held by us;
- request correction of inaccurate personal data;
- update account information;
- withdraw direct-marketing consent;
- close your account;
- request deletion of information that is no longer required;
- object to or raise concerns about particular processing;
- ask questions about our privacy practices; or
- make a privacy complaint.
These rights are not absolute. We may be required or permitted to retain or withhold certain information, including where it:
- relates to another person;
- is subject to legal privilege;
- must be retained for legal, tax or accounting purposes;
- is required for fraud, safeguarding or security purposes;
- is relevant to a complaint or legal claim; or
- is otherwise exempt from access, correction or deletion under applicable law.
To submit a privacy request, contact:
Privacy contact: SlashCode Limited Email: privacy@withmotivo.com Postal address: Not provided; privacy requests are accepted by email only
We may ask for information reasonably required to verify your identity and locate the relevant records.
Where a formal data-access request is made, we may require the request to be submitted in the form prescribed or recognised under applicable law. We may charge a fee where permitted, but any fee will not be excessive.
We will seek to respond within the period required by applicable law.
If you are dissatisfied with our handling of your personal data, you may contact the Office of the Privacy Commissioner for Personal Data, Hong Kong, or another competent privacy authority where applicable.
18. Closing an account
A user may request account closure through the available account settings or by contacting us.
After receiving a valid closure request, we may:
- disable access to the account;
- remove the public profile;
- cancel outstanding matching requests;
- restrict further processing;
- retain required transaction, dispute, safeguarding and legal records; and
- delete or anonymise other information in accordance with our retention schedule.
Closing an account will not automatically cancel any outstanding payment obligation, refund process, complaint, investigation or confirmed lesson arrangement.
19. Third-party websites and services
The Service may contain links to third-party websites or integrate third-party services.
We are not responsible for the independent privacy practices of those third parties. Users should review the relevant third-party privacy notices before providing information to them.
The presence of a link or integration does not mean that we control the third party’s processing of personal data.
20. Business users and organisations
Where a school, music centre, organisation or other business arranges access to the Service, that organisation may separately determine why and how some personal data is processed.
In such circumstances:
- the organisation may be an independent data user or controller;
- we may process certain information on its instructions;
- the organisation’s own privacy notice may also apply; and
- requests relating to organisation-controlled information may need to be directed to that organisation.
We will provide further information where a specific organisational arrangement applies.
21. Changes to this Privacy Policy
We may amend this Privacy Policy from time to time to reflect:
- changes to the Service;
- new features;
- changes in our processing practices;
- changes to service providers;
- security developments; or
- legal and regulatory requirements.
The updated policy will be published through the Service with a revised “Last updated” date.
Where a change is material, we may provide additional notice through the Service, by email or through another appropriate channel.
Unless otherwise stated, an updated Privacy Policy takes effect on the effective date stated in the updated version. We will seek additional consent where required by applicable law.
22. Language
This Privacy Policy is currently available in English only. We may make it available in more than one language in the future.
If there is an inconsistency between the English version and a translated version, the English version will prevail to the extent permitted by applicable law, unless we expressly state otherwise.
23. Contact us
Questions, privacy requests and complaints may be sent to:
Slash Code Limited Attention: Privacy Officer Address: Redacted for public display Email: privacy@withmotivo.com Support: support@withmotivo.com Website: https://withmotivo.com