Privacy policy
How Maple Verba handles account information, practice responses, recordings and messages, and the choices available to you.
Last updated
At a glance
- Public information pages can be viewed without an account. Signing in and practising involve additional account and response information.
- Speaking practice records your voice. Authorized staff can review permitted submissions; optional external evaluation requires a separate choice.
- Security cookies and browser storage support sign-in, preferences and saving work. Some recovery data can remain on your device after you sign out.
- Cookie-free browser IP/location page measurements run before and after cookie acceptance. Additional cookie-based analytics and advertising cookies require Accept cookies. Eligible public pages can load Google's tag with advertising and analytics consent denied before your choice and after withdrawing consent through Cookie preferences; Google may receive limited signals without cookies. Google ad personalization is disabled.
- Use the Contact us form for privacy questions, access or correction requests, and requests to close an account or remove information.
The service this policy covers
This policy covers the public website and practice application operated under the Maple Verba brand. “We” refers to the service operator. It explains information handling for visitors, learners, authors, evaluators and administrators. For questions about the operator or its responsibilities, use the Contact us form, which is available without signing in.
The application provides independent practice and demo sets. It does not administer official CELPIP, IELTS, TCF or TEF examinations, provide official past papers, or issue official scores or certificates. Our practice history and feedback are learning records, not records held by an official examination provider.
Information collected
The information involved depends on the features you use. Avoid placing identification documents, financial details, health information or other unnecessary sensitive information in responses or messages. Practice prompts can normally be answered using fictional examples.
- Account information: username, name, email address, password hash where applicable, account role, workspace access, subscription assignments, practice targets, last sign-in and recent signed-in activity. Phone number and profile country are optional; authorized administrators can view and export account details.
- Account country: after successful sign-in, the server can use the sign-in IP address with ipwho.is and, when configured, IPinfo to estimate your country. These providers receive the IP for this lookup. A recent permitted visit can supply an already detected country. If the server sees only a private network address and automatic profile country is enabled, your browser can ask ipify for its public IP (without sending account credentials, cookies or a referrer) and send that address to the signed-in account-country endpoint for an approximate lookup. This is separate from optional site analytics; browser reports are never used for authentication, access control or billing. Country, source, lookup state and detection time are kept in your profile; raw IPs are not stored in the account profile. Your automatic country can change at subsequent sign-ins. Choose a country manually in Profile & security to keep your own selection and stop browser country discovery. Estimates may be inaccurate with VPNs or mobile networks, and failures do not prevent sign-in. Administrators can switch off account country lookups separately from site analytics.
- Practice records: selected exams and sections, answers, written responses, voice recordings, transcripts where generated, timing, submission status, results and reviewer feedback. Short practice also saves exercise snapshots, answers, explanations viewed, mistakes and scheduled review dates. Your optional daily plan stores a practice duration, exam date and timezone. Voluntary quality reports store the selected category, related practice or submission and any note you provide; authorized administrators can review and resolve them.
- Administration records: access requests, decisions, assignments, consent choices, notification preferences and audit records of relevant actions.
- Contact information: the name, email address, subject and message you submit, together with inquiry dates and handling status.
- Technical records: network addresses and request information needed for delivery, security, troubleshooting and abuse prevention.
- Consented site analytics: a random browser identifier, visit and page times, source/campaign labels, approximate country, device/browser/OS categories, active-page time and sign-in or practice-launch events. IP addresses and reported user agents are encrypted separately for limited administrator inspection.
Why information is used
Practice reminders: unless you opt out, candidates with an email address can receive one encouragement email after a configurable period without sign-in or signed-in activity (15 days by default). Active use resets that period. Turn reminders off in Profile & security or Notification preferences, or use the unsubscribe link in a reminder. Security and account recovery emails are separate.
We use account information to authenticate users, manage access and maintain profiles. Practice information lets the application save and resume work, enforce session timing, mark objective answers, support permitted review and show progress. Access requests and administrative records support decisions about available workspaces, published exams and feedback.
Messages support responding to inquiries. Technical and audit records support investigating errors, protecting accounts and maintaining service integrity. Progress charts and administrative statistics use application records; they are different from tracking visitors across unrelated websites. Optional uses, particularly external evaluation, are explained separately below.
Website analytics and browser IP/location
The signed-in learning journey records limited action categories such as opening Today or viewing practice feedback, with workspace, record reference and timestamp. This optional telemetry excludes answer text, support notes, staff and configured internal testing accounts, respects DNT/GPC and analytics disablement, and follows the configured analytics retention and reset controls. Saved exercises, plans, mistakes and support requests are separate functional records and are preserved by analytics reset. Learning progress and review queues use those functional records; completing a short exercise does not establish an official score or guarantee a review deadline.
Daily learner-engagement reports count recorded successful sign-ins per account and day, distinguish accounts created that day from existing accounts, and match same-day mock starts and submissions. Sign-in snapshots include device/browser categories derived from the request, without retaining a raw user agent. A background lookup may send the server-observed sign-in IP to ipwho.is and, when configured, IPinfo for approximate country and state/region; only those coarse categories are added to the sign-in snapshot. The temporary lookup payload is encrypted and expires after five minutes; this feature does not retain raw sign-in IPs in the analytics record. These optional analytics respect DNT/GPC, analytics disablement, history retention and analytics reset. Missing historical dimensions remain unknown. These reports do not collect failed passwords or send follow-up emails automatically.
Signed-in learner activity is also used for first-party service analytics and plan-selection support without requiring optional cookie acceptance. We record server-confirmed sign-ins and practice launches, and observed plan-catalogue views, individual plan reviews and checkout attempts with timestamps, the selected plan and a limited entry-point category. Identity comes from the authenticated session, never an IP match or a browser-supplied account ID. Authorised Super Admins can view the learner's existing name, username, email and phone alongside this activity and current billing status, and export a follow-up report. A click is not proof of a payment or of an abandoned purchase. Reports wait at least 24 hours after the latest interest before suggesting follow-up, and exclude later confirmed payments and pending payment reviews. No automated plan-follow-up emails are enabled. New analytics events respect DNT/GPC and exclude staff. Existing saved latest-sign-in timestamps and registered-account counts also support aggregate account statistics, independently of tracking consent. Analytics history follows the configured retention period, up to 730 days; account and billing records retain their separate lifecycles. Older anonymous observations are not retrospectively identified. Contact us about access, correction or removal, or to decline plan-selection follow-ups.
When an eligible public or exam-entry page opens, the browser can contact ipify for its public IP without waiting for Accept cookies. That request omits account credentials and referrers. The server validates the reported address and can send it to ipwho.is, with IPinfo Lite as a fallback, for approximate country, region, city and network details. This cookie-free view stores one page observation with a server timestamp and an allowlisted path. It sets no analytics cookies, uses no persistent browser identifier, derives browser, operating-system and device categories without saving a raw user agent, and groups no browsing sessions. New signed-in observations are associated with the authenticated learner account; anonymous observations have no account association. Campaigns and referrers are not attached. Missing or invalid browser reports remain unavailable; a server address is not substituted. Browser IPs can be fabricated and VPN/proxy results can describe an exit network, so these are not verified identities or precise locations. Staff sessions and DNT/GPC signals are excluded. The same private access, audit and retention limits below apply. Withdrawing cookie-based analytics does not disable this cookie-free collection.
Selecting Accept cookies enables additional cookie-based first-party measurement on this site and the Google Ads and OpenAI advertising measurement described below. Cookie-based measurement stays off until you accept. Separate cookie-free page measurements can operate before and after acceptance. Cookie preferences in the public footer lets you change your choice; a browser Do Not Track or Global Privacy Control signal also keeps collection off. Withdrawing stops future cookie-based collection and removes the analytics browser/visit cookies; it does not automatically erase previously recorded history. Contact the operator about removal requests.
We use these measurements to understand which exam guides and public mocks attract interest, how visitors find the site, whether initially anonymous visits sign in, and which devices need attention. The server records successful sign-ins and practice launches for measured visits. We do not collect passwords, answer text, voice recordings, private page identifiers or arbitrary URL query strings in site analytics. Only source, medium and campaign labels from campaign links are used; referrers are reduced to hostnames.
Analytics history, including estimated location and network categories, is retained for up to 730 days, with a shorter period configurable by the operator, and pruned by a daily task. Encrypted IP addresses and user agents are available to Super Admins for up to 30 days or a shorter configured period, then expire and are cleared by that task. Viewing visit details is audited. For cookie-free browser-IP measurements and accepted visit analytics, the server may send the relevant public IP to ipwho.is over HTTPS for estimated continent, country, region/state, city, postal area, latitude/longitude, time zone, ISP and network organisation/ASN information. IPinfo Lite is the backup for country and basic network information. Neither provider receives your account, page history, user agent, answers or recordings from this lookup. Derived results are cached for up to one hour under hashed keys. The Cookie policy links both providers' privacy policies and explains the fresh choice for this expanded integration. These are IP-based estimates rather than GPS readings or a visitor's exact address. VPNs, mobile networks, gateways and privacy tools can reduce accuracy. Network names identify an IP network rather than your employer. Distinct visitors estimate browsers rather than individual people.
Optional analytics can also make a direct browser request to ipify to discover a public IPv4 or IPv6 address when a LAN, VPN or router hides it from the server. This request begins only after the current cookie choice is accepted. ipify receives ordinary connection metadata; credentials and page referrers are omitted, and we send no account, page history or practice content. Results are temporarily cached in browser memory, and withdrawal aborts discovery and clears that cache. The server validates a browser-reported public IP and uses it only as a fallback for a non-public observed address. Such addresses are labelled and not independently verified; they do not grant access, identify an account or control billing. The same network-detail encryption and retention limits apply. The Cookie policy explains this integration and links the ipify API and privacy statement.
Our first-party dashboard does not import Google Ads spending or session recordings. Staff browsing is excluded from site-traffic reports. Google Ads measurement is a separate optional integration described below. Existing security logs, necessary cookies and practice records have their separate purposes described in this policy.
Optional Google Ads measurement
We advertise the service through Google Ads. Eligible public pages load Google's tag AW-672579736 using advanced Consent Mode v2 with advertising and analytics consent denied before your choice and after withdrawing consent through Cookie preferences. Google receives network/browser metadata and may receive limited signals without cookies. Advertising cookies and application page-view events require Accept cookies; accepted page events can include public page addresses and permitted campaign/ad-click identifiers. DNT/GPC and staff sessions do not initialize the tag. Google Ads page events exclude private routes except for a single consented registration completion event. We do not configure account identifiers, email addresses, passwords, practice answers or recordings as tag data. Google Analytics 4 is a separate optional destination described below; no contact or purchase conversion events are configured.
If you have accepted optional measurement when a new email or Google account is successfully created, a session-bound confirmation can send one Completed Registration conversion to Google Ads. Eligibility expires after 15 minutes and consent/privacy signals are checked again before sending. The event uses a random duplicate-protection identifier, a generic signup-completion location and value zero. It does not include your identity or practice data. Existing-account sign-ins, password resets, account linking and signup-page visits do not generate registration conversions. Essential-only registrations are not later backfilled. Browser restrictions can prevent delivery; a conversion does not represent a purchase.
The tag can use first-party _gcl_ cookies for ad-click attribution. Ad personalization and enhanced conversions are disabled. Google handles received data under its own privacy policy and advertising terms, and may process it outside your country. Google's retention is separate from the operator's site-analytics retention and deletion tools. The Cookie policy links Google's privacy, partner-site information and cookie inventory.
Leaving the notice unaccepted keeps Google's consent signals denied; browser privacy signals prevent tag loading. Withdrawing through Cookie preferences stops our page-event calls and removes accessible first-party Google ad cookies. Eligible pages can still load Google's tag with consent denied and limited cookieless signals. This does not erase information Google already received or cookies on Google's domains. Earlier first-party-only analytics choices are not treated as advertising consent.
Optional Google Analytics 4 measurement
The production website uses Google Analytics 4 measurement ID G-F7ZGLBV6W1 through the same Google tag loader as Google Ads. The tag is installed on public and learner application pages. All consent signals start denied; Accept cookies enables analytics storage and our page-view events. Staff sessions, administrator screens, survey links and browser Do Not Track or Global Privacy Control signals are excluded. Before acceptance or after withdrawal, Google can receive limited connection and consent signals without analytics cookies.
Our page-view events use public page addresses or grouped learner screen names such as /workspace/ielts/results. The application removes private URL queries and account, payment, attempt and result identifiers from these event addresses, uses a generic page title, and limits referrers to their origin. It does not configure names, email addresses, passwords, answers, recordings or receipt contents as GA4 event data. Automatic Enhanced measurement is controlled separately in the Google Analytics property and must be disabled by the operator when using these manually controlled page events.
GA4 can use first-party cookies named _ga and _ga_ followed by the stream identifier. This integration requests the exact site hostname and a 90-day lifetime. Cookie preferences withdraws analytics consent, stops our page events and removes accessible GA4 cookies on this site. Google Signals and advertising personalization are disabled. Google processes received data under its own terms and privacy policy; its retention and deletion settings are separate from this application's Site Analytics controls.
Optional OpenAI advertising measurement
Accept cookies also permits OpenAI advertising measurement on eligible public pages and a registration_completed event for a successfully created account. Its pixel loads only after acceptance. Browser and server use one random event identifier for duplicate protection. Existing logins, Google linking, practice activity, staff sessions and essential-only registrations do not generate this conversion. Browser privacy signals keep collection off.
The browser SDK receives connection information and the current page address. The server sends a generic signup-completion address, event time and any consented opaque ad-click or browser references. It does not manually send email addresses, names, IP addresses, passwords or practice content for matching. OpenAI's SDK may perform automatic advanced matching if enabled in Ads Manager; that optional account setting can hash recognised contact fields. Events request an opt-out from future advertising personalisation. The Cookie policy describes browser storage, delivery retries and withdrawal limits.
Pending server payloads are encrypted, expire after six days and are cleared after successful delivery or cancellation. Delivery records expire after 30 days; backups have separate retention. Withdrawal requests cancellation of pending delivery but cannot recall an in-flight request or erase data OpenAI already received. OpenAI's processing and retention are separate from the operator's analytics controls and may involve processing outside your country.
UPI payments and receipt review
For UPI purchases in INR, Miogenlogic Private Limited collects the amount shown at checkout. Payment requests are tied to your signed-in account and the purchased plan. Submitted receipt images and bank confirmation text are stored privately with encryption at rest and are available to authorized administrators for reconciliation. Do not submit PINs, OTPs, passwords, account balances or unrelated transactions.
We may send the receipt image or confirmation text to OpenAI using the platform’s configured API service to extract the amount, recipient, transaction reference and payment status. This operational processing assists human payment review and is separate from optional advertising measurement. AI extraction cannot verify receipt of funds in a bank account. Administrators receive an operational notification and email identifying the purchaser, plan and amount; receipt contents are viewed within the authenticated application.
When provisional access is enabled, confirming that you have paid activates the purchased plan pending bank reconciliation. Receipt uploads are optional by default. A unique order note is included in the payment QR to assist matching, though bank statements may omit it. Full approval depends on payment being received. Administrators may revoke the access associated with an unconfirmed payment. The original plan duration and used allowance continue during reconciliation. Contact support to correct a payment or ask about payment-record retention; accounting obligations and backup retention may limit immediate deletion.
Password and Google sign-in
Where a password is used, the application stores a password hash rather than the readable password. Administrators may provision accounts. If Google sign-up or account linking is enabled and you choose it, Google supplies a verified identity identifier, email address and available profile details such as name and picture URL. We use these to create, connect or authenticate your account.
If email account creation is enabled, you verify your email using a one-time code before entering your first and last name, password and practice preferences. An account is created only after you confirm the final step. Password recovery also verifies your email with a code before updating your password and ending previous sessions. Verification codes and security notices are processed by the configured email service.
Google receives information involved in the sign-in interaction under its own privacy terms. Displaying a Google profile image can also make a request to Google's image servers. Disconnecting Google in Profile requires an alternative password and removes the application's identity connection; it does not delete your Google account or existing practice history.
Cookies and information on your device
Session and anti-forgery cookies support sign-in and secure requests. Local storage remembers sidebar preferences and your cookie choice. Only selecting Accept cookies enables optional site analytics; leaving the notice unaccepted or simply reading a policy does not. Browser databases can hold writing drafts, answers and queued audio while saving or recovering from an interrupted connection. The Cookie policy explains these mechanisms in more detail.
Signing out does not necessarily erase every locally stored draft or recovery item. Successful uploads remove their queued items, but some recovery data has no automatic expiry. Use a private, trusted device, sign out when finished and clear this site's browser data when appropriate. Clearing storage before uploads finish can permanently lose unsaved work; it does not delete copies already saved on the server.
Microphone access and recordings
Microphone access is requested only for Speaking practice. Listening, Reading and Writing do not require microphone permission. Your Speaking preparation timer starts after microphone setup. Speaking response windows can begin recording automatically as the exercise advances. Recordings are uploaded in segments and associated with the relevant attempt. The application does not require camera access.
Your voice, background conversations and details you mention can identify you or other people. Choose a quiet, private location and avoid recording others without appropriate permission. The current application has no voiceprint identification feature. Optional local speech transcription converts a recording into text; a transcript is not a reliable assessment of pronunciation or a guarantee of accuracy.
Required processing and optional choices
Public browsing does not require a practice account. Starting an exam requires the displayed practice rules and confirmation that responses and recordings may be saved. Browser microphone permission is a separate technical permission. Optional external evaluation has its own consent choice; accepting general rules or reading this policy does not automatically authorize it.
You may decline optional external evaluation. To ask about withdrawing a previous choice for future processing, contact the operator and identify the relevant attempt. Withdrawal cannot recall material already downloaded, sent to another recipient or included in a completed review. Necessary account and practice processing may continue while you use those features.
External evaluation and optional providers
When authorized through the separate evaluation choice, permitted staff can export written responses and recordings for external review. Export packages omit direct account identifiers, but contain attempt references, task material and response content. A voice or personal statement can still identify someone; removing a name does not make every submission anonymous.
When an authorized author chooses OpenAI exam generation, authored prompt kits and exam instructions are sent to OpenAI using background processing. These requests set store=false, but OpenAI temporarily stores background response data for roughly ten minutes to support status checks. This mode is not Zero Data Retention. Candidate practice reviews use a separate foreground process. Locally saved recovery output is encrypted; failed generation history and repair output follow the administrator's retention setting, with a 30-day default. Minimal spending and request-deduplication records remain after history is removed.
An administrator may also configure an optional HTTPS evaluation service. The connected text service sends task context, writing and available transcripts as text; it does not send audio in that text-only request. Separately, if the platform enables OpenAI AI practice review and you consent on a completed report, your writing and speaking recordings may be sent to OpenAI Platform for transcription and feedback. These requests omit your account name and email, but your answers or voice may identify you. Speaking scores based on transcripts do not assess pronunciation or acoustic fluency. Returned feedback and transcripts are stored privately in encrypted form. API usage and access are controlled by the administrator and your applicable plan. Manual exports can also contain audio. Before opting in, ask which recipient, processing location and retention terms apply. Provider training or reuse practices depend on that recipient's terms and configuration; this policy makes no blanket promise about them.
Who can access information
Learners access their own permitted records. Administrators and authorized authors or evaluators can access information within their roles and permissions to manage access, maintain exams, investigate issues and review submissions. Practice responses are therefore not confidential from all staff operating the service. Contact inquiries are available through the Super Admin inbox and are not published by the contact form.
Hosting, database, storage, email and optional identity or evaluation providers may process relevant information when used. Information may also be handled to comply with applicable legal obligations or address security incidents and disputes. External resources and social links lead to independently operated sites with their own policies.
Notifications and contact messages
In-app notices can report access decisions, scheduled practice, completion and feedback events. Exam-update emails require an administrator-configured mail service and your enabled email category preferences. Verification codes and password-security notices support the account flows you request and do not depend on optional notification preferences. You can review notification choices in your account. Delivered email necessarily exposes its address and message content to the mail services involved.
The public contact form stores an inquiry in the private administrative inbox; submission does not automatically publish it or enroll you in marketing. Archived inquiries remain stored. Optional Google Ads measurement is described above and does not send contact-form contents as tag data. Any materially different marketing use needs an appropriate notice and any consent required for that use.
Security and its limits
Public forms and sign-in use rate limits, browser-bound one-use form checks and short-lived keyed security counters to reduce spam and password/code guessing. Contact and password-recovery forms use a local security question; signup has no visible security question. Repeated failed password logins can require an extra check. These checks run on our server without an external CAPTCHA provider. Security addressing uses the observed connection and explicitly trusted proxies, not an analytics browser IP report. Counter keys use a keyed digest rather than storing an email address or IP in the key; expired security counters are removed by hourly cleanup. Security controls operate independently of optional analytics consent and analytics deletion.
Safeguards include role-based access, password hashing, request protection and encryption of selected stored content, private media and inquiry payloads. This is not end-to-end encryption: authorized application services and permitted staff can access information, and some account details and operational metadata are stored without field-level encryption.
Use HTTPS when accessing a public deployment; local HTTP testing does not provide equivalent transport protection. Downloaded exports, browser storage, recipient systems and backups have separate security considerations. No internet service or device can promise absolute security. Keep credentials private and use Contact us promptly if you suspect unauthorized access, without sending your password.
Retention, deletion and backups
The application has no universal automatic expiry for accounts, practice records or contact inquiries. Retention depends on the record's purpose, the operator's configured processes and applicable obligations. An optional cleanup process can remove older completed CELPIP recordings while retaining metadata; it does not provide automatic deletion of every transcript, exam family, account or inquiry.
Email verification codes expire after ten minutes, and a verified signup must be completed within fifteen minutes. Pending names, password hashes and code material are cleared on completion or by scheduled expiry cleanup. The scheduled process removes expired verification records after one day and older abuse-prevention counters after two days. Clearing a pending signup does not delete a completed account.
Backups and downloaded exports may contain additional copies. Removing a live record does not instantly erase every backup or recipient copy. Contact the operator for the applicable retention arrangements or a deletion request. Any restrictions, necessary continued retention and practical backup limitations should be explained when your request is considered.
Processing locations
Storage and processing locations depend on where the operator hosts the service and which providers it enables. A Canadian exam focus, Canadian spelling or a Canada-related image does not establish Canadian data residency. Google sign-in, email delivery, external evaluation and downloaded review packages may involve processing in other countries. Ask the operator for current provider and location details before submitting information if location is important to your decision.
Your controls and privacy requests
You can edit supported profile details, change a password, manage notification preferences and review available attempts through your account. For access, correction, an available copy of information, account closure, deletion or an objection to processing, use the Contact us form with a clear description of your request. Available rights depend on applicable law and circumstances.
We may need proportionate information to verify your identity before releasing or changing private records. Do not send passwords or identity documents in an initial inquiry. The interface does not currently offer automatic account deletion. If you are dissatisfied with the handling of a concern, you may contact the privacy authority responsible for your circumstances.
Younger users
The current registration flow does not verify age. A parent or guardian should contact the operator before a younger learner supplies personal information or recordings so that appropriate permission and safeguards can be considered. If you believe a child's information was submitted without appropriate authority, use Contact us to request review. Avoid including unnecessary details about the child in the initial message.
Changes and questions
The date above identifies this policy version. Material changes to information handling should be brought to users' attention, with a separate consent request where required. Merely publishing a revised policy does not replace meaningful consent to a new optional purpose. Use the Contact us form for questions about this policy or the Cookie policy and specify “Privacy” as your subject.
Related information
For questions about this policy, contact the team.