Privacy Policy
How InToday collects, stores, and protects your data
Last updated: 15 November 2026
InToday is practice- and business-management software operated by Inteady Software Inc. It is used by your business — a clinic, home-care agency, sole proprietor, or any other organization or individual that subscribes to InToday — and its staff to manage bookings, records, billing, and communication with clients. This policy explains what we collect, where it lives, who can reach it, and the specific commitments we make about data we receive from Google and Microsoft accounts you choose to connect. The short version: your data is yours, you decide what is connected and enabled, and you can take it with you at any time.
1. Who can access the data
Data belongs to the business that entered it. Access inside a business is controlled by per-user permissions, so staff see only what their role allows. Businesses are isolated from one another at the database level — no business can read another business's data.
Inteady Software Inc staff do not browse your business's data. We access it only when you ask us to for support, when we must investigate a security or abuse incident, or where the law requires it. Administrative access is logged.
2. Access control and logging
Accounts are individual, not shared. Permission changes, record access, and administrative actions are recorded in an audit log the business can review.
3. Data residency
All platform data — records (clinical or otherwise), bookings, billing, and anything we sync from a connected mailbox or calendar — is stored in Canada in Amazon Web Services Canadian regions. Data is encrypted in transit and at rest.
Some categories of service we use to deliver features process data in the United States. While your information is processed outside Canada, it is subject to the laws of that jurisdiction and may be accessible to the courts, law enforcement, and national security authorities of that country. We limit what each provider receives to what its part of the service needs, and we bind every provider by contract in how it may use it.
4. Service providers
You decide most of what leaves the platform. Services your business deliberately connects, and the payment processor your clients see on their receipts, are named here; swappable infrastructure is described by category so this policy stays accurate as we improve the underlying plumbing.
- Services you connect: Google, Microsoft, QuickBooks, Xero, and practice-management systems you import from — each only when your business chooses to connect it, and only with the access you grant.
- Payments: Stripe processes card payments and payouts.
- Hosting: Amazon Web Services, Canadian regions.
Connected integrations are your choice. Services like QuickBooks, Xero, Google, and Microsoft are connected and enabled by your business, and your business is solely responsible for confirming a connected service fits its needs and obligations — including which edition it uses and where that provider stores data. Once information flows to a service you connected, that provider's own terms and privacy practices govern it.
Categories of infrastructure provider we use:
- SMS and voice telephony providers
- Conversational AI and speech providers
- AI model providers, under contracts that prohibit using your data to train their models — your data is not used to train anyone's AI
- Video conferencing and telehealth providers: Whereby by default (Whereby's privacy policy), or another provider your business chooses, such as Microsoft Teams or Google Meet
- Meeting transcription providers
- Email delivery providers
- Fax transmission providers
- Error monitoring and usage analytics providers (with PHI excluded)
For voice, SMS, and conversational AI, the processing location depends on the configuration your business selects at setup — some options process in Canada, others in the United States. The setup screen shows which is which, so the choice is always in your hands.
For businesses that bill insurers and government payers — ICBC, WorkSafeBC, MSP/Teleplan, and TELUS eClaims — those payers receive submissions only on your business's instruction, when your business chooses to submit a claim or invoice.
5. Google user data
Connecting a Google account is optional and is always initiated by you. If you connect one, we request only the scopes needed for the features you use.
Scopes we request and why
-
gmail.readonly— reads your mail so InToday can show your inbox and message threads next to the client record they relate to. -
gmail.modify— applies labels and marks messages read, archived, or snoozed when you triage them in InToday. We do not permanently delete your mail. -
gmail.send— sends only the messages and replies you compose or explicitly approve. InToday does not send mail from your account on its own initiative. -
userinfo.email,userinfo.profile,openid— identifies which mailbox you connected so we can label the account in the interface. -
calendar.readonly,calendar.events— shows your existing calendar alongside InToday bookings and attaches meeting links to appointments. -
analytics.readonly,adwords,webmasters.readonly,business.manage— reads marketing performance figures for businesses that choose to connect those accounts.
How we store it
Message content and metadata we sync are stored in your business's database in AWS Canadian regions, encrypted in transit and at rest. OAuth tokens are stored encrypted and are used only to call Google on your behalf.
Human access
No person at Inteady Software Inc reads your Google user data except when you give explicit permission for a support request, when it is necessary to investigate a security incident or abuse, or where required by law.
AI processing
InToday can draft replies and summarise threads for you. When you use those features, the relevant message content is sent to our AI provider for processing under a contract that forbids using your data to train or improve generalised AI or machine-learning models. Your Google user data is not used to train any model, ours or anyone else's, and it is not retained by the provider for training purposes.
What we never do
- We never sell Google user data, or transfer it for a fee.
- We never use Google user data for advertising, and never use it to build advertising or marketing profiles.
- We never use Google user data to train generalised AI or machine-learning models.
- We never transfer Google user data to third parties except as needed to provide or improve InToday's features for you, for security purposes, or to comply with applicable law.
InToday's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Revoking access and deleting your data
You can disconnect a Google account from InToday at any time in the app's email account settings, which deletes the stored OAuth tokens and stops all further access. You can also revoke InToday's access directly from your Google Account at myaccount.google.com/permissions.
To have synced mailbox content deleted, disconnect the account and contact support@ntdy.io. Deleting your InToday account removes it as described in section 10.
6. Microsoft user data
Connecting a Microsoft 365 or Outlook account works the same way. We request mail and calendar permissions to read, triage, and send the messages you act on in InToday, and to display your calendar. Microsoft user data is stored, protected, accessed, and deleted on the same terms set out in section 5 — including that we never sell it, never use it for advertising, and never use it to train generalised AI models.
7. AI features, call recording, and transcription
Every AI feature in InToday is opt-in and business-controlled. Nothing is recorded, transcribed, or sent to an AI provider unless your business has turned the feature on, and your business can turn it off again at any time.
- When your business enables call recording or the AI receptionist, calls may be recorded and transcribed so the business has an accurate record and the assistant can help callers.
- The business controls how the AI receptionist is configured, including how it introduces itself to callers and what callers are told about recording.
- The business decides what its clients or patients are told about these features and is solely responsible for obtaining the consent its province requires for recording and AI-assisted calls.
- Data sent to AI model providers is processed under contracts that prohibit training: it is not used to train their models and is not retained for training purposes.
8. Cookies and analytics
We keep cookies minimal and purposeful:
- Essential cookies keep you signed in and maintain your session. The app does not work without them.
- Usage analytics help us understand how InToday is used so we can improve it. PHI is excluded from analytics, and we never sell personal information.
- Advertising and remarketing are used only for visitors to our marketing site — never inside the app, and never using patient or clinical data.
9. Legal framework
We operate under Canadian privacy legislation, including PIPEDA and, where health information is involved, applicable provincial health-information legislation. Where health information is involved, your business remains the custodian of that information; Inteady Software Inc processes the data your business entrusts to it on your business's instructions.
10. Data retention and deletion
Your data is yours to take. You can export it at any time while your account is active — no waiting period, no gatekeeping. After you close your account, we retain your data for 60 days so you can retrieve anything you missed, then permanently delete it.
Record retention schedules — for health businesses, the periods your college or regulator requires clinical records to be kept — remain your business's responsibility, as custodian where health information is involved. Export what you must keep before the 60 days end.
11. If something goes wrong
If a security incident affects your data, you hear it from us first — we notify affected businesses without undue delay, with the facts we have and the steps we are taking. The business — where health information is involved, as custodian of its patients' records — notifies the people affected where the law requires it, and we support the business with everything it needs to do that well.
12. Your rights
You may ask to access, correct, or delete the personal information we hold about you, and to withdraw consent for optional processing. Write to support@ntdy.io.
13. Location data (service providers and staff)
This applies only to staff who use InToday to manage shifts. We do not collect device (GPS) location from patients or clients. Like most online services, our servers see the IP address of any device that connects, which can indicate an approximate region — for example, when a document is signed electronically, the IP address is kept as part of the signature's audit trail. If a future feature ever needs device location from patients or clients, it will be optional, asked for at the time, and reflected in this policy first. With your consent we collect device location, including in the background while a shift is active, for geofenced clock-in and clock-out, route tracking during active shifts, and optional location sharing with your employing organisation or supervisor. You can disable location at any time in the app or in your device settings; some shift features will not work without it. Location data is stored in Canada and is never sold.
14. Changes to this policy
We update this policy from time to time as the product evolves. Meaningful changes are flagged by email or in-app, and the revised date above always tells you when it last changed. Continued use of InToday after a change means you accept the updated policy.
15. Privacy Officer and contact
Our Privacy Officer is Mubashshir Zakir. Questions, complaints, or requests about privacy: support@ntdy.io.