Ironstone Design

Privacy policy

In force from November 11, 2026 for Sellers who join from that day, and from December 11, 2026 for Sellers who joined before it. Version 2026-11-11.1.

Ironstone is 1001732317 Ontario Inc. o/a Ironstone Design, reachable at contact@ironstonedesign.com and by mail at 2914 Pine Ave, Unit #195, Niagara Falls, NY 14301.

On this page
  1. Scope
  2. Information collected
  3. Purposes
  4. Disclosure
  5. Where information is stored
  6. Retention
  7. People in Europe and the United Kingdom
  8. People in Canada
  9. People in California
  10. Children
  11. Access and correction
  12. Security
  13. Changes

1. Scope

1.1 This Privacy Policy covers personal information that Ironstone collects through ironstonedesign.com, app.ironstonedesign.com, mysiteslive.com and the Storefronts.

1.2 Ironstone is accountable for that information under the privacy laws that apply to it. Its Privacy Officer is responsible for the protection of personal information and can be reached at privacy@ironstonedesign.com or by mail to the Privacy Officer, 1001732317 Ontario Inc. o/a Ironstone Design, 2914 Pine Ave, Unit #195, Niagara Falls, NY 14301.

2. Information collected

2.1 Account information: the email address, the storefront name, the prices, and, for outreach, the legal name, the mailing address and the country the Seller supplies.

2.2 Welcome answers: the name a Seller gives, how it describes itself, what it wants to use Ironstone for, how much it has built or sold websites before, the tools it picks first and how it heard about Ironstone. Ironstone uses them to set up the Seller’s first screens and, counted without names, to learn how new Sellers find it.

2.3 Help chat: each question a Seller or a member of its team types into the help chat in the app, the answer shown and its cost, kept to check and improve the answers and deleted with the Account.

2.4 Billing information: Stripe’s identifiers for the Seller’s customer record and connected account. Stripe holds every card number and bank account, and Ironstone never receives either.

2.5 Client information: the business details a Client or a Seller enters for a Site, the Client’s email address, and the acceptance record with its date, its wording, and the IP address and browser details from which it was given.

2.6 Intake information: the details, the description, the opening hours, the services, the logo and the photos a business sends through an intake form, its confirmation that it owns the photos and the logo or may use them, the time of that confirmation, and the IP address the form was sent from.

2.7 Business information in the Lead finder, described in the Prospect Data notice at ironstonedesign.com/legal/prospect-data/.

2.8 Mailbox information: the app password a Seller saves for outreach, sealed with AES-GCM when saved, and the replies received in that mailbox.

2.9 Google sign-in: when a person signs in with Google, the email address and the Google account identifier that Google returns. Ironstone never receives a Google password.

2.10 When you ask for a sign-in code, we record the time, the email address, and the device and network it came from, and keep it for up to 90 days to protect your account from misuse.

2.11 Team members: the email address of each person a Seller invites to its team.

2.12 Bookings and orders: the name, email address, telephone number, the service or the items, the time chosen and any note a customer sends through a Site’s booking or order page, kept for the Client and its Seller.

2.13 Affiliate referrals: the Affiliate sees the first name and the state of each Referred Account, and no other detail of it.

2.14 Abuse prevention: hashed records of the network, the device mark, the card, the telephone number and the payout account linked to an Account, used to apply limits and to stop self-referral; and Cloudflare Turnstile, which checks that a form is sent by a person.

2.15 Technical information: the IP address and browser details in Cloudflare’s request logs; for each signed-in session, the browser and an approximate location (a city and a country, from the IP address), shown to the Account holder on the Security screen; and the cookies in the table below. Ironstone uses no advertising cookies.

2.16 Embedded map services: Sites displaying embedded Google Maps transmit user request parameters directly to Google, subject to the Google Privacy Policy available at policies.google.com/privacy.

2.17 Visits: Ironstone counts visits to ironstonedesign.com and to Storefronts itself, without cookies and without storing anything on the visitor’s device: the page, the site that linked to it, campaign tags, the country, state or region and city, and the kind of device, the buttons and links that matter, the time on a page, and a visitor key that changes every day (a one-way hash of the IP address and the browser with a random value that is replaced daily; the IP address itself is not stored). A browser that sends Global Privacy Control or Do Not Track is not counted. A new Account keeps the source of the visit that brought it.

2.18 Messages sent through the contact form on ironstonedesign.com, delivered to Ironstone by email.

2.19 Lead information: the name, email address, telephone number and message a visitor sends through the contact form on a Site, the visitor’s choice about marketing follow-up with the sentence shown beside it, and the page the message was sent from. The visitor’s IP address is kept only as a salted hash, to limit repeated messages. Taps on a Site’s call and text links are counted per day, with no visitor identifier.

