You choose whether to use AI sharing, recording and optional analytics. You can manage retention, export your data and request account deletion in the app. The details below explain how those choices work.
Who we are
Monty is operated by Meridian Ventures LTD. For privacy questions or to exercise your rights, contact support@askmonty.co.uk. We are the controller of information used to manage accounts and administer the service. Businesses using Monty decide how their callers' information is used; we process it on their behalf to provide the service.
This policy covers the Monty service and this public website.
Information we handle
We handle account names, email addresses, phone numbers, business addresses and registration details; selected imported contacts and contact photos; business handbook content and uploaded sources; call audio, transcripts, summaries and follow-up tasks; customer messages, photos and documents; appointments and connected-calendar information; business and assistant profile images; subscription and usage records; device push tokens; and security and operational logs.
Conversations can contain personal or sensitive information supplied by you or callers. Do not provide passwords, payment-card details or unnecessary sensitive information.
Where information comes from
We receive information when you create an account, enter business details, upload knowledge, import selected contacts or use the app. Callers and message recipients provide information during conversations. Connected sign-in, calendar, telephone and payment services provide the information needed for the features you enable. Monty also generates service records such as summaries, usage totals, delivery events and security logs.
Contacts you choose to import
On iPhone, you can choose a contact using Apple’s contact picker. Monty receives the selected contact’s name and phone numbers so you can review them before importing. We do not automatically upload your whole address book. You can also add a number manually.
Imported numbers can be used for customer records and caller rules, including trusted callers. Only import contacts you are authorised to use. Removing a saved contact does not also erase related call, message or job history; those records follow the retention and deletion controls described below.
Why we use it
We use information to create and protect accounts, set up and run the receptionist, route calls, make authorised bookings, send requested messages and notifications, manage subscriptions, prevent abuse and maintain the service. We do not sell personal information or use it to track people for advertising across apps. We need account information to provide the service. Security and abuse prevention support our legitimate interests. You can withdraw optional permissions.
Businesses must establish the appropriate lawful basis for using their callers' information.
Optional usage analytics
If you enable Help improve Monty, we send PostHog screen names, setup progress, action outcomes, timing and platform information, with random identifiers. We use these to understand which steps are confusing and improve the app. We do not send form contents, names, emails, phone numbers, call recordings, transcripts, or payment details through this tracking. Session replay and automatic click capture are disabled.
PostHog receives network requests, which expose your IP address in transit; location enrichment is disabled. Your choice and a random identifier are stored on this device. Analytics is off until you opt in, and you can turn it off in Account & security. Turning it off clears the local analytics identifier and pending events, but cannot retract events already sent. PostHog retains events according to its configured retention settings. Contact us with any privacy questions.
Referral rewards
If you use a referral link or code, we record which business or individual referred you, qualifying subscription payments, reward amounts, subscription discount redemptions and cashback payout status. A pending referral code is stored on your device for up to 30 days and cleared after sign-in. Referrers see anonymous referral labels, progress and reward status, not the referred business's name, email or payment details.
Subscription discount offers are sent to your billing provider and confirmed against verified transactions. Authorised Monty operators can review referred businesses and cashback recipients to arrange a payout. For individually managed referrers, we store the name and contact email supplied by the operator, assigned codes, agreed reward amounts, referral progress and completed-payment references. These individuals do not need a Monty account and do not receive access to customer records.
Disabling a code stops new referrals while retaining existing reward and payment history. We do not collect bank details in the referral screen. When an account is deleted, its referral code and account links are removed; minimal payment and review records are retained without those account links. We retain a keyed fingerprint of an owner who has claimed a referral to prevent repeated claims after account deletion. Subscription providers retain their own transaction records.
Referral records for your account are included in your data export.
Phone number registration
To register a phone number, we collect the actual user's legal name, business or tax registration details where applicable, address, website, verified contact details and authorisation. When required by the number country, number type or provider review, we also collect identity, address or business evidence, such as an ID, passport, utility bill or registration document.
Authorised Monty operators review this information and share the required details and evidence with our telephone provider, Twilio, to verify eligibility and register the number. This processing supports providing the phone service and meeting applicable number-registration requirements. It does not grant permission for marketing.
Registration documents are encrypted in Monty's database, restricted to the account owner and authorised registration operators, included in the owner's export and removed on account deletion. They are not sent to OpenAI, added to receptionist knowledge or included in usage analytics. Local temporary upload copies are removed after upload. Abandoned draft uploads and uploads awaiting customer corrections are deleted after 30 days; approved document copies are deleted after 30 days.
Active submitted or in-review evidence is retained while review is open. Registration details, consent and approval references remain while needed to provide the account's phone service or until account deletion. Provider copies and backups follow their own retention rules; deleting Monty data does not immediately erase those copies.
Service reliability
The app sends limited error reports to Monty’s own service to help detect failures. Reports contain the app version and build, platform, a predefined error category and a broad screen category. They do not include your messages, raw error text or stack traces, account or device identifiers, URLs, tokens or customer content. Reports are counted in daily aggregates, retained for 30 days, and are separate from optional PostHog usage analytics.
Your IP address is visible in transit and used temporarily to limit excessive reports; it is not saved in the diagnostic aggregate. This reporting does not capture native operating-system crashes.
AI and OpenAI
Monty uses OpenAI to power its AI features.
When you use AI features, we send OpenAI your voice or typed messages, relevant business profile and handbook content, call audio or transcripts, and the customer, message, task and calendar records needed for your request. These may include names, phone numbers, email addresses, appointment details and other personal information supplied in conversations or documents.
If you use AI support, we also send your support conversation and limited account setup details, such as plan and subscription status, call-answering settings and whether setup or verification is complete. Support does not automatically include customer records or call content.
OpenAI uses this information to answer calls, help with business setup, transcribe and summarise conversations, suggest handbook improvements, answer questions about your business, prepare work changes for your confirmation and troubleshoot support questions. This choice covers your own AI support chat; it does not opt other people into their personal support chats. You can stop AI sharing in support separately and ask the Monty team without AI.
We do not include your account password or billing card details. Do not put passwords or payment-card details in conversations or documents.
OpenAI does not train its models on API data by default. Its own retention rules still apply, including abuse-monitoring logs normally kept for up to 30 days, with exceptions. Monty's call-retention setting does not control OpenAI's retention.
Calls, voice tests, business setup and call summaries use OpenAI as part of Monty's core service and do not require this optional permission. This setting controls additional AI tools, including knowledge imports and work or support assistance. You can decline or withdraw optional permission in Settings → Account & security. This stops new processing by those additional tools, but does not turn off calls or undo information already sent.
For business and caller information, you are responsible for having authority to share it and giving callers the required privacy information. Your permission here does not replace a caller's rights or your legal obligations.
Your Monty work conversation
Each dedicated Monty conversation is private to the signed-in account. Workspace and role restrictions still apply. Using it is optional. Your current OpenAI sharing permission covers sending your messages and relevant customer, message, call, task and calendar details to OpenAI to answer questions and prepare work on your behalf. If you have already given that permission yourself, you do not need to agree again in Monty chat. Otherwise, you are asked before your first message.
The business must also have enabled AI sharing. Saved customer messages and other reference material do not grant authority to make changes. You review the recipient, details and proposed change before confirming it in the app. Existing messaging permissions, customer opt-outs and workspace access still apply. A queued message is not proof of delivery, and a proposed or pending appointment is not a confirmed booking.
Conversation messages and proposed changes are encrypted in the application database and are included in your account data export. They remain saved until you clear the conversation or delete your account. There is no default time limit. Clear conversation removes its messages and pending proposals; completed tasks, appointments and customer messages remain in their respective app sections. Operation receipts also remain until the account is deleted.
When chat content is deleted, keyed request fingerprints and identifiers remain until account deletion to prevent duplicate processing. Deleting an account removes that account’s conversation and operation receipts. OpenAI’s independent API retention rules still apply. Do not include passwords, verification codes, payment-card details or unnecessary personal data in chat.
Monty support chat
In-app support conversations are private to the signed-in user and specifically authorised Monty support staff. AI support shares your support messages and limited account setup diagnostics with OpenAI for troubleshooting. If you personally accepted the current general AI disclosure that includes support, no second choice is needed. Otherwise, choose Start AI chat explicitly before sharing. An older agreement or another person’s agreement does not opt you in.
Customer call recordings, transcripts, contacts, passwords and payment-card details are not automatically included. You can ask the team for help without enabling AI, and stop AI sharing from the chat. Stopping support sharing stays in effect until you explicitly restart it there. Withdrawing your general AI permission also stops your support sharing; information already sent cannot be recalled.
Relevant or unresolved issues are queued for team review, with team replies shown in the same conversation. Chat content and case summaries are encrypted in the application database. Conversations remain until the user's login or account is deleted and are available in the user's support history/data export. Call-retention settings do not delete support chats. Do not include passwords, verification codes, payment-card details or unnecessary personal data in messages.
OpenAI's API retention rules still apply.
Customer messages and saved work
Customer profiles can include addresses, email, contact preferences and private workspace notes. Notes remain internal and are not supplied as receptionist knowledge. Incoming and outgoing SMS and verified email replies are held as encrypted conversation history, accessible to the owner and active team members. Message read status, pins, archived conversations and saved quick replies are personal to each user.
Messaging consent is recorded separately for each channel; customer opt-outs take precedence. Private upload links let customers send photos and PDFs into the conversation. Links expire after seven days and can be revoked; uploaded files remain until message cleanup or account deletion. Image metadata is removed. Provider attachments that are not supported are indicated without downloading them.
Recent message text and drafts are cached in protected device storage, or encrypted browser-session storage, to support interrupted connections. Cached history expires after seven days and signing out clears the cache. Saving a contact preference does not by itself grant permission to send messages. Saved jobs track work and owner-entered values; these figures are not verified revenue or payment records. Jobs and profiles remain until removed or the account is deleted.
Removing a saved contact deletes its profile but keeps call, message and job history. Automatic cleanup erases message content after the chosen period while retaining minimal delivery and duplicate-prevention metadata; future appointment messages are handled with the appointment lifecycle. When a caller asks about earlier work, Monty asks permission to text a verification code. They enter it on their phone keypad before Monty can access relevant previous enquiries or open job status.
Private notes and financial values are excluded. The code is not added to the call transcript.
Team work and internal voice
Team members can manage permitted customer follow-ups and view their assigned appointments. Owners can manage the team’s work; colleagues see other people’s appointments as busy time. Connected personal calendar titles are not shown in this view. Talk to Monty is optional and starts only when a signed-in person chooses Start conversation after reviewing the sharing notice.
It sends their voice and the relevant permitted customer, task and appointment details to OpenAI to answer work questions and prepare changes. The business must also have enabled AI sharing. Proposed changes need confirmation in the app. Monty does not save internal voice audio or conversation transcripts to call history; temporary conversation text is held for the session. Confirmed tasks remain in the workspace until explicitly removed with their related call or account.
Automatic call cleanup preserves team-created tasks and removes their link to the expired call. OpenAI’s retention rules still apply.
Conversation images
You can save photos in a customer or call conversation. The business owner and active authorised team members can view them. Images are encrypted in the application database, resized and stripped of embedded location and camera metadata. Saving a photo does not send it to a customer or to OpenAI. If you choose Send photo, Monty sends an SMS containing a private viewing link after checking messaging permission and allowance.
The link expires after seven days; anyone with that link can view the photo while it is valid. The uploader and business owner can remove photos. Removing a photo also makes its viewing link unavailable. Deleting the associated call or business account also removes saved images. Images are included in the business owner’s data export. Backups follow the service’s backup rotation.
Recordings, transcripts and learning
Incoming callers hear an AI/transcription notice. When audio recording is enabled, incoming callers can press 2 to opt out of the recording. Outbound AI calls start with the assistant's natural introduction, without a separate spoken recording or transcription notice. Outbound transcripts are saved, and audio is saved when the business has enabled recording. Businesses are responsible for informing outbound recipients about recording and transcription and obtaining any required permission.
Turning off audio recording does not turn off transcription. Where learning from owner-answered calls is enabled, recordings may also be transcribed and analysed. Owner-selected learning calls save their conversation text as a source in Knowledge and prepare proposed facts for review. Mock customer calls do not create knowledge suggestions. Suggested knowledge needs the business's approval before future calls use it.
Businesses should explain their own purposes, retention and contact route to callers.
Suppliers and integrations
Amazon Web Services hosts the service and backups and can deliver service email. Twilio handles phone calls, recordings, phone verification and configured SMS delivery. Configured email conversations use a private reply address; verified replies from the linked customer email appear in the same inbox. Email attachments are not automatically imported; customers can use a private upload link instead. OpenAI provides AI voice, transcription, analysis and optional support assistance.
PostHog receives the limited usage events described above only when you enable analytics. If you choose Apple or Google sign-in, that provider shares a verified email address, a stable account identifier and, when available, your name. Apple can supply a private relay address. We keep encrypted provider credentials to support account revocation when you delete your account. This sign-in does not grant calendar access.
Expo and Apple/Google deliver mobile notifications; notification text is generic. Stripe handles web subscriptions, and Apple/Google handle purchases made through their app stores. Google Calendar, Microsoft Outlook and Apple iCloud Calendar receive scheduling information only when the relevant integration is connected or used. An iCloud calendar connection uses an encrypted Apple app-specific password, which you can revoke in your Apple Account.
Email delivery uses Amazon SES or Resend, depending on the service configuration. Payment providers receive payment details directly; Monty stores subscription references and status rather than full card details. Suppliers may process information outside the UK; provider-specific locations, retention and transfer protections apply. UK hosting does not mean every supplier processes data only in the UK.
Google sign-in and Google Calendar
Google sign-in and Google Calendar are optional and separate. If you choose Google sign-in, Google provides a verified email address, a stable account identifier and available profile information such as your name. We use these to identify your account and support sign-in. Choosing Google sign-in does not connect your calendar.
If you connect Google Calendar, Monty reads the connected primary calendar's identifier, access permissions and scheduling metadata. It requests event identifiers, timing and busy/cancelled status in the time range needed to check availability. This availability request excludes event titles, descriptions, locations and attendees. The separate diary view can show titles from the owner’s calendar; colleagues’ personal calendar titles are not requested by that view and appear as Busy. New connections request event access for calendars you own, and Monty connects your primary calendar.
When you enable calendar writes, Monty sends Google the details needed to create, reschedule or cancel your authorized Monty appointments. For appointments managed by Monty, we retain the external event identifier and a synchronization snapshot, including title, timing, cancellation state and version information, to reconcile changes and identify conflicts. Relevant changes made in Google Calendar can update the corresponding Monty appointment. This does not import every Google event into Monty's customer records.
We keep connection credentials encrypted so the server can maintain the calendar connection. Calendar data is processed on our hosting infrastructure to provide the scheduling functions you choose. When you enable AI call handling, available appointment times derived from calendar checks and booking results can be sent to OpenAI so the receptionist can offer times and confirm authorized bookings. Appointment information may also be used by the messaging features you enable, as described elsewhere in this policy. Google sign-in information is used for account access and administration. These permissions are not used for advertising or selling your personal information.
Who receives Google user data: we share, transfer or disclose it only as needed to provide and secure the features you use, with your permission where required, or when required by law. The recipients and purposes are described below.
Amazon Web Services (AWS) hosts Monty’s application, databases and backups. AWS processes the Google sign-in and connected-calendar information needed to host and operate the service, including encrypted connection credentials and any calendar records we store.
OpenAI receives relevant Google Calendar-derived available times and booking or appointment information when you use enabled AI features, including the receptionist or Monty’s work assistance. OpenAI processes that information to provide the AI response or scheduling feature you requested.
For the appointment messages and reminders you enable, Twilio processes SMS messages, Meta processes WhatsApp messages, and Amazon SES or Resend processes emails, as applicable. These providers receive the destination and appointment information needed to deliver the message. Expo and Apple or Google notification services receive the limited delivery information and generic notification text needed to send app alerts.
Google receives the scheduling details needed to create, update or cancel events when you enable calendar writes. The business owner and authorised team members can see relevant information in Monty according to their access permissions, and the customer receives the appointment details included in an authorised message. We do not sell Google user data or share it for advertising.
You can disconnect a calendar in Monty after resolving pending synchronization work and future linked appointments. This removes the stored calendar connection credentials and stops further access through that connection. Disconnecting does not erase existing appointments or events already held in Google Calendar. You can also revoke Monty's access in your Google Account. Saved Monty appointment records follow the retention and account-deletion controls described in this policy; backups rotate separately. Google applies its own retention rules to data it holds.
Monty's use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. We use this information only to provide or improve the connected features described here. We do not sell it, use it for advertising or credit decisions, or use it to train general-purpose AI models. Human access is limited to your affirmative permission, necessary security or legal work, or permitted internal use of aggregated data.
Google API Services User Data Policy · Manage Google connections
How long we keep information
Business call data is not automatically deleted based on its age. Previous automatic-cleanup settings no longer expire records. Call history, transcripts, follow-ups, past appointments and outbound conversation content remain until explicitly deleted or the account is deleted. Provider recording deletion can take additional time or require retries. Recording opt-outs and explicit deletion requests are still honoured.
Handbook entries, knowledge-review sources (including learning-call transcripts), their evidence and contacts stay until removed or the account is deleted. Removing source history removes its transcript; delete associated knowledge entries separately to remove their saved excerpts. Outbound attempt metadata and do-not-call records help prevent unwanted calls. Email delivery events remain until account deletion. Subscription providers may retain transaction records for legal obligations.
Backups and provider copies are not erased immediately when live data is deleted; backup rotation and provider retention apply. Monty’s setting does not control independent providers’ retention periods.
Your controls and account deletion
You can change recording and learning preferences in Settings → Account & security → Privacy & data, export account data, and request permanent deletion in Settings → Account & security. A business owner’s deletion removes the workspace for its team. Staff can delete their own login without deleting the business’s records. An owner’s deletion may need time to settle an active call, provider usage or an uncertain number order before workspace data can be removed.
New activity is paused while that request is processed, and unresolved provider issues require operator review. Recording cleanup and phone-number routing cleanup retry separately; minimal provider identifiers remain while cleanup completes. Monty-owned pool numbers may be reassigned to another business immediately after their old routing is cleared. Other managed rentals are released through the provider.
Deletion does not cancel Apple or Google subscriptions: cancel them through the store to stop renewal. Web subscriptions are cancelled as part of account deletion. Existing events in an external calendar and records lawfully held by independent providers are not erased by deleting Monty. Remove carrier forwarding before deleting; your old Monty number may be reassigned.
Security and your rights
We use access controls, password hashing and HTTPS to protect the service, but no service is risk-free. Depending on applicable law, you may ask to access, correct, delete, restrict or transfer your information. You may also object to certain uses, withdraw optional permission or complain to the UK Information Commissioner's Office at ico.org.uk. Callers should normally contact the business they called. You can also contact support@askmonty.co.uk, and we will help direct your request.
We may need to keep some information to meet legal obligations or resolve disputes. We update this policy when our data practices change.
Contacting support
You can use support@askmonty.co.uk for both support and privacy questions. Incoming support and privacy email is received through Amazon SES and forwarded to a support inbox hosted by Google. Your message, contact details and attachments are shared with these providers so we can receive and respond to your enquiry.
Original incoming messages are stored privately in encrypted AWS storage and scheduled for deletion after 30 days; deletion processing can take additional time. Suspicious or unusually large messages are held there for review instead of being forwarded, and the support inbox receives a notice. Forwarding status records expire after 30 days, delivery events after four days, and error records after 14 days. These schedules do not delete the forwarded copies in our Google inbox. The app’s call-retention setting does not apply to support correspondence. Contact us if you would like us to review or delete correspondence, subject to any information we need to keep for legal obligations.
Visiting this website
This public website provides product information, industry guides, legal policies and an optional live AI receptionist demo. We have not added advertising, analytics or tracking scripts. The website is hosted on Amazon Web Services using Amplify Hosting and its content delivery infrastructure. AWS receives technical request information such as your IP address, browser information and requested pages to deliver and protect the website. Infrastructure logging and retention rules apply.
If you choose Start demo call and allow microphone access, your audio is shared with OpenAI to generate live spoken replies. Monty does not record or store demo audio or transcripts. Live captions appear temporarily in your browser. Our dedicated demo service keeps session metadata and a keyed hash of your network address for call controls and abuse prevention; completed session metadata and expired limit records are removed within approximately 24 hours. Provider processing and retention are described in OpenAI’s API data controls. Please use made-up details. The demo cannot make real bookings, send messages or access customer accounts. You can mute, end the call or leave the page at any time.
Emailing us shares your message and email address so we can respond to your enquiry. Links to Apple, OpenAI and other services take you to websites with their own privacy practices.
Meridian Ventures LTD