LasikiewiczEmail protection Trial for $0.50

Home › Privacy

Privacy policy

Last updated: 1 February 2026. Applies to lasikiewicz.com and to the service delivered under the name Lasikiewicz.

This policy is written to sit inside the Personal Information Protection and Electronic Documents Act (PIPEDA) and the ten fair information principles behind it. Where a shorter sentence would have been clearer but less precise, the precise one was kept.

1. Who is responsible

The responsible party is Lasikiewicz, a sole proprietorship in Toronto, Ontario, operated by Mateusz Lasikiewicz. Reachable at hello@lasikiewicz.com or by post at Lasikiewicz, 18 King Street East, Suite 1400, Toronto, ON M5C 1C4, Canada (address to confirm). Enquiries are answered within one business day, and privacy enquiries within thirty days.

2. What is collected, and why

Three groups of data, each with its own purpose. Nothing else is collected, and no field is taken "for later use".

Categories of personal information, examples and purposes
CategoryExamplesWhy
Account data Name, e-mail address, province, postal code for tax, card token and the last four digits To identify you, deliver the setup, issue receipts and calculate HST/GST correctly. Card numbers themselves are held by the processor.
Service data The addresses you ask to manage, aliases created, filter and forwarding rules, the audit document, leak alerts, correspondence These are the service. Without them the audit and the filtering cannot exist.
Technical data Mail metadata in transit through the filter layer (sender, recipient alias, subject, headers, timestamps), site request logs, the consent record Routing, sorting, debugging, and knowing which consent choice applies.

What is deliberately not collected

  • No mail passwords. The service works from rules and forwarding, so credentials are never requested or stored.
  • No mail bodies retained by default. Message content passes through the filter for sorting; only headers and the routing decision are stored for the alias log.
  • No card number. Held by the payment processor.
  • No advertising profiles. Analytics is limited to the Meta Pixel described in the cookie policy, and only after consent.
  • No sale of your data. At any point, to anyone, for advertising or otherwise.

3. Consent and its basis

Consent is explicit for the subscription: it is given on the terms checkbox at checkout and is recorded with a timestamp. It can be withdrawn at any time, though withdrawal ends the service in most cases because the service is the processing of an address.

Marketing e-mail is separate from the service e-mail. Receipts and leak alerts are service messages and are not affected by any marketing opt-out. Marketing consent is never bundled into a pre-ticked box.

Cookie-level consent is handled by the banner, recorded in local storage, and can be changed through "Cookie preferences" in the footer.

4. Retention limits

  • Account and audit data — for the duration of the subscription, then twenty-four months, for the tax and dispute window.
  • Alias log — ninety days of routing metadata, then aggregated to counts and the detail cleared.
  • Correspondence — twenty-four months, as part of the same record.
  • Site logs — fourteen days.
  • Consent record — until the choice is changed or the cookie storage is cleared.

After these periods data is deleted, not archived indefinitely. Deletion follows the retention schedule automatically rather than depending on a manual sweep.

5. Service providers

Everything below is processor-role: they act on instruction and do not use the data for their own purposes.

  • Payment processor (Canadian entity) — card acceptance, tokenisation, receipts.
  • Mail routing and hosting (server in Canada) — the alias layer and forwarding.
  • Transactional mail delivery — the receipt and alert messages themselves.
  • Breach index (public and commercial datasets) — matching an address against known leaks. A third-party index learns that a query was made for the first hex characters of a hash of the address where available.
  • Meta Pixel (Meta Platforms, US/IE) — only if marketing consent is given.

Where a processor stores anything outside Canada — currently the breach index and the pixel — the transfer is disclosed here, a comparable level of protection is required by contract, and a copy of the relevant clause is available on request.

6. Your rights

Under PIPEDA you may, at no charge:

  • Access the personal information held about you, and the meaning of the data in plain terms.
  • Correct anything inaccurate or incomplete.
  • Withdraw consent, and be told the consequence of doing so.
  • Request deletion of anything not needed for the tax window.
  • Withdraw marketing consent without touching the subscription.
  • Ask about transfers abroad and the protection applying to them.

Requests go to hello@lasikiewicz.com with "Privacy" in the subject line. Identity is confirmed by replying from the address on the account — no ID scandals, no notarised copies. Response within thirty days; a reasoned extension is possible once, only where the volume genuinely requires it.

7. Complaints

If something is wrong, write first — most complaints are answered inside a week without a formal step. If that fails, you may complain to the Office of the Privacy Commissioner of Canada:

Office of the Privacy Commissioner of Canada, 30 Victoria Street, Gatineau, QC K1A 1H3 — toll-free 1-800-282-1376, or via the online complaint form at priv.gc.ca.

You may also complain about the handling of a provincial matter to the Office of the Information and Privacy Commissioner of Ontario, and in Quebec to the Commission d'accès à l'information.

8. Security measures

Transport to this site and to the mail layer is TLS, registration requires a tokenised payment processor, access to the operator tools is password-managed with a second factor, and the audit documents sit on a separate store with no public index. Backups are encrypted.

No system is perfect. If a breach creates a real risk of significant harm, the OPC is notified as required and affected clients are contacted with what was exposed and what to change.

9. Children

The service is aimed at adults. Accounts are not created for minors, so the child-consent provisions of PIPEDA are not engaged in normal use. A parent writing for a household address is the account holder for these purposes.

10. Changes

Amendments are dated at the top of this page. A change that widens what is collected is announced by e-mail to active subscribers at least fourteen days before it applies.

This policy sits beside the terms, cookie policy and accessibility statement. Assistance service, not an antivirus.