práctica
PRÁCTICA · LEGAL

práctica Privacy Policy

Effective date: 2026-11-16

Main changes in this version: section 2 adds subscription and transaction data; section 10 adds retention arrangements for subscription transaction data; and section 13 updates the payment information. This policy describes the data processing needed to load personal subscription options, prepare or process purchases, restore purchases and handle store notifications. Publishing this policy does not itself initiate a purchase or create a charge.

The Traditional Chinese version of this Policy prevails. Other language versions are provided for reference only; in case of any discrepancy, the Traditional Chinese version governs.

1. Who we are

práctica is operated by A&J EDUCATION TECHNOLOGY LIMITED ("we", "us").

This Policy explains how we collect, use, share, retain and delete the personal data of students, teachers, parents and legal guardians.

Privacy contact email: practica.support@gmail.com
WhatsApp: +852 9034 9107

The service was previously provided by an individual operator. From 14 October 2026 it is operated by the company named above. The handover does not change the purposes or scope of data use; if anything changes later, we will give notice as required by law.

2. What we collect and why

Account and relationship data

We process email addresses, display names, account roles, sign-in verification data, an irreversible hash of the device PIN, and language preference, in order to create, identify and protect accounts and to provide the interface and notifications in the right language.

Teacher data includes the instruments they teach and the T code used at registration. Parent data includes the surname or form of address they enter. We do not require a phone number in order to create a parent account.

We also record the issuing, use and linking of T codes, S codes and P codes, in order to establish and manage permissions between teachers, students and parents.

To handle registration and authorisation for minor students, we record the version of the declaration text shown at the time, when it was accepted, and the relationship to the student. We also record the age band the student reported (under 18, or 18 or older), the source, text version and time of that record, and the parent permission state and times for sending content to a teacher. We do not collect dates of birth, and we do not collect identity documents.

Practice and teaching data

We process:

This data is used to provide practice records, assignments, teaching feedback, progress tracking and learning encouragement.

Subscription and transaction data

When you or your parent view personal subscription options, prepare or initiate a subscription purchase or restore purchases, or when we check a subscription or handle store notifications, we process the following subscription-related data as needed for that operation: which student the subscription is for, which account pays, the purchase platform, store product and plan identifiers, the subscription status reported by the store, automatic renewal status, the current charge and renewal price and their currency, any free trial, billing period and expiry dates, any refund or revocation date, store transaction identifiers, and the early-bird pricing eligibility record we keep for each student.

When we receive a subscription notification from a store, we record its identifier, type, processing result and a hash of its content. We do not keep the original notification or the full receipt.

Where a purchase does not result in an active subscription (for example verification was not completed, the store did not confirm it, the purchase was cancelled, or the receipt was invalid), we still process and keep the records needed to reconcile that attempt, so that we can avoid double charging, check subscription status, and handle refund or dispute queries.

Notification, support and technical data

We process device push tokens in order to send practice reminders, teacher feedback and child activity notifications. Push messages are relayed by Expo's push service and then delivered by each platform's official push service: Google's Firebase Cloud Messaging for Android devices, and the Apple Push Notification service for Apple devices. Those services process the device push token and the notification content. You can manage notification permission in your device settings.

When you contact support, we process the contact details, description and attachments you provide, in order to answer your query or handle your request.

We use error reports to diagnose faults. An error report carries our internal account identifier (a random string), the account role, the app version and device environment data, so that we can locate the problem. We do not deliberately send practice audio or video, or their contents, into error reports. Error reports are data that can identify an individual account, and we do not describe them as anonymous.

We also record the app version, interface language, device time zone, and the country, region or city inferred from network information, in order to understand where and on which versions the app is used. These usage records are associated with an account.

Usage records do not store full IP addresses, and do not store the browser or device user-agent string. To infer country, region or city, we send ipinfo only the network prefix of the IP address (the first 24 bits for IPv4, or the first 48 bits for IPv6), and we store only the country, region and city returned.

To prevent brute-force attempts, the per-minute attempt counters for linking-code lookups and for reviewer sign-in are keyed on the source IP address or the email address. These counters currently have no automatic expiry.

Our cloud, network and error reporting providers may keep access logs that include full IP addresses, under their own arrangements. Those logs are handled under each provider's own policy and are not held in our business database.

