Privacy Policy

This policy covers the June website (hellojune.io), the June app (app.hellojune.io), and the June for Business mobile app. It is written in plain English on purpose. The short version: your data is yours, June collects what it needs to run your shop and nothing more, and nobody here sells data. Ever.

June is operated by Hey Sweet Peas Inc., based in Burlington, Ontario, Canada. That company is responsible for your account details and for what happens when you visit the June website or use the June app. For the client and pet records a shop keeps in June, the shop is responsible, and June looks after that data for the shop. You can reach June at support@hellojune.io.

What June collects

• Account information. Your name, email address, and business details you enter when you sign up.
• Business data you enter. Clients, pets, appointments, services, prices, invoices, signed agreements, and uploaded documents such as vaccine records. This data belongs to you and your business.
• Billing details. Subscription payments are processed by Stripe. June never sees or stores your full card number.
• Client payments (optional).If your shop turns on online payments, your clients' cards are processed by Stripe through your shop's own Stripe account. June keeps a record of each payment (amount, date, card brand and last four digits, and the consent your client gave) but never sees or stores full card numbers. If your shop connects a card machine (Square or Stripe), June also keeps a record of each in-shop card payment: amount, tip, date, card brand and last four digits.
• Messages. When June sends texts or emails on your behalf (booking confirmations, reminders, waiver requests), a record of what was sent is kept so you can see it and so deliverability problems can be fixed.
• Basic technical logs. Standard server logs used to keep the service running and secure.
• How you use the website and the app. Which pages you open and what you click, your device and browser type, your IP address, and your rough location. Some visits are also recorded as a replay of the screen, with everything you type hidden. Details in the cookies section below.
• Ad visits. If you came to the website from an ad on Google, Facebook or Instagram, Google or Meta notes the visit and whether you later started a trial, so June knows which ads work.
• Demo and support calls. If you book a call with June, June keeps your name, email, the time you picked, and anything you write in the booking form. Calls are recorded and transcribed so the founder has accurate notes. If you would rather not be recorded, say so at the start of the call and the recording stops.
• Connected calendar (optional). If a staff member connects their Google Calendar, June stores the connection credentials (encrypted) and the start and end times of their busy events. Details in the Google Calendar section below.

What June does with it

Run the product you signed up for: bookings, reminders, checkout, records, reports. Send you service emails about your account. Send you the occasional email with setup tips and news about June, each with an unsubscribe link. Fix bugs, keep June secure, and stop abuse. Measure how June is used and which ads bring people to it, as the cookies section below explains. That is the whole list. June does not sell your data, does not sell your clients' data, and does not use your client list for its own marketing.

Your clients' information

Client and pet records entered into June belong to the business that entered them. The business decides what to collect and why. June stores and processes that data only to provide June to the business, and only as the business tells it to. In UK and European law terms, the business is the controller and June is its processor; the Data Processing Terms are the contract between them. Texts and emails go only to clients of your business about their appointments and paperwork, and every text respects opt-outs automatically (reply STOP and June stops).

If you are a client of a shop that uses June, contact the shop first about your information. The shop can see, correct and delete your records. If you contact June instead, June will pass your request to the shop and help it answer.

Text messages and your mobile number

Businesses on June collect mobile numbers with consent, at booking or in person, to send appointment text messages such as booking confirmations, reminders, and pickup alerts. Texting is two-way: if you text a business back, your reply, including any photo you send, is delivered to that business's team inbox in June and kept with your client record there. Message frequency varies, message and data rates may apply, and every text honors STOP (opt out) and HELP automatically.

Mobile information is never shared with third parties for promotional or marketing purposes. We will not share your opt-in to an SMS campaign with any third party for purposes unrelated to providing you with the services of that campaign. We may share your personal data, including your SMS opt-in or consent status, with vendors that help deliver text messages, such as phone companies and messaging platform providers, and with no one else. Text messaging opt-in data and consent are never sold or shared with any third parties for marketing purposes.

Texting works in the United States, Canada and the United Kingdom. In the United Kingdom, texts cannot include photos. Appointment texts are service messages, not marketing, and shops may not use June to send marketing texts.

The June for Business app on your phone

June for Business is the app your team installs to run the day from a phone. It works with the same shop data as the web app, plus a few phone-specific things:

• Push notifications.The app can notify your team about new bookings and incoming client texts. To deliver them, your phone's push token is registered with an established push delivery provider, tied to your staff account. Notifications can be turned off any time in your phone's settings.
• Crash reports.If the app crashes, a technical report (app version, device model, operating system version, and the staff account it happened to) is collected by a crash reporting service so the problem gets fixed. Crash reports never include your clients' information.
• Usage basics. The app records which features get used, tied to the staff account, so June knows what to improve. No client data rides along.
• Camera and photos. The app asks for camera or photo access only when a staff member attaches a picture, for example texting a pet photo to its owner or adding one to a pet profile. Only the pictures you choose to attach are uploaded.
• A saved copy for bad signal. The app keeps an encrypted copy of recently viewed shop data on the phone so the day still opens with no connection. It expires on its own within a day, and signing out removes it immediately.

Connecting your Google Calendar

Staff members can connect their own Google Calendar to June. It is optional, personal to each staff member, and never required. When you connect, you pick exactly one calendar, and June does three things with it:

