Privacy Policy

1. Two roles

Orderdale is run by Easetra Inc., a corporation incorporated in Ontario, Canada. In this policy, “we”, “us” and “Orderdale” mean Easetra Inc.

For your merchant account, we decide what is collected and why, so this policy applies directly.

For the orders placed in your store, the merchant decides what to ask for and why. We store and process that information on the merchant's behalf, under these terms and their own privacy practices. Every store has a privacy page that tells its customers this: the merchant's own policy, or one we write from the store's settings.

2. What we collect from merchants

When you create and run a store:

• Your name and email address from the Google account you sign in with.
• Your business details: name, contact information, location, the payment details you add (such as an e-Transfer address, bank account details or a payment link), hours, policies and everything you publish. A customer sees your payment details in their order email, and on their order page while that order is waiting for payment.
• Technical records needed to run the service, such as sign-in times and error logs.
• When you ask us to approve a store: where we can see your business, as you tell us, and our notes on the review. We compare payment details across stores to catch ones used for fraud.
• The id of the Stripe account you connect for card payments, which our review of a store may also look at, and whether Stripe lets it take payments. Stripe collects the identity and bank details it needs on its own pages; we never see them.
• When you invite someone to help run your store: the email address you invite, deleted 30 days after the invite is used, cancelled or expires; and who is a member of which store. Members of a store see each other's name and email.

3. What we store about your customers

When someone orders from a store:

Customers do not create an account, and we never ask them for banking credentials: they pay in their own bank or payment app. A customer who pays by card enters the card on Stripe's own page; the card details go to Stripe, never to us, and Stripe tells us whether the payment went through.

• What they ordered, the total, any note they left, and their answers to the store's questions — photos included, when a store asks for them. Only the store's members can open those photos.
• The contact details the order needs — name, email or phone, a delivery address when they choose delivery, and an email for a receipt when they order in the shop.
• When they join a waitlist, book a table, set up a repeat order or hold a pass or membership: their name and email (and a phone number, when they give one for a booking), the party size, dates and note, what repeats and when, and which credit is theirs. A waitlist entry is deleted 30 days after the store tells them the item is back.
• If they report something to us — “I never placed this order”, “stop emailing me”, or a problem with a store: what they chose or wrote, the order it is about and its email address. A problem report is never shown to the store.
• What the store keeps about them: its notes on them and on an order, whether they came to a booking, who an order is for when the store asks (a child, a pet: the name given, with the store's notes and that person's visits), a block if it stops taking their orders, and whether their email address has confirmed it reads its inbox.

4. How it is used and who processes it

Information is used to run the service and nothing else. We do not sell it or use it for advertising. The companies that process it for us are:

Ads on free-plan storefronts and dashboards are chosen by the store's area — never by who is visiting or who runs the store. We don't track visitors or merchants for ads or across sites, and advertisers never receive merchant or customer information. When a business buys an ad from us, we keep the email and business name it gives, its ad and its payment records, to run the ad, bill for it and keep the records the law asks of us; Stripe handles the card. An email left on a full area's ad waitlist is kept only until we write to it once.

We give information to the police or another authority only when the law requires it, or when the law allows it so that fraud or another breach of the law can be investigated — for example, who ran a store and where it was paid, when its customers paid for orders that never came.

• Supabase — the database and sign-in behind your store, hosted in Canada.
• Cloudflare — hosting for the site; storage for uploaded images and order photos; delivering order and status emails; and the bot check at checkout (Turnstile), which sees the visitor's IP address and browser.
• Google — sign-in, so we never handle a password; and the map on a storefront whose merchant added one, which loads from Google Maps only as a visitor scrolls near it.
• Stripe — card payments, for stores that turn them on: it receives the customer's card details, email address and the order's amount and number, and pays the store's own Stripe account.
• Google reCAPTCHA — the bot check on the forms of a store opened at its own domain (ordering, “Find my order”, bookings, waitlists), which sees the visitor's IP address, browser and how the page is used.
• Stripe, and Link, its checkout service — Link sells our paid plans to merchants as our reseller and merchant of record, and Stripe processes the payments: it receives the merchant's name, email and billing address, the store's name and which store a plan is for, and the card details, and as the seller Link also uses them under its own privacy policy — we never see the full card number.

5. Where it is kept and how it is protected

Data is stored with the providers above and may be processed in Canada, the United States or other countries where they operate. That means it can be subject to the laws of those countries.

Access is restricted by database rules so that a merchant can only reach their own store's data, traffic is encrypted, and staff access is limited to what support and operations require.

If a breach of our safeguards creates a real risk of significant harm to anyone, we tell the people affected and the Privacy Commissioner of Canada — and, for people in Québec, the Commission d'accès à l'information — as the law requires, and tell the merchant when it involves their customers. We keep a record of every breach, whatever its size.

6. How long it is kept

Orders and customer records stay as long as the store exists, because merchants need their own history — except photos sent with an order, which are deleted 90 days after it was placed or, for an order booked for a later date, 90 days after that date (sooner if the merchant deletes them), and a customer's details that the merchant deletes at their request. When a merchant deletes their account, the stores they own alone and everything in them are deleted 30 days later. What remains is the billing records of paid plans, which we and Stripe keep as the law requires (six years for our own records); database backups, until they roll over; a record that the deletion happened; for a store that went live, who ran it and where it was paid — its name and address, its contact details, the owner's sign-in email, what they told us when asking to go live and every payment detail it offered (a connected Stripe account's id included), and the problems its customers reported to us about it (what they wrote, when, and the order's number and total) — kept for two years so that fraud reported later can still be traced, then deleted; and payment details we blocked because they were used for fraud, which stay blocked so no other store can offer them.

Error and access logs are kept for a short period and then removed.

7. Your choices

You can see and correct your merchant details in the dashboard at any time, and delete your account and its data yourself from the Account page. Cancel a paid plan first; a store under review is closed through support instead.

If you ordered from a store and want your information changed or removed, ask that merchant first — it is their record. They can delete your details from their dashboard: the order stays in their sales records, without your name, contact details, address, notes or answers. You can also write to us and we will help them act on it.

8. Cookies

We set only the cookies the site needs: the ones that keep you signed in, one that remembers the language you chose, and one that remembers a store's own language for a few hours while you browse it. Google sets its own cookies when you sign in with Google or when a store's map loads. There are no advertising or cross-site tracking cookies.

A storefront counts its visits for its merchant, as daily totals only: visits, products opened and checkouts reached. The visitor's browser keeps a short note in its own storage — not a cookie, and never sent to us — so one visit isn't counted twice; we store nothing about the visitor, such as an IP address or device.

When someone orders in a shop with the shop's code, we keep a one-way, salted hash of their IP address — never the address itself — only to stop codes being guessed, normally for about a day.

To save typing next time, your browser keeps the name, email, phone and address you last used at a store's checkout, and links to your recent orders there. They stay on that device and reach us only when you place an order; “Not you? Clear these details” at checkout removes them.

9. Changes and contact

If this policy changes, the date at the top changes with it, and we will tell merchants by email when the change is significant. Questions and requests go to support@orderdale.com.

One person at Orderdale is responsible for how we handle personal information; write to support@orderdale.com with “Privacy” in the subject to reach them. If our answer doesn't settle it, you can complain to the Office of the Privacy Commissioner of Canada or, in Québec, the Commission d'accès à l'information.