3. Required data, optional data, and our legal bases

Creating an account and using certain features requires the corresponding data. For example, recording is not possible without microphone permission, and a teacher cannot give feedback on practice content that is not provided.

We explain at the point of collection which data is required and which is optional, and what happens if it is not provided. We do not ask for data beyond what the relevant feature reasonably needs.

Under applicable law, we process data on the basis of valid consent, processing necessary to perform a valid contract, legal obligations, or another applicable lawful basis.

Accepting this Policy is not the same as having consented to every purpose. Where applicable law requires separate consent for a processing activity, we will explain it and ask for consent before that processing begins.

4. Recording and device permissions

Practice recording is started by the student. The app does not record practice content in the background. The same applies to practice recording started from the exam pages.

When a teacher uses voice feedback or another recording feature, the teacher must also start it and grant the required permission.

Installing the app does not give us continuing access to the camera or microphone. You can manage permissions in your device settings; withdrawing a permission does not automatically delete content already uploaded.

Assignment images are uploaded only after you select them. We do not read your contacts, and we do not scan your whole photo library or other apps' data in order to provide these features.

Practice content is uploaded over Wi-Fi only by default. Content not yet uploaded may be held on the device; if a recording is interrupted, the part already recorded can be uploaded later.

On the recording screen the app reads the device battery level and available storage, only to show you a prompt on that screen. Neither of these leaves your device.

5. Who can see a student's data

The student

A student can see the practice, recordings, assignments, learning progress and teacher feedback in their own account.

The currently linked teacher

A teacher can see the practice recordings the student chose to send to the teacher, and the recordings submitted for quizzes, and can use repertoire, assignment and exam data to give teaching feedback.

For a practice the student chose to keep to themselves, the teacher can see the practice date and duration, but cannot open the audio or video file.

After a student changes teacher, the new teacher can see that student's past practice content already sent to a teacher, quiz submissions, repertoire, exam lists, and later practice data. The new teacher does not get the previous teacher's private notes.

The currently linked parent

A parent can see:

A parent cannot use the parent account to watch recordings the student kept to themselves, recordings not yet marked, or recordings the teacher has not sent. This applies to the repertoire, assignment and exam pages.

Parent accounts are read-only and cannot record on a child's behalf or edit student data.

Other people and our staff

Other students, teachers and parents who are not authorised cannot see the data described above.

Our staff and the technical service providers we need may process data to the extent necessary to provide the service, handle support, deal with a security incident, or meet a legal obligation, subject to corresponding access and confidentiality limits.

What a parent can see in the app does not limit the right of a guardian, once identity and authority are verified, to ask us for access to, correction of, or deletion of data under applicable law.

6. Linking, unlinking, and exam data

A P code can be used once and is valid for 30 days. In the current version each student can be linked to one parent. A parent can unlink in the app, and the student account is notified.

After unlinking, the former parent loses in-app access to that student's data, but the student's data itself is not deleted as a result.

If the former parent still pays for a subscription for that student, after unlinking they can still view and manage the subscription they pay for (such as its status, price and expiry date), but can no longer see the student's learning data.

After a teacher-student link ends, the former teacher loses access to that student's data. The student can still see the history they have retained.

Exam lists and progress stay with the student account and can be managed by the new teacher after a change of teacher. The system may keep the creator record needed for audit purposes, but that record does not give the former teacher access again.

Students and parents can view exam lists read-only; the related teaching content is edited by the currently linked teacher.

Parent and student contact details are not automatically given to a teacher because of linking. What a teacher can see about a parent is limited to the relationship and form of address shown in the app, and does not include the parent's email address.

7. Children's and minors' data

práctica is intended to be used by children and young people with their parents and teachers involved. An account for a minor student must be created by a parent or legal guardian.

Where applicable law requires guardian consent, we will, before collecting the children's data concerned, explain to the guardian the categories of data, the purposes, the recipients and their rights, and complete the required consent process.

How an adult is involved: the adult who creates an account for a minor student must complete email verification using an email address they can receive codes at, and must make the declaration that they are registering on the student's behalf when the account is created. In addition, before a minor student sends practice content to a teacher, the student's linked parent account must grant permission, which the parent can withdraw at any time. We record the permission state, when it was granted or withdrawn, which parent account gave it, and the version of the explanation shown at that time.

