Citizenship Journey
Privacy policy
Last updated: November 16, 2026
Private data stays private. Only aggregate data is public.
Private citizenship, account and report data entered or loaded into this site will never be monetized, sold, or shared outside of this site, now or in the future. It will not be rented, licensed, traded, or given away, or used for advertising, marketing, commercial profiling, or unrelated research. Necessary operational processing by the service providers described below is distinct from outside disclosure or commercial use of private records.
The only applicant data publicly available is anonymous aggregate data put together using private records whose owners have agreed to the relevant aggregate use. These combined statistics benefit the public and remain subject to the site's privacy safeguards. Individual private records, names, emails, and private explanations are never published.
A permanent commitment to your private data
This protection covers all private citizenship and account information submitted or loaded into the site, including account and contact details, individual application and milestone records, represented applications, document requests, costs, provider names, private explanations, and feedback messages. It applies to existing data and future submissions. The separate, voluntary shop-email signup described below does not authorize marketing with any of these private records.
A future change in ownership, business model, or privacy-policy wording will not authorize the sale, monetization, or outside distribution of these private records. This commitment does not expire. The site owner will not provide private data to advertisers, data brokers, researchers, social-media groups, or other outside recipients.
You may still access and download your own data, choose whether to contribute to public aggregate statistics, and withdraw optional sharing. Necessary hosting, storage, authentication, and explicitly opted-in email delivery remain limited operational uses, not commercial uses of your private data.
What you provide
The form collects your name, verified email, and the application details and milestone dates you choose to submit. Contact information supports account ownership and private report management. Please do not enter identification numbers or document images. A tracking number is accepted only in the private shipment helper described below.
Optional Program Support Unit (PSU) information includes whether an application was transferred, the transfer date, and any reason or reason code provided. Your free-text reason remains private and is never published. With application-timeline sharing enabled, PSU answers can filter aggregate results. Reason-code filter choices require at least five distinct reporting accounts sharing timelines; they are community-reported, not an official IRCC list. Do not enter names, file numbers or sensitive personal details in these fields.
What the public can see
The only applicant data available to the public is anonymous aggregate data compiled from consenting private records: combined counts, distributions, aggregate milestone summaries, and median or average processing intervals. The site does not publish your name, email, individual report, private explanations, or a downloadable list of submissions. Reports are self-reported; observed timings are not predictions or IRCC guarantees.
Who can access your report
You can view and update your own report after verified sign-in. Other applicants cannot view or edit it. The site owner can access stored information to administer the site, but does not share individual records with anyone, including Facebook or Reddit groups, advertisers, or researchers.
Services needed to operate the site
Replit provides hosting and database storage, and Clerk provides account sign-in and verification (and Resend delivers optional email alerts, described below). Google processes photo-finder searches and Anthropic, through Replit AI Integrations, processes consented AI helper requests, both described below. These technical providers process information needed to operate their services. This necessary processing is distinct from the owner distributing or publishing your submission; this policy is not a claim that no service provider handles data.
Site-usage analytics count basic activity and interactions. Applicant names, emails, application details, milestone dates, and account identifiers are not attached to custom analytics events.
Citizenship costs
Every application carries a fixed $75 CAD fee set by the site owner (not a verified government fee quote). Cost entries you add under My report or My documents (label, kind including third-party services, optional private provider name, service category and activities, currency, amounts, document type and issuing country, shipping origin country or region, and how costs are split across your applications) are stored privately with your account. Provider names are never public. Never enter a street address. Document costs are entered on each saved document and linked to that request automatically; the receipt label, provider and contact details stay private and are never public. Cost entries are removed when you delete your main report. Document requests are kept.
Cost sharing is separate from every other consent and is off by default. Only if you opt in, and mark a profile complete, do its totals join anonymous summaries by currency and document type, shown only when at least 5 distinct accounts contribute. Currencies are never converted. Opting in to cost sharing is separate from document-timing sharing: a cost-only opt-in may share coarse document-cost metadata (document type and issuing country) even if your timing opt-in stays off, and a timing opt-in never shares costs. You can withdraw by switching sharing off and saving.
Document requests
If you use My documents, we privately store, linked to your account, the issuing country, province and agency, record type, optional region and issuing authority name, the generation of the document subject (or unknown), the step dates you enter, and whether you opted in to aggregate summaries with the time you consented. Please do not enter personal names, ID numbers, addresses or document contents. We do not handle, receive or store documents, payments or tracking numbers, and we do not contact any agency or submit requests for you.
Individual requests are never public. Sharing is off by default for new reports and managed in your Report → Privacy and sharing section. If you opt in, request dates contribute only to anonymous median and average intervals grouped by country, record type and generation group (G0, later, or unspecified), calculated from each account's own average so every account counts equally. A group or stage appears only when at least 5 different accounts contribute. The private region text and authority name are never used publicly. Turn document sharing off and save your report to withdraw that purpose, or delete an individual request to remove it from future summaries. Timings are self-reported observations, not official authority times or promises. Requests are independent of your application report: deleting a report does not delete them.
Province/state comparisons are a separate optional use, off by default on every document request. They require you to select a standardized Canadian issuing province/territory or US state/DC/territory and check that request's separate jurisdiction-consent box. Existing private regions, country-only timing consent and “select all consents” on your application report do not opt you in. Only that standardized issuing jurisdiction, record type, broad generation group and combined timing statistics can appear; individual dates, requests, private region text and authority names stay private. At least five distinct accounts are required after every grouping/filter and separately for each time interval. Uncheck jurisdiction sharing and save the request to withdraw only this use. Disabling all document timing sharing also withdraws jurisdiction consent and bumps saved versions so an older editor cannot restore it. Re-enabling timing sharing does not automatically opt requests back into province/state comparisons.
Unfinished browser drafts
Unfinished application, document-request and feedback forms are saved in this browser’s local storage, separately for each signed-in account. They are not sent to the site or included in aggregates until you explicitly submit or save. Drafts stay on this device until a successful save or until you choose “Discard unfinished draft”; they do not sync between devices. Someone with access to this device or its browser data may be able to read them, so avoid shared devices or discard drafts before leaving one.
Questions, feedback and feature requests
A private unread-reply indicator works without email alerts. We store which version of a manager reply you opened so the badge stays consistent when you sign in on another device. This state is only for your account: it is not shown to the manager as a read receipt, included in public statistics or sent to analytics. Deleting a message also removes its unread state.
When you use Feedback, we store your message type, subject, message, verified account email, submission time, status and any manager reply. Messages are private to your account and the site manager; they are not published, shared with other applicants, or included in public statistics. Replies appear in your private message history. You or the site manager can delete a message and its reply. Do not include IDs, document images, tracking numbers or other sensitive personal information.
Reply email alerts are optional and off by default for each message, separate from milestone reminders and public-data sharing. If you opt in, Resend processes your verified account email and a generic alert linking to Feedback; your subject, message, reply and application details are not included. We store your choice, consent time and private delivery bookkeeping. Enable or disable alerts beneath your message; enabling them only covers future replies or reply changes, not old replies. Disabling alerts or deleting the message cancels pending alerts; an email already handed to the provider cannot be recalled. Provider acceptance is not a delivery or read receipt.
Optional milestone email reminders
If you opt in on My report, Resend, a necessary opt-in provider, processes your email address and a generic email message. Your subscription, consent and pending delivery bookkeeping are stored privately. Generic emails contain no other person’s individual record and none of your private application details.
An email is queued only for newly recorded milestone activity among applicants with the same application submission date as yours, including the year. At least 5 reports in that submission-date group must have recorded the matching stage, and you must still be waiting for it or a later stage. Participation is voluntary, off by default, and does not backfill past updates. Each email includes an unsubscribe link; mail services supporting one-click unsubscribe can also stop reminders without sign-in. Opting out cancels queued reminders. Deleting your report removes your subscription and private delivery records. Already-sent emails cannot be recalled, and providers manage their own logs and retention. Anonymous sending-limit counters contain no applicant identity. Emails suggest checking eCAS; they are not IRCC status updates or timing predictions. Unsubscribe page
Optional feature-announcement emails
News about site features and invitations requires separate permission; having an account or consenting to another email type is not permission for announcements. Manage your choice under My Report → Privacy & notifications. Resend processes the recipient address and announcement message when an authorized announcement is sent. Announcement permission does not enable ECAS checks or other notifications.
Every feature announcement includes a no-login unsubscribe link and supports mail providers’ one-click unsubscribe. Opening the link shows a confirmation page; confirming stops only announcements for that address. We retain a hashed recipient identifier, the allow/block choice, its update time and any in-site opt-in consent record. The identifier is pseudonymous, not anonymous. For owner-approved mailings, we also retain the campaign, account reference, recipient hash, attempt time and sending outcome to prevent duplicate invitations. The current verified account address is checked again before sending; the campaign records do not store a copy of the email address or applicant details. Suppression remains when an application report is deleted so deletion cannot accidentally restore email permission. It does not change milestone reminders, ECAS checks or notifications, feedback replies, or shop emails. An email already handed to the provider cannot be recalled.
Private comparisons, confirmations and export
When signed in, My report compares your own files with community observations. Comparisons appear only when at least 5 distinct other contributor accounts qualify. They are observations, not forecasts, and the site has no access to IRCC except the optional invite-only status sync described below, for your own connected applications only. You can confirm you are still waiting; this stores only a confirmation time and does not change your dates. You can download a CSV of your own saved report, represented files, documents, costs and allocations. It is sensitive, never public, and contains no other account’s data. Deleting your account data does not remove files you already downloaded; keep them secure.
Milestone-check emails are sent daily (at most once in 24 hours) or weekly (one digest after seven days), as you choose, and only when there is eligible activity. Choosing a frequency does not opt you in.
Application guides, photo finder, shipment helper and AI helper
If your saved report or a represented application lists a Quebec-born ancestor, we show Quebec-specific document guidance. Choosing “Don't show this again” saves an account-linked preference and its update time, so the alert stays dismissed across devices and sign-ins. The guide remains available under Documents. This preference does not change your report, sharing consent or email settings.
The Start your application guide is readable without an account. “I am Canadian now” is hidden until you sign in and explicitly confirm receipt of your own citizenship certificate in My report. We privately save your receipt date and the time you confirmed it, linked to your account; this is your declaration, not an IRCC verification, and is not included in public statistics. Removing the confirmation locks that section again. If you check off guide steps or document reminders, we store the IDs of the items you marked complete, linked to your account. The document-reminder questions (your situation, whether a minor is applying, and whether translations are needed) stay in your browser tab and are not sent or saved. The guides do not collect documents, uploads or identification numbers.
The optional shipment helper writes the carrier, a private tracking number and an optional actual shipping cost to your existing report and private cost ledger. The tracking number is private, linked to your timeline, and never public or included in aggregates. Automatic shipment tracking is not active. Apart from the optional invite-only IRCC status sync described below, the site never asks for IRCC credentials.
The photo business finder sends the ZIP/postal code you type, or your browser location only after you press the location button, to Google to find nearby businesses and draw a map. Google processes these requests under its service terms; we do not control Google’s retention. This site does not store your location, put it in the address bar or analytics, or save results. Listed businesses are not official, approved or guaranteed providers. We retain Google place IDs and, for each signed-in account, the correct or incorrect vote per photo type, to show community counts. These votes are feedback, not endorsements.
The optional AI helper requires sign-in and a separate, initially unchecked consent each session. Your non-identifying question, fixed precheck choices and the current conversation in that tab are sent to Anthropic through Replit AI Integrations to generate an answer. Personal-detail screening on the page and server is best-effort, so do not enter names, dates of birth, addresses, contact details or ID numbers. We do not store transcripts on the server; the conversation lives only in your browser tab and is cleared when you leave or press Clear conversation. Only usage counts needed for rate limits are stored. Your existing applicant data, reports and documents are never fed to the AI helper or used for marketing.
Optional invite-only IRCC status sync
The owner may explicitly start a one-time batch for due, active connections whose users already consented to stored daily checks and still have ECAS access. This uses the same encrypted runner, audit, per-application allowance and sitewide safety limits; it does not reveal lookup details to the owner or enroll anyone. Paused connections and one-time-only users are excluded. We retain internal connection references and non-identifying batch times, counts and result codes. Any emails still require your separate ECAS-email opt-in.
This feature is invitation-only during testing, with public access OFF, and requires separate, initially unchecked consent. Daily connections encrypt the five lookup fields IRCC requires: identification type and number, surname, date of birth and country of birth. Only a masked identifier is displayed. They are never logged, sent to AI or made public. Checks run inside short requests on this website, with database-enforced single-flight claims, spacing and daily limits across all instances. A separate scheduled trigger sends an authenticated empty request; it receives no applicant data and has no database or encryption key. The owner can stop checks and ECAS emails without redeploying. From ECAS results we retain only status, milestone/request dates, check times and success/error codes, plus comparison and consent metadata. We do not retain result snapshots, addresses, applicant names, application descriptions or history sentences. Other events appear only as “Other IRCC update” and their date. Optional owner mapping templates contain only approved vocabulary, remove dates, numbers and everything after “to:”, have no user/application link, and are pruned within the 30-day retention window while the service is running. Matching dates are confirmed without changing them; empty dates may be filled and mismatches require your review. Pause or disconnect at any time. Disconnect deletes the encrypted lookup details and other check-history entries; your saved milestone and request dates remain yours. Withdrawing an invitation pauses its connections and blocks emails.
Instead of daily updates you can choose “Verify once”, with its own initially unchecked consent. The same five fields are held only in this website request's memory and discarded afterward. They are not saved in a database or durable queue; no daily connection or status snapshot is created. Saved outcomes include confirmations, automatically filled milestone dates, conflicts and any choices you make afterward, along with consent and non-identifying comparison counts. A busy or timed-out check does not save your lookup details to retry. The owner sees counts by internal application ID, never your lookup details. Both modes share database-enforced per-application limits and sitewide safeguards. If a crashed request has an uncertain outcome, its quota is not refunded and its application is not checked again before its allowance resets.
ECAS emails have their own explicit opt-in, separate from community and shop emails. The testing daily digest includes non-identifying labels you choose, status, milestone dates and the last check time; it reports failed or missed checks honestly. These limited details are processed by Resend and your email provider only when you opt in to delivery to your verified sign-in address. Names, identification numbers, birth dates and addresses are never included. The owner can switch to generic update-only notices without redeployment. Unsubscribing stops ECAS emails without stopping checks; already-sent messages cannot be recalled and providers control their own retention. One nightly run starts around 3 a.m. US Eastern, with emails due after the user's checks rather than held until morning. Check now joins the next nightly run, while Verify once is a request-only on-demand check. Safety limits, the run window and outages can carry applications to another night; queued and failed checks are described separately. Other site activity can still keep the app or database awake during the day. A public count of confirmed dates requires at least 5 distinct consenting contributors. The feature may not be running. Other community reminders remain suggestions, not IRCC updates.
Per-application ECAS credential protection
Daily connections use a separate random encryption key for each application. AES-256-GCM protects both the lookup details and that key; only the wrapped data key is stored with the ciphertext. Authentication binds the encrypted material to the connection, account and format version. No website page, administrator tool or credential export displays saved lookup details. You may replace them by re-entering all five fields, but cannot retrieve the previous values.
The authorized check runner opens saved credentials only for the check. Setup necessarily handles the details you enter, and an explicitly authorized legacy-format upgrade must briefly decrypt old records before encrypting them in the new format. Key rotation re-wraps data keys without decrypting the lookup payload. These access attempts are recorded using only internal connection IDs, timestamps, fixed purposes and results; the owner sees counts and recent audit entries, never credentials. Access fails closed if the audit cannot be recorded.
Disconnecting or deleting a connection removes its ciphertext and wrapped key from the live database. Older database backups or storage history may retain encrypted copies until their retention periods expire; this is not a promise of immediate destruction of every historical copy. Saved milestone dates remain yours. Keys and temporary buffers are cleared where practical, but JavaScript memory management cannot guarantee physical erasure of every temporary string or process-memory copy.
This protects against ordinary database inspection and viewing through the site, including by an administrator. It cannot prevent a person or infrastructure operator who controls both the running application/master key and database from technically decrypting records. Unattended checks require the server to decrypt. An external key-management service is not currently used.
Separate, optional shop emails
The shop has its own optional signup for Maple Roots products and offers. You must enter an email address yourself, tick an initially unchecked shop-specific consent box, and confirm the link sent to that address before the subscription becomes active. We do not import or prefill account emails, use application details to target merchandise, or treat milestone reminders, feedback alerts, aggregate-sharing consent, or purchases as permission for shop emails.
Resend processes only the address you enter and the confirmation or shop message needed for this separate subscription. We store the address, consent wording version, request and confirmation times, hashed action tokens, and withdrawal time independently of applicant records. Confirmation links expire after 24 hours. Submission or delivery-provider acceptance alone is not a confirmed subscription or proof that an email arrived.
Shop messages must include a shop-specific unsubscribe link. You can also cancel an unconfirmed request using the link in the confirmation email. Opening a link does not change anything until you select the action button. Unsubscribing stops shop messages and cancels pending confirmation without changing your milestone or feedback email preferences. Resubscribing requires fresh confirmation; an older subscription’s link cannot withdraw a later, freshly confirmed subscription. No promotional campaign is sent merely because this signup is available.
Your choices and deletion
Your report has one Privacy and sharing section with separate choices for application timeline aggregates, anonymous document timings, anonymous cost summaries, and milestone-check emails. Optional choices are off for new reports. Select all consents checks every choice, including the required permission to store your private report and the optional email subscription; you may still uncheck individual choices. Nothing changes until you save.
You can save private records without agreeing to public sharing or emails. Turning a sharing choice off and saving excludes those records from that public use, without deleting them. Document and cost sharing choices apply to your existing and future eligible records; incomplete costs and groups below the five-contributor threshold remain excluded. An email unsubscribe takes effect separately and is reflected in your report settings. Previously sent emails or previously published aggregate summaries cannot be recalled.
Participation is voluntary. Sign in and open My report to correct, update, or delete your submission. Deleting a report removes it from the active report database and future aggregate calculations. Account records, security logs, and backups are managed separately by the relevant service providers; report deletion is not a promise of immediate deletion from those systems.