1. Who we are and how to contact us
LingoTab.com is operated by 18361193 Canada Incorporated, a Canadian company responsible for the personal information described in this policy. In jurisdictions using the term, that entity is the data controller for the processing described in this policy.
Our Privacy Officer handles privacy questions, access and correction requests, deletion requests and complaints. Contact details appear in the contact panel at the end of this policy. Send privacy requests to [email protected], marked for the Privacy Officer.
This policy covers information handled by LingoTab.com. App stores, payment services and sign-in providers also handle some information for their own purposes under their notices. Their involvement does not remove our responsibility for personal information under our control.
2. An adult learning service
The launch service is intended for people aged 18 or older who also meet any higher applicable minimum age or age-of-majority requirement in our Terms. It is not offered to children or to people below that eligibility age. Parental permission does not create an exception.
If we learn that we have collected information from an ineligible learner, we will investigate, stop inappropriate processing and take steps to close the account and delete information, subject to lawful retention requirements. Please contact our Privacy Officer if you believe this has happened. We do not currently require routine uploads of identity documents; any future age-assurance process will need its own clear notice.
3. Information we collect
The information involved depends on whether you browse, learn as a guest, sign in, use AI or voice features, contact us, or make a purchase. Not every category is collected from every visitor.
| Category | Examples and source |
|---|---|
| Account and sign-in | Email address, display name, account identifier and authentication/session information from you and the enabled sign-in provider. Password-based sign-in is handled through Firebase Authentication; do not send passwords to support. |
| Learning profile and progress | Learning and guidance languages, selected course, learning goals and preferences, chapter and activity records, answers, attempts, review history, points, streaks and learning timestamps, from your choices and activity. |
| AI and translation interactions | Questions, messages, selected text sent for translation, relevant conversation history, lesson context, generated replies, feedback and any resulting transcript. |
| Voice and audio | Microphone recordings or live audio that you choose to submit, transcripts, speech-feedback results, and generated spoken replies. Local replay recordings and uploaded audio have different handling, as section 5 explains. |
| Technical and security information | IP address, browser or app/device information, operating system, session identifiers, request times, errors and usage or abuse-prevention records, as necessary for the service or collected by its providers. |
| Support and communications | Your contact details, message, attachments and information needed to investigate a request. Please remove unrelated personal information from screenshots and attachments. |
| Community, when enabled | Community display name and any supported avatar, chosen languages and topics, group participation, posts and corrections, shared progress fields, milestone posts, challenge activity and reward records. Sharing choices are separate from private learning records. |
| Community safety, when enabled | Reports and reasons, reported content and relevant context, reporter and reported account IDs, block relationships, filter flags, moderator actions, appeals and security records needed to investigate abuse. |
| Purchases, when enabled | Billing contact information, processor or store customer/transaction identifiers, plan, payment status, renewal or cancellation status, receipts, refunds and limited payment-method details supplied by the payment service. |
4. Why we use personal information
We collect information for identified purposes, rather than treating access to the service as permission for unrestricted use. If a new purpose is materially different, we will explain it and obtain consent where required before using information that way.
- Create and authenticate accounts, remember preferences and separate one learner’s records from another’s.
- Provide lessons, exercises, translations, AI explanations, conversation practice and speech feedback that you request.
- Save progress and, where supported and connected, synchronize the relevant records across devices.
- Use learning activity and preferences to offer relevant practice, review and instructional support.
- When enabled, deliver the community features you choose, display posts to their indicated audience, share only progress fields you opt into, support optional challenges and enforce reward caps.
- Filter community content, investigate reports, apply blocks, support human moderation and appeals, and prevent harassment, spam, scams and reward manipulation.
- Manage trials, subscriptions, receipts, cancellations, refunds and access when those payment features are enabled.
- Respond to support and privacy requests, send essential service messages, investigate errors, prevent misuse and protect the service.
- Understand and improve the service using information appropriate to that purpose. New optional analytics, advertising or unrelated AI-training uses require separate assessment and any required notice or consent.
- Meet legal, accounting, tax and regulatory obligations and establish or defend legal claims.
5. Microphone access, recordings and spoken practice
Voice features require microphone permission from your browser or device. Recording begins when you activate the relevant control. You can stop recording and revoke permission in browser or device settings. Declining the microphone limits voice features; available reading, listening and typed activities can still be used.
A recording made only for local replay may remain in browser memory or a temporary app file. When you request transcription, speech feedback or a voice conversation, the feature sends audio to LingoTab.com’s service and/or the relevant provider. Some practice features submit audio automatically when you stop; a live conversation streams audio while connected. Follow the notice beside the recording control.
The current integrations route different voice features to Google or ElevenLabs. Submitted audio can produce a transcript and teaching feedback. Transcripts, feedback and generated spoken replies can remain in learning records or speech caches even when the original microphone audio was processed only for that request. Do not assume that ending a call deletes every related record.
The reviewed teaching implementation does not include voice cloning or voiceprints for identifying learners. Pronunciation feedback is used for language practice, not identity verification or an assessment of health or emotion. Avoid recording other people or submitting sensitive details that are unnecessary for a language exercise.
6. AI tutoring, provider processing and model training
AI requests may contain your question or recording, recent conversation, selected learning and guidance languages, current course, chapter and activity, relevant progress and preferences, and the exercise context needed to explain the lesson. We aim to limit this context to what the feature needs. A provider also receives technical information associated with the request.
Google Gemini is used in the current AI integrations. Google speech services may generate spoken replies. ElevenLabs is used for transcription in some speech features. Providers may process information for service delivery, security, abuse prevention and legal requirements under the applicable contract. Authorized personnel may access information for those purposes; this is not a promise that every interaction is handled only by machines.
Provider training and review rules depend on the service and configuration. Google’s published Gemini terms distinguish paid services from unpaid services: unpaid inputs and outputs may be used for product or model improvement and human review, while its paid-service terms state that prompts and responses are not used to improve Google products, with separate safety logging. LingoTab.com’s production configuration has not yet been verified for this draft.
The reviewed LingoTab.com implementation does not include training a foundation model on learner conversations. We do not represent that all provider processing is training-free. Any optional future use of identifiable interactions for model training beyond delivering the requested service would require a clear explanation and an appropriate legal basis, including separate consent where required.
7. Learning personalization and automated processing
The service may use your answers, attempts, review activity and selected preferences to suggest practice or adapt explanations. AI feedback and pronunciation results can be inaccurate and are learning aids rather than accredited qualifications.
Automated systems may also apply usage allowances, verify access and detect suspicious activity. If you believe a result, restriction or account decision is wrong, contact us for review. This policy does not claim that a human reviews every exercise. Where applicable law provides rights concerning a decision based exclusively on automated processing, you may request the required explanation, make observations and seek human review through the privacy contact.
8. Guest learning, saved progress and device storage
The website uses browser storage, including local storage and IndexedDB, for learning progress, preferences, saved vocabulary and related records. The mobile app uses app storage and protected sign-in storage. Some data remains specific to a browser, device, course or account; not every feature supports cross-device synchronization.
Where a guest-to-account import is offered, the relevant confirmation controls determine which guest progress is linked to the account. Signing out, deleting the app or clearing browser data is not the same as deleting an account or server record. Clearing device data can remove unsynchronized progress that we cannot recover.
Use a separate device profile on a shared device and sign out after use. A saved or signed-in session can expose learning information to another person with access to that device.
9. Cookies and similar technologies
Cookies and local storage help maintain sessions, associate guest activity with the correct learning space and remember preferences. The current reviewed website does not include a verified deployment of third-party advertising pixels or an analytics service. Firebase sign-in and other requested external services have their own storage and technical processing.
| Current website storage | Purpose and duration |
|---|---|
| school_v2_guest cookie | Associates guest activity with a guest identifier. Configured for up to one year unless replaced or cleared sooner. |
| school_v2_account cookie | Authenticates a website session. The current server caps its lifetime at the token’s remaining validity or one hour, whichever is shorter. Signing in again can create a new session. |
| Language preference fallback cookie | Used when browser local storage is unavailable or full. Configured for up to one year. |
| Browser/app storage and Firebase sign-in persistence | Learning data and preferences may remain until removed through available controls or device settings; account and provider copies are separate. Sign-in persistence can last beyond the website session cookie. |
You can manage cookies and storage through browser or device settings. Blocking required sign-in storage can affect account access. We will provide any legally required choice before enabling non-essential tracking; a reference to future advertising in this policy is not consent to activate it.
10. Communications, advertising and analytics
Essential messages may concern account security, requested support, purchases or changes to the service. Optional promotional messages require consent or another valid basis under the applicable rules and must provide an effective unsubscribe option. Opting out of promotions does not stop necessary service messages.
We plan to promote LingoTab.com through advertising services when marketing launches. An advertising platform can process information about an ad view or click under its own notice. This does not mean that LingoTab.com sends it your private tutor messages or recordings.
On-site advertising tags, remarketing, audience uploads, analytics SDKs and conversion tracking are not treated as already enabled by this draft. Before introducing them, we will identify the actual tools, data, purposes and choices, and obtain any required consent. Private learning conversations and recordings are not included in the proposed advertising use.
11. Subscriptions, Apple Pay and app-store purchases
Stripe is planned for website subscription payments. Apple Pay and other supported payment methods may be added after merchant accounts and integrations are ready. Android and Apple app distribution is also planned. Only the options actually presented at checkout will be available.
When enabled, payment services process payment credentials, billing information and transaction information needed to complete and secure a purchase. LingoTab.com may receive a customer or transaction identifier, plan, amount, currency, payment status, limited payment-method details and subscription events. The intended integration sends full card details to the payment provider, rather than storing them in LingoTab.com’s learning database.
Apple Pay is a wallet payment method and is distinct from an Apple App Store in-app purchase. If Apple Pay is offered, Apple, your bank/card network and the processor handle information needed for that method. LingoTab.com does not receive the Face ID or Touch ID biometric information used to authorize a wallet payment.
If subscriptions are offered through Apple App Store or Google Play billing, the store processes the purchase under its own terms and privacy notice. LingoTab.com may receive receipts or purchase tokens, product identifiers and subscription, refund or cancellation status to verify access. Store purchase information is different from receiving your full card number or store-account password. This draft does not assert that store billing is already integrated.
A trial does not require payment information unless its actual signup flow says so. Cancelling a subscription and requesting deletion of personal information are separate actions. Neither this policy nor an app uninstall is a cancellation instruction to a payment provider or store.
12. When information is disclosed
Information is disclosed to the providers needed for the feature you use, not to every provider simply because you visit an informational page. Some providers act on our instructions; payment, store and security providers may also act independently for their own legal or operational purposes.
| Provider or recipient | Role and relevant information |
|---|---|
| Google Firebase Authentication | Sign-in, account verification and security: account identifiers, email/name as supplied, authentication information and technical data. |
| Google Gemini and Google speech services | Requested AI teaching, translation, speech feedback, voice conversation or spoken output: submitted content, relevant learning context and associated technical data. |
| ElevenLabs, for enabled transcription features | Audio submitted for speech recognition and associated request information. Processing of customer content depends on the applicable business arrangement. |
| Stripe; Apple Pay participants; Apple/Google app stores, when enabled | Payment processing, purchase verification, subscription access, fraud prevention and transaction records, as described in section 11. |
| Other community members, when enabled | Your community display name, permitted avatar and posts within the audience shown by the feature, plus only the progress fields or milestones you choose to share. Private answers, mistakes, recordings and Oli conversations are excluded. |
| Authorized community moderators and safety providers, when enabled | Reports, relevant posted content, filter results, block information and limited account/security records needed for safety and appeals. Access is restricted by role; moderation providers must be identified before use. |
| Hosting, database and support providers | Information necessary to operate the chosen infrastructure or answer a request. Exact production suppliers and locations remain to be confirmed before release. |
| Professional advisers, authorities or a transaction successor | Information reasonably necessary for legal/accounting advice, valid legal requirements, protection of rights or a proposed corporate transaction, with appropriate limits and safeguards. |
We do not sell personal information in the reviewed service, and the draft does not authorize sharing private learning content for cross-context behavioural advertising. If future practices would constitute a regulated sale or advertising-related sharing, we must update the notice and provide the required opt-out or consent controls before starting.
We may disclose information at your direction, to comply with lawful requests, protect safety or rights, or in a financing, merger or sale subject to applicable confidentiality and privacy requirements. The planned community will show only the profile information, posts and progress that its visibility controls permit. It does not publish private tutor conversations. Sections 21 and 22 explain the planned sharing and safety arrangements.
13. International processing
LingoTab.com is based in Canada, but using a Canadian company does not mean information stays in Canada. Google states that Firebase Authentication operates from United States data centres. AI, speech, payment and infrastructure providers can process information in other countries in which they or their service providers operate.
Information processed abroad may be accessible to courts, law enforcement or other authorities under that country’s laws. Privacy protections may differ from those where you live. We remain responsible for information under our control as required by applicable law.
Where local law requires a transfer assessment or a particular safeguard, the production arrangement must satisfy it before the transfer occurs. You may request information about the relevant providers, locations and applicable safeguards through our Privacy Officer. This draft does not claim that a particular adequacy decision, standard contract or UK transfer document has already been verified.
14. How long information is kept
Retention depends on the purpose, sensitivity, account status, legal obligations, security needs and whether a request or dispute requires preservation. Information should be deleted or irreversibly anonymized when it is no longer needed, subject to applicable law. Replacing a name with an identifier alone does not make a record anonymous.
The current implementation does not establish one automatic deletion deadline for all records. The following identifies the relevant criteria; it is not a promise that every copy is deleted immediately when a session ends.
| Record | Retention approach and limits |
|---|---|
| Account details and learning records | Kept to operate the account and learning history, then reviewed for deletion when the account closes or the purpose ends, subject to legal or dispute requirements. Some device copies persist until cleared. |
| Submitted microphone audio | Some LingoTab.com routes process input only for a request or live session; the app may retain a local replay file. Provider safety/retention rules are separate. No universal zero-retention guarantee is made. |
| Transcripts, chat and speech feedback | Some chats are session-only; other teaching routes save recent exchanges and learning observations. Relevant records may remain with the account or learning history. |
| Generated audio and caches | Generated spoken replies can be cached or archived beyond the session. If a reply contains personal information, its copies must be considered in access and deletion handling. |
| Support, security, usage and payment records | Kept for the support/security purpose, applicable financial record obligations, fraud prevention or a claim, rather than automatically removed when a subscription is cancelled. |
| Community profiles, posts and shared milestones, when enabled | Kept for participation and the sharing choices you make. Disabling progress sharing removes those fields from community view; existing milestone posts require separate deletion. Account closure includes linked community records, subject to limited lawful retention. |
| Community reports, blocks, moderation and appeals, when enabled | Restricted records may remain after a post is removed or an account closes to resolve a report or appeal, enforce a block, address a safety risk or meet a legal obligation. Retention must be necessary, reviewed and time-limited under the approved schedule. |
| Backups and provider copies | Deletion from active systems does not necessarily remove backups immediately. Backup expiry and vendor deletion rules must also be applied. Retained copies should remain restricted and not be restored to ordinary use without the required deletion controls. |
15. Security
We use safeguards proportionate to the information and risks involved. The reviewed implementation includes account verification, separation of account records, request limits and restricted storage for certain server-side speech files. Production deployment also requires verified secure transport, access controls and appropriate vendor arrangements.
No service or transmission method can be guaranteed completely secure. Protect your sign-in credentials, keep your device updated and notify us if you suspect unauthorized account access. We will assess privacy incidents and make notifications to affected people and regulators where the applicable law requires them.
16. Your privacy choices
Reading this policy is not blanket consent to every optional purpose. We request consent where required and distinguish service delivery from optional marketing, tracking or any future unrelated model-training use.
- Choose whether to use an optional microphone or AI feature, and review its notice before sending content. Required information is needed to deliver the feature you request.
- Change available learning and guidance preferences; keep personal or third-party sensitive information out of practice prompts.
- Revoke microphone access in device/browser settings, sign out on shared devices and manage cookies or app storage.
- When community features open, choose whether to share progress, change that choice, delete your own milestone posts and use reporting or blocking controls. Lesson participation does not require community sharing.
- Unsubscribe from optional marketing. Use any available tracking choices when new optional tools are introduced.
- Ask for access, correction, deletion or other applicable rights through the privacy contact. Withdrawing consent does not undo lawful past processing and may prevent a feature from continuing.
17. Access, correction and account deletion requests
You may ask what personal information we hold, how it has been used or disclosed, and request access or correction. You may also ask to close an account and delete associated personal information, subject to the rights and exceptions that apply where you live. The reviewed account interface does not yet provide a complete self-service account-deletion workflow.
Use the privacy contact shown below, state the request and include the account email or identifier needed to find your records. We may seek proportionate verification before disclosing or deleting information; we will not ask for your password. An authorized agent may need proof of authority where applicable.
We respond within the applicable legal deadline. Canadian PIPEDA access requests ordinarily require a response within 30 calendar days, with only permitted extensions and notice. Other jurisdictions have their own periods, such as the GDPR’s usual one-month response period. We will explain a lawful extension, refusal or retained information and the available complaint route.
Deleting an account can remove progress and personalization. We may retain limited records required by law, to complete a transaction, protect security or handle a dispute. We must address linked authentication, progress, relevant conversation and audio records, community profiles and posts, sharing settings, moderation records subject to lawful exceptions, and provider copies; deleting only the sign-in identity is insufficient. Cancelling charges with a store or payment provider may require a separate step.
18. Additional rights by location
Rights depend on the law that applies; this policy does not waive mandatory local protections or claim that every privacy statute applies to every Canadian business.
- Canada, including Quebec where its law applies: you may have rights to access and correct information, withdraw consent subject to lawful limits, obtain qualifying computerized information in a commonly used technological format, and exercise other rights concerning dissemination or automated decisions. You may complain to the Office of the Privacy Commissioner of Canada or the relevant provincial authority, including Quebec’s Commission d’accès à l’information.
- EEA, United Kingdom and Switzerland, where applicable: rights can include access, rectification, erasure, restriction, portability, withdrawal of consent, objection to legitimate-interest processing and objection to direct marketing. You may complain to your local data protection authority. Representatives or a data protection contact required for those markets must be identified before the relevant launch.
- United States, where applicable: state laws may provide access, correction, deletion, portability and opt-out rights for certain sales, targeted advertising or profiling, as well as an appeal right and protection from unlawful discrimination. The reviewed build does not implement those advertising uses; any future regulated use must include the required controls and recognition of applicable opt-out preference signals.
- Other locations: request the rights available under your local law through the privacy contact. Mandatory local procedures, notices or protections take precedence over inconsistent wording in this policy.
19. Legal bases where required
Where the GDPR or similar rules require a legal basis, the proposed purposes map to the following bases. We do not treat a contract as a basis for unrelated tracking or provider model improvement. Applicable notices must identify the actual basis for the final processing arrangement.
| Purpose | Relevant basis, where applicable |
|---|---|
| Provide the account, learning features and purchases you request | Performance of a contract, or steps you request before entering it, to the extent the processing is necessary. |
| Optional community progress or milestone sharing | Your specific sharing choice and consent where required. Refusing or withdrawing sharing does not remove access to core lessons. Posting a response intentionally shares that response with the audience shown. |
| Community operation and safety | Contract necessity for requested community functions and legitimate interests in proportionate abuse prevention and moderation, where available and after assessment; consent or another basis where required. |
| Optional marketing, non-essential tracking or a separately proposed optional use | Consent where required. It must be possible to refuse or withdraw without being forced to accept an unrelated purpose. |
| Security, prevention of misuse, support, proportionate service improvement and claims | Legitimate interests where available, after assessing necessity and your rights; consent or another basis where required instead. |
| Financial records, regulatory obligations and required disclosures | Compliance with an applicable legal obligation. |
20. App stores, external links and other services
External websites, app stores, wallet providers and optional sign-in services have their own privacy practices. Review the notices for the service you choose. Downloading from a store does not mean that LingoTab.com receives all information the store collects.
Before release, the Apple App Store privacy disclosures and Google Play Data safety declaration must match the actual app, SDKs, voice processing, purchase flows and deletion arrangements. This website policy does not itself complete those store disclosures or create an account-deletion feature.
21. Community profiles posts and optional progress sharing
The first community version is planned for English and Spanish topic groups, including everyday life, work and travel. It will support short posts, questions, friendly corrections, optional milestone sharing and weekly group challenges. It is not yet available. Participation will require a signed-in eligible account and acceptance of the community rules. The following describes the launch design; we will verify the controls and update this policy before opening access.
A community profile uses your chosen display name, any supported avatar and relevant language or topic choices. Posts and corrections are visible to the audience identified by the group or posting control, together with your community identity. The first version is intended for participating members, not public search indexing. We will explain and obtain any required consent before extending visibility outside that audience.
Progress sharing is off by default. You choose which supported details to display: streaks, earned trophies, current chapter and recent learning milestones. These summaries are connected to your account but do not expose the underlying lesson records. Signing in, joining a group or completing a chapter does not consent to sharing. Each milestone post requires your choice; automatic sharing would require a separate opt-in.
Lesson answers, mistakes, detailed assessments, microphone recordings and private Oli conversations stay private from other members. A short practice response you deliberately write as a community post is visible to its chosen audience. Authorized service providers may still process private learning information as described elsewhere in this policy; private from members does not mean never processed for the requested lesson or support.
You can turn progress sharing off without losing your lessons or earned learning rewards. This stops future sharing and removes the selected profile progress fields from community view. Previously created posts, including milestone posts, must be deleted separately. Closing an account includes its community profile and linked posts, subject to necessary retention described in section 14. People who saw content may have copied it; we cannot guarantee removal of copies outside our control.
Optional weekly challenges may record participation, completion and limited reward events to award capped points and prevent duplicate claims. The challenge will explain any shared results before you join; participation is not permission to publish private exercise answers. Community use is optional and does not require uploading contacts, precise location, identity documents or other sensitive details.
Coming soon: mutually accepted practice partners, text chat, voice messages and live conversation are planned for a later phase, not the initial community. Private lesson recordings are not automatically shared with a partner; a voice message you deliberately send is shared with that recipient. Before use, we will explain message content, voice processing, call connection data, recipients, providers, retention, any recording or transcription, and the relevant privacy and safety controls. No live recording or transcription will be enabled without clear notice and any required consent. We make no claim that future messages will have end-to-end encryption. These rules do not authorize undisclosed future processing.
The coming-soon partner finder is planned to support searches by language, nationality or location using profile fields that members choose to make discoverable. Nationality and country or city will be optional, self-declared fields; nationality will not be inferred from language, name or location. The plan does not require precise GPS coordinates, a street address or an uploaded contact list. Members will be able to change or hide discovery fields, turn discoverability off and block unwanted contact. Sharing a profile does not automatically accept a private message or live call. We will confirm the search audience, controls and data handling before the finder opens.
22. Community reporting blocking and moderation
The planned community includes content filtering, Report and Block controls, and a human moderation dashboard. A report may include the post or profile being reported, its surrounding context, the reason, your account ID, the reported account ID, relevant timestamps and supporting details you choose to provide. Blocking stores the account relationship needed to limit interactions. Blocks and reports are not displayed as public progress or profile information.
Automated filters may flag or temporarily hold content. Authorized human moderators can review the relevant posts, reports, safety history and limited technical or account records needed to assess a concern, act and handle an appeal. A community report does not give moderators unrestricted access to every private lesson answer or Oli conversation. Separate support or safety access must be necessary and follow the purposes and safeguards described in this policy.
We do not display reporter identity to the reported member as part of the report. Details of the event may still allow them to infer who reported it, and lawful disclosure may be required. We restrict moderator access and keep records of moderation actions. Relevant information may be disclosed to qualified safety providers or authorities when necessary and lawful; the final provider configuration and processing locations must be confirmed before use.
Moderation may result in a warning, content removal, posting limits, community suspension or account closure. Where lawful and safe, the affected person will receive the relevant reason and a route to human review. Filters can be wrong; requesting a review is permitted. A report, block or appeal is not a guarantee of immediate action or removal, and the service is not an emergency-response channel.
Deleting a post removes it from community view, but limited evidence may be kept in restricted safety records to investigate abuse, resolve an appeal, prevent evasion or meet legal requirements. We must set and enforce purpose-based retention limits rather than retaining all removed content indefinitely. Safety records must also be considered when answering access or deletion requests, with other people’s rights protected.
For support, privacy questions or safety concerns, contact [email protected]. Community reporting and appeal controls will be explained before community access opens.
23. Changes to this policy
We may revise this policy to reflect changes to the service, providers or law. We will update its effective date and provide additional notice of material changes where required. If a change requires new consent, we will request it before the relevant new processing begins; continued use alone is not a substitute for required consent.
Earlier versions will be identified by their version and date. The preparation date on this local draft is not its effective date.
24. Contact our Privacy Officer
For a privacy question, rights request or complaint, contact [email protected] using the details below. You may also contact a competent privacy regulator; you do not lose that right by raising the matter with us first.
- Legal entity
- 18361193 Canada Incorporated
- Privacy Officer
- [Privacy Officer name or position — to be confirmed]
- [email protected]
- Mailing address
- 5200 Finch Avenue East, Toronto, ON M1S 4Z4, Canada