How we tell age apart: when the account is created, or before content is first sent to a teacher, we ask the student to choose, on a screen with no pre-selected option, whether they are under 18 or 18 or older, and we store that choice, its source, the version of the text shown and the time. This is self-reported by the user and is not an age we have verified. We do not collect a date of birth and we do not collect identity documents. A student who has reported being 18 or older decides for themselves whether to send content to a teacher. We ask for this report only once. Where there is no such report, we treat the account as a minor's, which means parent permission is still required. Your rights of access and correction under applicable law are set out in section 12.

Entering an S code or a P code, ticking a parent declaration, or a teacher stating that consent has been obtained, does not automatically replace a verification process required by applicable law.

We do not show advertising to minor users, we do not use third-party advertising networks, and we do not use their personal data for marketing.

A guardian whose identity and lawful authority have been verified can contact us to access, correct or delete their child's data, or to withdraw consent-based processing. We will explain what the withdrawal means for the relevant features and for the student account.

Unlinking or deleting a parent account does not automatically delete the child's account. However, if we receive a valid withdrawal of consent, we will stop the relevant processing as required by law and carry out any necessary restriction or deletion.

If we find that children's data has been collected without the required consent process, we will restrict the processing concerned and complete deletion or other necessary steps as required by law.

8. Advertising, analytics and artificial intelligence

We do not sell personal data, do not provide personal data to advertisers, do not use third-party advertising networks, and do not track your behaviour in other apps or websites for advertising purposes. The app contains no advertising.

We do not collect precise location. Country, region or city level usage statistics are different from precise location tracking; how they are handled is described in section 2.

This service has no artificial intelligence analysis, speech-to-text, content recognition or automatic scoring, and we do not provide your content for the training of artificial intelligence models. If we add such a feature later, we will give notice as required by law before processing begins, and ask for consent separately where that is required.

What this covers is our own product features and our arrangements with our providers. How each provider operates within its own service is governed by its own policy, and we do not make statements on its behalf.

For any new purpose, we will give notice as required by law before processing begins, and ask for consent separately where that is required.

9. Technical service providers and cross-border processing

Under our current arrangements we use the following providers:

ProviderPurposeProcessing location
SupabaseAccount, practice, feedback and other database recordsThe project is located in Singapore (ap-southeast-1)
Cloudflare R2Audio, video and assignment imagesThe bucket location hint is set to Asia-Pacific. A Cloudflare location hint indicates the general region where data is placed, not a specific country
BrevoSending sign-in and verification emailHandled by that provider under its own arrangements; see its privacy policy
ExpoRelaying push notificationsUnited States
Google (Firebase Cloud Messaging)Delivering push notifications to Android devicesHandled by that provider under its own arrangements; see its privacy policy
Apple (Push Notification service)Delivering push notifications to Apple devicesHandled by that provider under its own arrangements; see its privacy policy
SentryError reportingUnited States
ipinfoInferring country, region or city from an IP network prefixUnited States

Data may be stored or processed outside the place where you are. We will put in place the contractual and other safeguards required by applicable law, and we will not treat the use of an overseas provider, or your acceptance of this Policy, as satisfying every cross-border requirement.

We may also disclose data to the extent necessary to comply with applicable law or valid legal process, or to handle a security incident.

10. Retention and deletion

We keep personal data only for as long as is reasonably necessary for the purposes we have explained.

Retention under the current features is as follows:

DataRetention
Files of ordinary practice video and audioDeleted automatically by the storage service 30 days after upload. The date, duration and other records of that practice stay in the account until the account is deleted
Video and audio that has been submitted as an assignment, marked, or savedNot subject to the 30-day automatic deletion above; kept for as long as is needed to continue providing the learning record. A student can delete an individual practice in their own account; a deletion request made to us covers the whole account
Raw usage recordsDeleted after 90 days, and handled together with account deletion
Daily aggregated usage statisticsKept. These aggregates are grouped by date, role, region, platform and version; where the number of users is small they may still relate to an individual account, so we do not describe them as anonymous
Handling of a deletion requestCompleted within 30 days of receiving the request
The contact email and the reason you give in a deletion requestCleared 180 days after the day we receive the request
The handling record of a deletion requestCleared 180 days after the day the case is closed
Database backupsOverwritten as backups rotate. Deleted data may still exist in backup copies until those backups are overwritten. We do not restore deleted accounts from backups
Accounting records for a subscription (amount, currency, date, purchase platform and our internal transaction record number)Kept in line with the retention requirements that apply to business records, generally 7 years. This does not cover store purchase tokens or the original notifications
Store identifiers needed to reconcile a subscription (store transaction identifiers, purchase tokens)Kept for 180 days after that subscription has ended and any related refund or dispute has been resolved, and then removed. While a subscription or a dispute is still being handled, we keep only the data needed to handle it

