Privacy policy
What we collect on teremu.com and in the Teremu app, why we process it, who we share it with, and how to exercise your rights.
At a glance
- We do not sell or rent personal data, and we run no targeted advertising.
- The site sets no first-party cookies. Analytics runs only if you accept it.
- We collect what you send us through a form, what you enter in the app to run your restaurant, and aggregate usage metrics.
- If you connect Gmail, your POS, or an external AI assistant, access is read-only and you can revoke it at any time.
- You can ask us to access, correct, or delete your data at any time.
This summary is for orientation only and does not replace the full text below.
Who is responsible for your data
Teremu is a product built and operated by MTM CYA Corp, trading as MTM Cofounders & Associates (“MTM”), a company incorporated in the United States. MTM is the controller of the personal data described in this policy. “Teremu”, “we”, and “our” refer to that same entity.
Data controller
MTM CYA Corp · United States · info@teremu.com
Relationship with MTM and other group products
MTM builds and operates several of its own software products; Teremu is one of them. You can find the company at mtmcya.com. Because all of those products share a team, infrastructure, and internal support, administration, and billing functions, authorised MTM personnel may access data processed through Teremu for those purposes. That internal access is not a disclosure to a third party: it remains under MTM’s control and responsibility, with the same safeguards described here.
Each MTM product keeps its own site, its own privacy notice, and its own systems. We do not merge or cross-reference your profile between different products for commercial or advertising purposes.
What this policy covers
This policy applies to the teremu.com marketing site — the public pages, the blog, and the contact and demo forms — and to the Teremu application (app.teremu.com and the mobile apps), including the integrations you choose to connect from it. It is the only published version: the privacy-policy links inside the app lead to this same page. The rules for using the service are in the terms of service, which complement this document.
What we collect
We collect data in four situations, and no others:
When you submit a form
The contact and demo-request forms collect your name, email address, and message. You may optionally add your restaurant name, a phone number, and your number of locations. We send that to our internal inbox and email you a confirmation. Please do not send sensitive data or third-party confidential information through these forms — they are not the right channel for it.
When you browse the site
If you accept analytics, Google Analytics records aggregate usage data — page views, approximate origin, device type, time on page — so we can tell which content is useful. reCAPTCHA Enterprise analyses browser signals at the moment you submit a form to tell people from bots.
When you use the app
When you create an account we store your name, email address, and sign-in credentials (managed by Firebase Authentication). To provide the service we process the data you enter about your restaurant: the location’s name and address, the invoices you scan or import and what they contain (supplier, line items, prices, dates), your recipe costings, menu, and inventory, the orders imported from your POS, and the names, emails, and roles of the team members you invite. Invoices may include your suppliers’ contact details; you decide what you upload and we process it on your behalf to provide the service.
Server logs
Our hosting provider automatically logs requests to the site and the app (IP address, timestamp, resource requested, user agent). These are necessary to serve pages, diagnose incidents, and prevent abuse, and are kept for a short period.
What we do not collect
We build no advertising profiles, use no social-media pixels, buy no contact lists, and collect no special categories of data (health, beliefs, biometrics) through the site or the app.
Integrations and AI processing
Inside the app you can turn on features that involve third parties. None is active until you connect it, all are read-only, and all can be disconnected from Settings. This is exactly what each one does:
Importing invoices from Gmail
If you connect your Gmail account, Teremu requests only Google’s read-only permission (gmail.readonly). With it, Teremu reads the last 31 days of mail once and, from then on, only new mail, to find supplier invoices. Documents it identifies as invoices enter the same review flow as a scanned invoice; everything else is discarded without being stored. Teremu never sends, modifies, labels, or deletes messages in your account.
Teremu’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. That data is used only to extract invoices and show them to you; it is not used for advertising, it is not sold, and no human reads it except with your explicit permission, for security purposes, or where required by law.
You can disconnect Gmail at any time from Settings or revoke access from the security settings of your Google account. Either way, we delete the access token. Invoices already imported are kept as part of your restaurant’s records, just like a scanned invoice, until you delete them.
AI processing
Three features use language models: invoice data extraction (the document’s image or text), menu and recipe suggestions, and the built-in kitchen assistant (your question together with the restaurant data needed to answer it). For that we send the information to model providers acting as processors on our behalf, whose terms prohibit using your data to train their models. Data derived from Gmail — any invoice imported from your connected inbox, whether read as text or as a page image — is processed only by Google (Gemini on Google Cloud Vertex AI, within our own Google Cloud project) and is never sent to any other AI provider.
Everything the AI returns is an estimate: the extracted amounts, units, and suppliers, and the pricing or recipe suggestions, are presented for you to review before you approve them. Nothing enters your records without your confirmation.
External AI assistants
The restaurant owner can connect Teremu to an external AI assistant — for example Claude or ChatGPT — through the MCP protocol. That assistant can then query the restaurant data the connecting user is allowed to see, and sends it to the assistant’s provider under that provider’s privacy policy, not ours. The connection is read-only: the assistant cannot create or change anything in Teremu.
You can revoke the connection at any time from Settings. We log which tools each assistant queries so you can check what data it has read.
Point of sale (POS)
If you connect your POS — Square today — Teremu imports the sales recorded there to compute your revenue and set it against your costs. We change nothing in the POS. You can disconnect it from Settings; sales already imported are kept as part of your records.
Billing and payments
Payments are processed by Stripe. Teremu never sees or stores your card number: you enter it directly with Stripe. Stripe collects your billing address and, for European Union businesses, your VAT identification number, and uses them to compute the applicable sales tax or VAT. Prices are shown exclusive of tax. We keep invoice and payment history for as long as tax and accounting rules require.
Legal basis and purpose
If you are in the EU, EEA, or UK, we process your data on the following GDPR bases:
- Forms: pre-contractual steps at your request (Art. 6(1)(b)) — we answer what you asked.
- Account, restaurant data, billing, and AI processing: performance of the contract (Art. 6(1)(b)) — it is the service you signed up for.
- Optional integrations (Gmail, POS, external assistants): your consent when you connect them (Art. 6(1)(a)) — withdraw it by disconnecting them.
- reCAPTCHA and server logs: legitimate interest (Art. 6(1)(f)) — keeping the service available and protecting our forms from automated abuse.
- Google Analytics: consent (Art. 6(1)(a)) — you can decline or withdraw without losing functionality.
- Keeping invoices and correspondence and responding to lawful requests: legal obligation and legitimate interest (Art. 6(1)(c) and 6(1)(f)).
We never sell personal data, do not rent it, and do not use it for third-party advertising.
Where processing rests on your consent, you may withdraw it at any time: analytics from the “Cookie preferences” link in the footer, and integrations from Settings. Withdrawal does not affect the lawfulness of processing carried out beforehand.
Who we share data with
We do not sell or rent your data. We rely on the following providers, who process it on our behalf and on our instructions:
- Google Cloud and Firebase (Hosting, Cloud Functions, database, file storage, authentication, Analytics, reCAPTCHA Enterprise) — hosting of the site and the app, form processing, measurement, and abuse prevention.
- Amazon Web Services (Simple Email Service), through MTM’s shared mail service — delivery of notification, confirmation, and digest emails.
- Stripe — subscription payments, billing address, and tax calculation.
- Google Maps Platform — looking up your restaurant during account setup.
- Google (Gemini on Vertex AI) — invoice data extraction, menu and recipe suggestions, and the kitchen assistant. Invoices imported from a connected Gmail inbox are processed only by Google.
- MTM CYA Corp and its authorised personnel — support, administration, and commercial management, as described above.
The services you connect yourself — your Gmail account, your POS, or an external AI assistant — are not our processors: they are providers you chose, and they handle your data under their own policies. Choose carefully what you connect.
We may also disclose data where strictly necessary to comply with a legal obligation or a valid request from a competent authority, to establish or defend legal claims, or in connection with a merger, acquisition, or corporate reorganisation — in which case we would tell you before your data became subject to a different policy.
These providers may process data outside the EEA, principally in the United States. Google, Amazon Web Services, and Stripe rely on the European Commission’s Standard Contractual Clauses and on the EU-U.S. Data Privacy Framework for those transfers; with our other providers we sign equivalent clauses. MTM, as a U.S. entity, processes data in the United States under the same contractual safeguards.
Cookies and similar technologies
The site sets no first-party cookies. Google Analytics loads only if you accept the cookie notice — until then no measurement script runs and none of its cookies are set. Your choice is saved in your browser’s local storage, not a cookie, so we do not ask again; clearing the site’s data removes it. reCAPTCHA Enterprise loads only at the moment you submit a form and may set third-party cookies for bot detection; it is a strictly necessary security measure without which the forms cannot work. The app uses only the storage strictly necessary to keep you signed in.
You can change or withdraw your decision at any time from the “Cookie preferences” link in the footer, and block or delete cookies in your browser settings. The site keeps working, though forms may stop submitting if you block reCAPTCHA. We honour browser privacy-preference signals where applicable law requires it.
How long we keep data
We keep each item only for as long as the purpose that justified it requires:
- Form messages: for as long as needed to handle your enquiry and any resulting business relationship, up to 24 months from last contact.
- Your account and restaurant data: while the account is active. After cancellation you can export it for 30 days; then we delete it.
- Access tokens for integrations (Gmail, POS, external assistants): deleted as soon as you disconnect the integration or revoke the permission with the provider.
- External-assistant query logs and mail discarded by the Gmail import: the log is kept for a limited period so you can audit it; discarded mail is never stored.
- Google Analytics data: 14 months, in aggregate.
- Server logs: a short period, per our hosting provider’s standard configuration.
Once those periods pass we delete or anonymise the information, unless a legal obligation — for instance keeping invoices for tax purposes — or the defence of a claim requires us to keep it longer.
Your rights
You may at any time request access, rectification, erasure, restriction, portability, or object to processing, and withdraw consent. Email info@teremu.com and we will respond within 30 days. We may ask for additional information to verify your identity before acting on a request; we use it for that purpose only.
Exercising these rights is free. We will not treat you differently or deny you any service for having done so.
If you believe we have not handled your request properly, you may lodge a complaint with your national supervisory authority. In Spain that is the Agencia Española de Protección de Datos (aepd.es).
United States residents
If you live in California or another state with consumer privacy legislation, you also have the right to know, access, correct, and delete the personal information we hold about you, and not to be discriminated against for exercising those rights. You can exercise them through the same channel above and, if you prefer, through an authorised agent.
We do not sell personal information and do not share it for cross-context behavioural advertising, as the CCPA/CPRA and equivalent state laws define those terms. Nor do we process sensitive personal information to infer characteristics.
Automated decision-making
We make no decisions producing legal effects about you based solely on automated processing, and we do not profile you for that purpose. AI results are estimates that you review and approve, and a reCAPTCHA score only determines whether a request is accepted as legitimate; if a submission is blocked in error, write to us and we will handle it manually.
Security
The site and the app are served entirely over HTTPS. Service credentials live in Google Secret Manager and never appear in code. Tokens for the integrations you connect are stored encrypted and used only by the server. Access to restaurant data and to the inbox receiving form submissions is limited to authorised personnel. No system is infallible: if a breach occurred that posed a high risk to your rights, we would notify you and the competent authority within the deadlines the law sets.
Minors
Teremu is aimed at restaurant professionals and is not directed at anyone under 16. We do not knowingly collect data from minors. If we find we have received a minor’s data without the necessary authorisation, we will delete it; if you are a parent or guardian and believe this has happened, please write to us.
Links to third-party sites
This site may link to pages we do not control, including mtmcya.com and the sites of other MTM products. Each has its own privacy notice, and we are not responsible for their content or processing practices.
Changes to this policy
If we change this policy we will update the date shown above. Material changes will be announced prominently on the site or in the app and, where the law requires it, we will ask for fresh consent. We encourage you to review this page periodically.
Questions?
Email info@teremu.com and a human will reply. No endless forms.