• Sees your list of calendars, once, so you can pick which one to sync. June does not read the others.
• Writes your June appointments onto the calendar you chose and keeps them updated when appointments change or are cancelled.
• Reads busy times from that calendar so your personal commitments block your online booking slots. June stores only the start and end times of events marked Busy, never their titles, details, guests, or locations. Events marked Free are ignored entirely.

The sign-in credentials Google issues are stored encrypted. Nobody at June reads your calendar. Information from your calendar is used only to provide the features described above, and for no other purpose.

Disconnecting deletes the stored credentials and stored busy times immediately, removes June's upcoming appointments from your calendar, and leaves past appointments in place as your own history. You can also revoke June's access at any time from your Google account's security settings.

June does not use information obtained through Google Workspace APIs to develop, improve, or train non-personalized artificial intelligence or machine learning models.

June's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Who touches the data

June runs on a small set of established, industry-standard providers: one hosts the database, sign-in and files, one runs the app's servers, one runs background tasks, one processes subscription billing, one delivers text messages and text sign-in codes, one delivers service emails, one sends June's own emails to shop owners, one delivers the mobile app's push notifications, one collects its crash reports, one measures which features get used and records screens, one checks that forms are filled in by real people, one books demo calls, one records and transcribes demo and support calls, and one carries the founder's own alerts about new sign-ups and shop activity. Each receives only what it needs to do its one job. June keeps a list of these providers and shares it with any customer who asks.

Some data goes to other companies because you or your shop chose it: Google, if a staff member connects Google Calendar, and Square or Stripe, if the shop connects a card machine or takes online payments through its own account. Google and Meta also receive ad visit data, as the cookies section explains, and use it under their own privacy policies.

Where your data is stored and how long it is kept

June's database and servers are in the United States. June is run from Canada, so the founder works with the data from Canada.

• Your account and shop data, including your clients' records and the texts and emails sent for your shop: kept while your account is open. If your subscription or trial ends, your shop stays read-only for 12 months so you can come back or export it. Then June deletes it. You can ask June to delete it sooner.
• Billing and tax records: 6 years, because tax law requires it.
• Shop setups that were never saved with an email: deleted after 30 days.
• June's emails to you:your email address stays on June's email list until you unsubscribe or your account is deleted.
• Screen recordings: 30 days.
• Usage records: 1 year.
• Mobile app crash reports: up to 90 days.
• Server logs: up to 30 days.
• Text sign-in codes: 24 hours.
• Demo and support call recordings, transcripts and notes: up to 18 months.
• Backups: after something is deleted, a copy can stay in backups for up to 30 days.

Cookies and similar tools

The website and the app store small files on your device, such as cookies, and read some information from your browser, for four reasons:

• To work. Keeping you signed in, remembering choices like your country on the pricing page, and checking that forms are filled in by real people. These are always on.
• To measure use. Counting visits and seeing which pages and features get used, so June can improve.
• To record screens.Some visits are recorded as a replay of the screen, so June can find bugs and fix confusing screens. On the website, everything you type is hidden. In the app, all text on the screen is hidden too, so a recording shows the layout and the clicks, not your details or your clients' details.
• To measure ads. Google and Meta tags note if you came from one of their ads and whether you later started a trial.

Pages that a shop's clients use, such as booking pages and the client portal, never record screens or measure ads.

Measuring use, recording screens and measuring ads are on unless you turn them off. You can turn them off at any time from “Cookie Choices” at the bottom of the website.

If you are in the United Kingdom or Europe

UK and European data protection law gives you extra information and rights. Here they are in one place.

Why June is allowed to use your data.

• To run your account, provide June, and give support: because June has a contract with you.
• To keep billing and tax records: because the law requires it.
• To keep June secure, stop abuse, and fix bugs: because June has a legitimate interest in a safe service that works.
• To email you setup tips and news about June: because June has a legitimate interest in telling its customers about June. Every one of these emails has an unsubscribe link.
• To record demo and support calls: because June has a legitimate interest in keeping accurate notes. You can ask not to be recorded.

Your data leaves the UK.It is stored in the United States, where June's providers are, and June works with it from Canada. The UK accepts that Canada protects data well enough for companies covered by Canada's private-sector privacy law, which covers June. Ask June if you want the details.

Your rights.You can ask June for a copy of your data, and ask June to correct it, delete it, limit how it is used, or send it to you in a format another service can use. You can object to uses based on June's legitimate interests, and you can always say no to marketing emails. June answers within one month, or tells you why it needs longer.

Complaints. If you are unhappy with how June handles your data, tell June first at support@hellojune.io. June confirms it got your complaint within 30 days, looks into it, keeps you updated, and tells you the outcome. You can also complain to the Information Commission, the UK's data protection regulator, at ico.org.uk/make-a-complaint, or, in Europe, to your local data protection authority.

Your rights

• You can export your data. Ask, and a complete copy of your clients, pets, and history will be sent to you.
• You can delete your account. Ask, and June deletes your account and business data within 30 days, apart from records that must be kept for legal or accounting reasons.
• You can ask what is stored about you and get a straight answer.

Questions

June is run by its founder, and privacy questions get answered by a human. Email support@hellojune.io, reply to any email June has sent you, or book a call from the website, and you will be talking to the person responsible.