2.20 Analytics on ironstonedesign.com: Google Analytics 4 (Google) and Microsoft Clarity (Microsoft) measure how visitors use the website, such as the pages viewed, clicks, scrolling and the kind of device, and Clarity records the visit’s mouse movements and taps with the text typed into forms masked. Both set cookies, listed in the table below. For visitors in the European Union and the European Economic Area, the United Kingdom, Switzerland and Quebec, neither runs until the visitor accepts it in a consent banner, and Google Analytics runs in Consent Mode version 2. Ironstone turns off advertising features in both.

3. Purposes

3.1 Ironstone uses personal information to open and run Accounts, build and host Sites and Previews, deliver each lead to the Client whose Site received it (and a copy to that Client’s Seller when the Seller asks for one), take payments and pay Sellers, send sign-in codes and service notices, prevent abuse, and meet legal duties.

3.2 Ironstone does not sell personal information and does not use it for advertising.

3.3 The Lead finder uses Google Maps Platform, and Google’s handling of that information is governed by the Google Privacy Policy at policies.google.com/privacy.

4. Disclosure

4.1 The companies listed at ironstonedesign.com/legal/subprocessors/ process personal information for Ironstone under written terms.

4.2 A Seller sees the information of its own Clients and of the businesses its own Lead finder searches return. A Client and its Seller see the leads sent through that Client’s Site. Ironstone may disclose information where the law requires it.

5. Where information is stored

5.1 Ironstone’s service providers store and process information in the United States and other countries, where courts and authorities may obtain access to it under local law.

6. Retention

6.1 Ironstone keeps personal information only as long as the table below states, and a daily job deletes what has reached its limit.

6.2 The photos and the logo sent through an intake form are kept for at most seven (7) days before the automated check. Those that pass become part of the Site; the others are deleted. The intake record is kept with the Client information.

7. People in Europe and the United Kingdom

7.1 This section applies to a person whose personal information Ironstone processes while that person is in the European Economic Area, the United Kingdom or Switzerland.

7.2 Ironstone processes that information to perform its contract with a Seller or an Affiliate (Accounts, Plans, payments and payouts); for its legitimate interests in running, securing and improving the Services and in preventing abuse (sign-in protection, limits and fraud checks); with the consent of the person, who may withdraw it at any time without affecting earlier processing; and to meet its legal duties, such as tax records.

7.3 For the information of a Client, of a Client’s customers and of the businesses a Seller contacts, the Seller (or the Client) decides the purposes, and Ironstone processes the information on its behalf under the Data Processing Addendum.

7.4 Such a person may ask for access to, correction of, deletion of or restriction of that person’s information, or for a copy in a portable format, and may object to processing based on legitimate interests, by writing to privacy@ironstonedesign.com. Ironstone shall answer within one (1) month.

7.5 Such a person may also complain to the data protection authority where that person lives or works.

7.6 Ironstone is established in Canada, which the European Commission and the United Kingdom recognize as giving adequate protection to personal information handled by businesses. The sub-processors that process the information in the United States or elsewhere do so under data processing terms that include the European Commission’s Standard Contractual Clauses, or under the EU-U.S. Data Privacy Framework.

8. People in Canada

8.1 Ironstone handles personal information under the Personal Information Protection and Electronic Documents Act and, for people in Quebec, under the Act respecting the protection of personal information in the private sector, as amended in 2021 (Law 25).

8.2 The person in charge of the protection of personal information at Ironstone is its Privacy Officer, reachable at privacy@ironstonedesign.com.

8.3 A person may ask to see or correct the personal information Ironstone holds about them, or may withdraw consent, by writing to privacy@ironstonedesign.com. Ironstone shall answer within thirty (30) days.

8.4 A person who is not satisfied with Ironstone’s answer may complain to the Office of the Privacy Commissioner of Canada at priv.gc.ca, or, in Quebec, to the Commission d’accès à l’information at cai.gouv.qc.ca.

9. People in California

9.1 This section applies to residents of California.

9.2 Ironstone collects the categories of personal information listed under “Information collected”, from the sources and for the purposes this policy states. It keeps each for the time the retention table states.

9.3 Ironstone does not sell personal information or share it for cross-context behavioral advertising, and does not use sensitive personal information to infer anything about a person.

9.4 A California resident may ask to know, see, correct or delete the personal information Ironstone holds about them, and will not be treated differently for asking. A request goes to privacy@ironstonedesign.com. Ironstone checks the request against the email address on record and answers within forty-five (45) days. An authorized agent may ask on a resident’s behalf with the resident’s signed permission.

10. Children

