This Privacy Policy explains how the organizers of DontBanCryptoATMs.ca operate this website and handle information when you use it.
DontBanCryptoATMs.ca helps Canadians identify their federal Member of Parliament and prepare an email about the proposed federal crypto ATM ban. The website does not send email on your behalf. You choose whether to open your email app, copy the message, edit it, and send it.
1. Information we collect
We collect the minimum information needed to operate the MP lookup tool and protect the website.
Postal code: When you enter a Canadian postal code, we normalize it and use it to identify the federal MP for that riding. We permanently cache postal-code lookup results so we do not repeatedly query public data sources for the same postal code. We also store an aggregate count of how many times each cached postal code has been looked up.
Optional name: You may enter your name so it can appear in the generated email. We do not store the name entered for the email draft unless you separately submit it with an optional testimonial.
Optional personal note: You may enter a personal note so it can appear in the generated email. We do not store your personal note.
Audience type: You may choose whether you are writing as a customer/user, merchant or host location, or Canadian supporter. This may change the suggested email text. We do not store this selection with your personal note, generated email body, completed message, or email address. If UTM data is present, we may store the selected audience type with a lookup-submission attribution record described below. If you submit a testimonial, we may store the selected audience type with that testimonial.
Optional testimonials: If you choose to submit a testimonial, we store the testimonial text you provide, your name if provided, store name if provided for merchants or host locations, selected audience type, normalized postal code if available, language, whether you had clicked copy or open email, lookup outcome, timestamp, and any available UTM parameters. We may use testimonials to support the campaign and put users' words in front of Canadian representatives in person.
Campaign attribution: When you visit the website, we may store a page-load attribution record with a timestamp. If UTM parameters are present, such as utm_source, utm_medium, utm_campaign, utm_term, or utm_content, we may store them with that record; UTM fields are stored as blank when no UTM parameters are provided. Any UTM parameters may also be placed into hidden form fields so they can be carried through a postal-code lookup submission. If you submit a lookup, we may store a separate lookup-submission attribution record with the selected audience type, lookup outcome, timestamp, and any available UTM parameters. If you click "Open email app," we may store an email-app click attribution record with available UTM parameters, the selected audience type, lookup outcome, and timestamp. This lets us understand campaign activity, referral sources, fall-off between UTM-tagged page loads and lookup submissions, and how often users open their email app from the tool. Campaign attribution records do not store postal codes, MP lookup details, your name, personal note, generated email subject or body, completed message, email address, wallet address, or financial information.
Language and approximate region: The site may use region headers supplied by the hosting provider or content delivery network, derived from IP address, to show French by default to visitors who appear to be in Quebec. Other visitors see English by default. You can switch languages at any time. Your language preference may be stored in the site session.
Generated email content: The website may generate an email subject and body for you to review. We may store that the "Open email app" link was clicked, but we do not store the generated email body, completed message, or whether you actually sent the email.
Technical information: Like most websites, our servers, hosting providers, security tools, or analytics tools may process basic technical information such as IP address, browser type, device information, requested page, date/time of request, referring page, and error logs. We use this information to operate, secure, debug, and improve the website. We do not intentionally connect technical logs to your generated message.
Cookies and analytics: The website may use essential cookies if required for security, forms, sessions, or normal site operation. If analytics are used, we use them for aggregate or technical activity and do not store personal message content. Do not enter sensitive information into this website.
2. How we use information
We use information to:
- validate and normalize postal codes;
- identify the appropriate federal MP;
- cache postal-code lookup results;
- count how often a cached postal code is looked up;
- understand campaign attribution and referral sources from UTM-tagged links;
- understand how often users open their email app from the tool;
- collect and organize optional testimonials submitted by users;
- choose a default language and manage language switching;
- generate a mailto link and copy/paste email block;
- display fallback instructions if an MP cannot be found;
- protect, debug, and improve the website;
- understand aggregate campaign activity without storing completed messages.
3. Postal-code caching
We permanently cache normalized postal-code lookup results. This cache may include:
- normalized postal code;
- lookup status;
- federal MP name, riding, party, and email address if available;
- public data returned by the representative lookup provider;
- an aggregate lookup count for that postal code;
- timestamps and administrative review fields.
This cache is not intended to identify individual users. The lookup count is an aggregate count for the postal code, not a user-specific history. We do not store your name, personal note, generated email body, completed message, or email address with the postal-code lookup unless you separately submit some of that information in an optional testimonial.
4. Third-party public data providers
If a normalized postal code has not already been cached, we may send that postal code to OpenNorth Represent API or another public representative lookup source to identify the relevant federal MP.
OpenNorth and other external websites have their own terms and privacy practices. We are not responsible for their practices, content, availability, accuracy, or security.
5. Email apps and mailto links
When you click "Open email app," your browser or device may open your email software with a prefilled recipient, subject, and body. Your email app, email provider, browser, device, and network may process that information. We do not control those services.
You are responsible for reviewing and sending any email. This website does not send the email for you.
6. What we do not collect
We do not intentionally collect or store:
- your completed email message;
- your generated email body;
- your personal note;
- your name, except when you choose to submit it with a testimonial;
- your email address;
- cryptocurrency wallet addresses;
- government identification;
- financial account information;
- payment card information;
- Social Insurance Numbers;
- copies of identity documents.
Do not submit sensitive personal information through this website.
7. Disclosure of information
We may disclose information only as necessary to:
- operate hosting, security, analytics, or technical infrastructure;
- use public representative lookup services;
- comply with legal obligations;
- detect, prevent, or investigate abuse, security incidents, or misuse;
- protect the rights, safety, and security of the website, users, or others.
We do not sell personal information.
8. Retention
Postal-code lookup records, including the aggregate lookup count, are retained permanently by design so the site does not duplicate public API requests.
Campaign attribution records containing UTM parameters, event type, selected audience type, lookup outcome, and timestamp may be retained for campaign reporting, security, debugging, or operational needs. Email-app click attribution records may be retained for the same purposes.
Optional testimonial records, including the testimonial text, name or store name if provided, normalized postal code if available, selected audience type, language, source action, lookup outcome, timestamp, and available UTM parameters may be retained for campaign, reporting, security, debugging, or operational needs.
Optional name, personal note, generated email body, completed email content, and user email address are not retained as part of the email-generation flow unless separately included in a testimonial submission.
Technical logs may be retained for a limited period according to hosting, security, debugging, or operational needs.
9. Safeguards
We use reasonable administrative, technical, and organizational safeguards appropriate to the sensitivity of the information we handle. No website or internet transmission is perfectly secure.
10. Accuracy
MP and riding data may be inaccurate, incomplete, outdated, or affected by postal-code boundary issues. If the result looks wrong, use the official House of Commons MP lookup.
11. Your choices
You can use the House of Commons MP lookup directly instead of using this website.
You can choose not to enter your name or personal note.
You can choose not to submit a testimonial.
You can edit or delete the generated email before sending it.
You can use the language switcher to choose English or French.
12. Access, correction, and questions
DontBanCryptoATMs.ca does not currently publish a direct privacy contact email. If a contact method is added later, it will be posted on this page.
We may need to verify your request before responding. Because we do not store personal notes, generated email bodies, completed messages, or user email addresses, and because testimonial names may be optional or incomplete, we may not have records connected to you.
13. Changes to this policy
We may update this Privacy Policy from time to time. The updated version will be posted on this page with a new "Last updated" date.