Version: 2026-10-11

Effective date: October 11, 2026

The short version

We collect what we need to answer messages, open and secure accounts, provide sites and handle billing. We send product news only when you opt in. We do not sell personal information.

www.keelpage.com has no advertising or third-party analytics. Its page-view counts use no cookies or browser storage. Account and private-site access use the cookies described below.

When you use our contact form

We collect your name, work email, company if you give it, what you need, your message and whether you ticked the product-news box. We also record the time, your browser’s user agent and a keyed fingerprint of your IP address. The fingerprint is made with a secret key; the form record does not store your IP address itself.

We use this to reply and talk with you about your site or the sites you build. Messages are stored in Keel’s inbox and database in Microsoft Azure’s Canadian regions. A copy is emailed to our team through Twilio SendGrid. Our team may also keep the conversation and contact details in HubSpot, our customer-relationship tool, to follow up.

Before the form sends, Cloudflare Turnstile checks your browser to distinguish people from automated scripts. Cloudflare processes the security check under its own privacy policy. We keep contact messages for 24 months by default. Copies in email or HubSpot have separate retention, described below.

When you open an account

We collect your name, email and business or account name. We record the terms version and time you accepted it. We record whether you ticked the news box. If you do, we keep the wording you agreed to, the time and the keyed network-address fingerprint as evidence of consent.

Cloudflare Turnstile runs the sign-up security check. Keel verifies its response token. Keel also uses hashed network addresses to limit sign-up requests: three per email address and ten per network address each hour. These checks protect accounts and reduce abuse.

The sign-up link works once and expires after 60 minutes. The account starts only when the link is successfully used. We use your details to create and manage your account, give you access and contact you about the service.

When you sign in and work on a site

Keel uses email links and passkeys instead of passwords. A sign-in-link request records your email, a safe return path, the time, a keyed address fingerprint, your browser’s user agent and a request identifier. The sign-in link expires after 15 minutes.

If you add a passkey, Keel stores its public credential and account record, including its name and creation time. Your device handles the private key and any fingerprint or face check. Keel does not receive that fingerprint or face data.

We keep account and site roles, invitations, bot and agent approvals, and security and activity records. These can identify who acted, on which site, when, through which kind of access, and what changed. They help us enforce permissions, investigate problems and support you. Microsoft Entra handles Microsoft sign-in for Keel’s system administrators.

Billing through Stripe

Stripe collects card details, billing name and address, and tax details during hosted checkout. Stripe holds card details; Keel does not store card numbers or security codes. We send Stripe your billing email and account and payment-operation identifiers to connect the payment to your account.

Keel keeps your billing email, plan, billing interval, extra sites, joining price group, locked price catalogue, Stripe customer and subscription identifiers, checkout and invoice identifiers, payment amounts and periods, payment status, cancellation and plan-change records, and any refund or dispute review records. Verified payment events retain routing identifiers and status, not the raw card or customer payload. We use these records to provide paid access, reconcile payments, handle billing questions and prevent repeated charges.

Service email and product news

Twilio SendGrid delivers sign-up and sign-in links, invitations, billing messages, form notifications and other service notices. It receives the recipient address and name, message content and message identifier. Keel records delivery results such as delivery, bounce, block, drop and spam reports so we can find delivery problems. Emails Keel sends through SendGrid have open, click, subscription and Google Analytics tracking turned off.

Service emails are needed to run your account. Unticking news or unsubscribing from news does not stop sign-in, billing or security emails.

At sign-up, the optional box says: “Email me Keel news and offers. I can unsubscribe at any time.” On the contact form, it says: “Send me Keel product news and offers. You can unsubscribe at any time.” We keep the wording, time and keyed address fingerprint with your consent record.

HubSpot manages product-news subscriptions only for people who tick the news box. Every product or marketing email must include an unsubscribe link and our mailing address. You can unsubscribe at any time, or write to privacy@keelpage.com.

HubSpot also serves a separate account-management purpose. When account sync is switched on, it receives the account owner’s name, email, business or account name, account identifier, plan, sign-up source and lead or customer status, even if news is unticked. A ticked news box additionally sends the consent wording and time to subscribe that address. Keel does not sync people merely because they are invited to a site.

