Skip to main content

Trust & Policies

Security and responsible disclosure

Last updated: October 3, 2026

Security and responsible disclosure: change log

Every version, newest first.

  1. Current version

    • First published.
· About 2 min read

This page explains how we protect your account and data, what you can do to stay safe, and how to tell us about a security problem.

In short

  • Report a security problem through our privacy request form.
  • Only test your own account, and don’t disrupt the service.
  • Follow the rules in good faith and we won’t take legal action; we credit you if you wish.

A plain-words summary only. The full policy below is what applies.

How we protect your data

  • Every page and API is served over HTTPS (encrypted in transit).
  • Sign-in is handled by a dedicated identity provider. We never see or store your password.
  • Card payments are handled by Stripe. We never see or store your full card number.
  • Staff access is limited to the people who need it for their job, and changes made in our staff tools are logged.
  • The service providers who host or process data for us are bound by contract to protect it, as our Privacy Policy explains.

Staying safe

We will never ask for your password, a sign-in code, or a deposit by email or text. Deposits for a home are paid only as your signed agreement says, to a named trust account. If a message asks you to wire money or change payment details, call (905) 553-8500 before you do anything.

Report a security problem

If you think you've found a security problem on summitly.ca, please tell us through the privacy request form and choose "Report a security problem". Include what you found, where, and the steps to see it. We confirm we got it within 3 business days.

Rules for security research

  • Only test against your own account. Don't access, change or keep anyone else's data. If you reach someone else's data by accident, stop, don't keep it, and tell us.
  • Don't disrupt the service: no denial-of-service, spam, or automated testing that sends large volumes of requests.
  • No social engineering of our staff, agents or clients, and no physical testing of our offices.
  • Give us a reasonable time to fix the problem before you tell anyone else.

If you follow these rules in good faith, we will treat your research as authorised, we won't take legal action against you over it, and we'll credit you when it's fixed if you'd like. We don't run a paid bug bounty.

Version history

    • First published.

Was this policy clear?