10.1 The Services are meant for people aged eighteen (18) or older. Ironstone does not knowingly collect personal information from a child, and deletes it when it learns of it.

11. Access and correction

11.1 A person may ask to see, correct or delete the personal information Ironstone holds about that person, and may withdraw consent, by writing to privacy@ironstonedesign.com. Ironstone shall answer within thirty (30) days.

11.2 A person may also complain to the privacy regulator that oversees Ironstone.

12. Security

12.1 The safeguards are described at ironstonedesign.com/security/.

13. Changes

13.1 Ironstone shall post any change to this Privacy Policy in the changelog, with its date, before the change takes effect.

Cookies

CookieSet onWhat it doesKept for
psapp.ironstonedesign.comKeeps a Seller signed inThirty days
pkapp.ironstonedesign.comTies a sign-in code to the browser that asked for itOne hour
ir_inironstonedesign.com and its subdomainsTells the website that the browser is signed in, so it shows the dashboard linkThirty days
gauthapp.ironstonedesign.comCarries a Google sign-in to its endTen minutes
ir_ref, rfironstonedesign.com, app.ironstonedesign.comRecords the Affiliate whose link was opened90 days
rcapp.ironstonedesign.comRecords an Affiliate’s discount code90 days
ajapp.ironstonedesign.comOpens the Affiliates page after a sign-up that began thereOne day
dvapp.ironstonedesign.comA random device mark that limits new Accounts from one deviceTwo years
pcThe Storefront’s addressKeeps a Client signed in to its client loginThirty days
pkcThe Storefront’s addressTies a Client’s sign-in code to the browser that asked for itOne hour
pvaapp.ironstonedesign.comOpens a Seller’s read-only view of a Client’s loginOne hour
obapp.ironstonedesign.comA random mark links the steps from finding a business to claiming its website at sign-up. It allows one website a day. Ironstone sees only daily totals.Thirty days
obvapp.ironstonedesign.comRemembers which version of the getting-started page you saw.Thirty days
obscapp.ironstonedesign.comRemembers the background picture on your getting-started page.Thirty days
oboptapp.ironstonedesign.comRemembers the headline, font, and background you selected on the getting-started page.Thirty days
obpassapp.ironstonedesign.comLets approved test browsers view the getting-started page without visitor limits, and keeps these visits out of our total counts.One day
pickapp.ironstonedesign.comRemembers the plan chosen on the pricing page until the end of sign-upOne day
tnapp.ironstonedesign.comDisplays required legal update notifications prior to account access.One day
pickbapp.ironstonedesign.comRetains selected subscription billing frequency throughout the registration process.One day
_ga, _ga_[id]ironstonedesign.comGoogle Analytics 4 tells visits from the same browser apart to measure how ironstonedesign.com is used.Two years
_clckironstonedesign.comMicrosoft Clarity links the pages of one visit and of later visits from the same browser, to show how visitors use ironstonedesign.com.One year
_clskironstonedesign.comMicrosoft Clarity links the pages of one visit and of later visits from the same browser, to show how visitors use ironstonedesign.com.One day
CLIDclarity.ms, owned by MicrosoftMicrosoft Clarity uses it to recognize the browser across websites that use Clarity, by marking the first time Clarity saw it.About one year

Every cookie is needed for the feature it names except the analytics cookies of Google Analytics 4 and Microsoft Clarity (item 2.20); none is used for advertising, and Sites set none of them. Visitors in the European Union and the European Economic Area, the United Kingdom, Switzerland and Quebec are asked for consent in a banner before the analytics cookies are set, and may withdraw it at any time from the link in the footer. Ironstone’s own visit counts stay cookieless, as Information collected describes.

How long information is kept

InformationKept for
Sign-in codesValid for ten minutes; the record is deleted after thirty days
Sign-in code requestsUp to ninety days
SessionsThirty days, or until the person signs out
Account, Storefront and Client informationWhile the Account is open, and thirty days after it closes
Client Sites of a closed AccountUp to ninety days after the Account closes, unless the Client moves to another Seller
Billing records (plans, fees, payments, refunds)Six years, as tax law requires
PreviewsThirty days after the build, or at once on takedown
Earlier versions of a SiteNinety days; the current version while the Site exists
Messages, bookings and orders sent through a SiteTwenty-four months, or ninety days after the Site ends or is taken down, or until the Client or the Seller deletes them
Notifications in the app, and the record of emails sentTwelve months
Abuse-prevention records (hashed)Twenty-four months
A business’s report about its SellerTwenty-four months
Lead finder searchesThe words searched, thirty days; the count used for billing, thirteen months
Content-security reportsNinety days
Photos sent with a change requestSixty days

Other policies