AI helpers and outside agents

Keel’s own AI helper is off unless a system administrator switches it on. It currently has no active model connection. Keel therefore sends no prompts, site content or form submissions to an AI model provider through that helper today.

Keel can record AI allowance and usage settings for your account. If you give an outside agent access, that agent can read and change what its permission allows. You choose its provider. That provider’s use of what you send it is covered by your arrangement with it. Do not give an agent personal information or access you do not want it to have.

Visitors to your sites

For a customer’s site, the customer is in charge of the personal information it collects. Keel handles that information for the customer to provide hosting, forms, access and page-view counts. Contact the site owner first about information you gave to that site. We can help the customer respond.

A customer chooses its form fields, whether to store submissions, notification recipients, any webhook destination and the retention setting. A stored submission can include the answers, uploaded files, consent wording and choices, time, browser user agent and keyed address fingerprint. Keel can email it to the customer’s chosen recipients and send it to a webhook the customer sets. Those copies are then under the customer’s control.

Keel’s page-view counts work as described below. Private sites do not run Keel analytics or the third-party trackers injected by Keel’s integration settings. Staging-copy forms do not send. Forms on a private main site can send for people allowed in.

Private-site access records include the site and host, access type, times and expiry, a hashed access token and, for a member, the user identifier. For a share link, Keel records its maker, expiry, use count and last-use time. The private-site cookie lets an approved visitor stay in; it is not an analytics cookie.

A customer may add its own scripts, embeds or services. The customer must explain their collection and cookies in its own notice.

Page-view counts

To see which pages people read, where they come from and what size of screen they use, Keel counts page views itself. It uses no analytics cookies, browser storage or third-party analytics on www.keelpage.com.

For each view, a small script sends the page’s address with nothing after a question mark, its title, which Keel forms are on it, the name of the referring website rather than the full link, and one of five screen-width ranges. It does not send your exact screen width.

To estimate different visitors each day, Keel makes a keyed fingerprint from your network address, browser user agent, site and date. It adds this to a statistical estimate and does not keep the fingerprint. The date changes the fingerprint every day, so this estimate cannot follow you from one day to the next. The page-view record does not store your IP address.

If your browser sends Global Privacy Control or Do Not Track, the view still counts but you are left out of the visitor estimate. Search and AI crawler visits are counted separately under the crawler’s name.

Individual views are deleted after 14 days. Daily totals stay for 14 months. The working data for the visitor estimate is cleared after three days; only totals remain. This data stays in Keel’s own database.

Cookies Keel uses

Keel does not set cookies for ordinary browsing or contact messages on www.keelpage.com. Turnstile is a Cloudflare security service; its own processing is covered by Cloudflare’s privacy policy.

On app.keelpage.com, __Host-Keel.Auth keeps you signed in. Its session lasts 12 hours and extends while you use it, up to seven days from an email-link or passkey sign-in. Microsoft administrator sessions have a 12-hour overall limit.

__Host-Keel.Xsrf and __Host-XSRF-TOKEN protect account requests from being forged by another website. They are browser-session cookies. Microsoft administrator sign-in also uses __Host-Keel.External for a temporary session of up to ten minutes and temporary sign-in checks supplied by the Microsoft sign-in framework.

On a private site, __Host-Keel.SiteAccess lasts 12 hours for a member. For a share-link visitor, it lasts until that link expires: seven days by default and at most 30 days. It can stop working earlier if access is withdrawn.

__Host-keel-preview-assets lets a preview load its media and theme files. It expires with the preview link, which lasts 12 hours. These access and security cookies do not track visits for advertising. Blocking them can prevent sign-in, private access or previews from working.

Who handles information and where

Microsoft Azure hosts Keel’s servers, database and file storage in Canada, including Canada East. It also holds backups, monitoring records and secrets. Microsoft Entra provides Microsoft administrator sign-in.

Cloudflare delivers public sites, manages their edge delivery and runs Turnstile security checks. Twilio SendGrid delivers email. Stripe processes payments. HubSpot keeps customer-relationship records and manages news subscriptions for people who opt in.