Deleting an individual practice: a student can delete that practice in their own account. No request to us is needed.

Deleting the whole account: you can request this in the app under Me → Account settings → Request account deletion, or on this public page: https://practica-site.practica-support.workers.dev/en/delete-account

A deletion request made to us covers the whole account and its related personal data, not a single piece of content that was already shared. If you only want a particular item removed and cannot do it yourself, contact practica.support@gmail.com and we will handle it manually after verifying identity and authority.

Where the law requires us to keep certain records, we will explain the reason, the scope and the period, and will limit the use of those records.

Subscription and transaction records: after an account is deleted, we remove the account links from the transaction record, so that it no longer points to a particular payer or student, but we keep the record of the transaction itself as set out in the table above, because payment, a refund or a dispute may still be in progress on the store's side. Once the store identifiers have been removed, a later refund or dispute query may need the store's help before it can be reconciled. The removal of the account links described above and the clean-up of the store identifiers are carried out within the periods set out in the table above; that clean-up may be run automatically on those periods or carried out by us manually.

Parent and student accounts are independent, and deleting one does not automatically delete the other. Personal data and content belonging to a deleted account does not gain a permanent retention exception merely because it was once shown to another account.

Unlinking does not by itself delete data. Data may also be deleted because a retention period ends, because a student deletes an individual item themselves, or for another lawful reason, not only because an account is deleted.

Each provider's own access logs or backups are handled under its own arrangements, and we make no commitment about their retention periods.

11. Data security

Under our current technical arrangements we use encryption in transit, PIN hashing, row-level access control in the database, time-limited signed links for media files, and rate limiting on linking-code lookups, to reduce unauthorised access.

Recordings are not published. Media files have no publicly accessible URL; playback always requires a server-side permission check before a time-limited link is issued.

Access by providers and by our own staff is limited to what is necessary to provide the service, handle support, deal with a security incident, or meet a legal obligation.

No system can guarantee absolute security. If a data incident occurs that must be reported under applicable law, we will notify the competent authority and the people affected as required.

12. Your rights and how to contact us

Under applicable law you may have rights to access, obtain a copy of, correct, delete, restrict the processing of, object to the processing of, port, and withdraw consent to the use of your data.

We provide in-app account deletion and a public deletion request page: https://practica-site.practica-support.workers.dev/en/delete-account

That service feature and your statutory data rights in different places apply separately.

To exercise your rights, please contact practica.support@gmail.com. We may ask for reasonably necessary proof of identity or guardianship, so that data is not given to someone who is not authorised.

We will act within the period required by applicable law, and we aim to reply within 30 days as a service standard. If we need longer and the law allows it, we will explain why and when to expect a reply.

You can also complain to the data protection authority that applies to you.

13. Payments and changes to this Policy

The following explains how data related to subscription payments is handled. Simply viewing subscription options does not result in a charge. However, we may create or update records needed to retrieve the applicable options, prepare a purchase, restore purchases or check subscription status before you confirm a purchase in the store, including when you ultimately do not make a purchase.

Subscription payments are handled by the Apple App Store or Google Play. We do not see or store your credit card or other payment card details.

To provide and verify each student's subscription entitlement, we obtain from that store and keep transaction data relating to the subscription (see "Subscription and transaction data" in section 2). We use it to decide whether learning features are available, show subscription status, handle duplicate payments and refund queries, and meet legal requirements.

We will tell you about material changes to this Policy through in-app notice, email or another appropriate method. Where a new purpose requires consent under the law, we will ask for consent before processing begins.

Terms of Use: https://practica-site.practica-support.workers.dev/en/terms

Contact us:

A&J EDUCATION TECHNOLOGY LIMITED
Email: practica.support@gmail.com
WhatsApp: +852 9034 9107