Information handled by these providers can be processed outside Canada. Canadian hosting of Keel’s own database does not mean every provider keeps everything in Canada. Information held abroad can be subject to that country’s laws and lawful government access.

We use providers to run the service, deliver messages, secure access and handle customer relationships and payments. We may also disclose information where the law requires it. We do not sell it.

How long information stays

Cleanup runs in background jobs. The periods below are the current defaults. A failed cleanup can delay physical removal. Customer-chosen retention and copies sent outside Keel can differ.

Contact and stored customer form submissions: 24 months by default, with their files and form-webhook deliveries. A customer can choose from one to 120 months for its site.

Sign-up requests: removed once their expiry is more than one day old. Sign-in-link requests: removed after processing, with a one-day cleanup backstop. Expired sign-up, sign-in and invitation token records: removed seven days after expiry.

Finished service-email records and their delivery events: 90 days from creation. Email alerts: 90 days from last seen. SendGrid lookup-job records: seven days. Pending or sending email records remain until they are resolved. Suppression records remain until removed.

Successful HubSpot sync payloads in Keel: cleared 30 days after completion. Pending and failed payloads have no automatic expiry. This does not delete the copy held in HubSpot.

Expired private-site handoffs and access sessions: removed after one day. Expired share-link records: removed after 90 days, once no session references them. Expired bot access tokens, agent refresh tokens and bot assertion-use records: removed after one day. Pending agent sessions are removed one day after their code expires. Ended, denied or expired active agent sessions are removed after 90 days.

Content versions: kept for at least 24 months, and the latest 100 versions of each item stay even if older. Audit records, including the account’s accepted terms version and time, move to an archive after 24 months. That archive has no automatic expiry.

Deleted media: normally removed from active storage after 30 days. Abandoned uploads: cleaned one day after upload expiry, with a two-day storage lifecycle backstop. Older media blob versions have a 30-day lifecycle rule. Deleted blobs and containers have a further 30-day recovery period.

Site backups: nightly copies last 30 days; manual and safety copies last 90 days. Failed backup records are cleaned after seven days, and queued records after one day. A backup in use for a restore can stay longer. Database recovery backups last 35 days. Azure monitoring logs are configured for 30 days.

Background-job input, events and artifacts become unavailable after 30 days; storage cleanup follows and can be delayed. Settled AI call details are eligible for removal after 24 months once the job and every call are settled. Unresolved calls and aggregate accounting records remain for reconciliation.

Account profiles, site records, billing records, marketing-consent records and some security and accounting records have no automatic deletion period in the current service. Consent records are intended to stay for the account’s life. Cancelling billing does not delete them. Copies in HubSpot, delivered email and other providers do not follow Keel’s database cleanup automatically. Ask us about removal; we will explain what we can delete and what we need to retain.

Keeping information secure

Keel uses access controls for accounts and sites, passwordless sign-in, private file storage and keyed address fingerprints in the records described above. Access tokens are stored as hashes. These controls reduce risk; no service can promise complete security.

Your rights and choices

Under Canada’s Personal Information Protection and Electronic Documents Act (PIPEDA), you can ask whether we hold personal information about you, how it has been used or shared, and for access to it. You can ask us to correct inaccurate information, withdraw consent where possible, and challenge how we handle it. You can also ask us to delete it. Write to privacy@keelpage.com or to Resonant Business Solutions Inc., 380 Wellington Street, Tower B, 6th Floor, London, Ontario N6A 5B5.

We may need to confirm your identity. We normally answer an access request within 30 days. If the law permits more time or limits access or deletion, we will explain. Withdrawing information needed to run an account may mean we cannot continue that service. Withdrawing news consent does not affect service access.

If your concern is about a customer’s site, contact that customer first. For our handling of your information, contact us. You can also complain to the Office of the Privacy Commissioner of Canada at https://www.priv.gc.ca/ or call 1-800-282-1376.

Changes to this notice

When our collection or use changes, we will update this page and its version and date. We will give account owners notice of material changes. If a new use needs consent, we will ask for it.