Pular para o conteúdo
14 dias de teste grátis, sem cartão10 idiomas176 tipos de negócio · 50 apps
PT· USD
Experimente uma demonstração ao vivoComeçar teste grátis

Política de privacidade

Quais dados pessoais coletamos, por quê e as escolhas que você tem.

Versão 5 · Em vigor desde 20 de novembro de 2026

1. Who we are

zmle and this website are operated by Zmle Technology, LLC. Registration details: Delaware Division of Corporations; registration number 10827053; formed 2026-11-02; registered agent: Legalinc Corporate Services Inc.. Postal address: 131 Continental Dr, Suite 305, Newark, DE 19713, United States. Privacy questions and requests: support@zmle.com. Data protection officer: none named yet; use the privacy contact above. EU representative (GDPR article 27): none named yet. UK representative: none named yet. Data protection law of the operator's own country: the privacy laws of the United States that apply to it, including the Federal Trade Commission Act and the consumer privacy laws of the states where they apply, such as the California Consumer Privacy Act.

For website visitors, zmle accounts and our own customers we are the controller of personal data. For the data our customers keep in their workspaces (their customers, staff, invoices, bookings and so on) we are their processor, under the Data Processing Agreement (zmle.com/legal/dpa): if you are a customer of a business that uses zmle, ask that business first, because it decides how your data is used. If you write to us about such data we pass your request to the business.

One policy for everyone. This policy applies wherever you are; there is no separate version for a particular country. We use the standards of the EU General Data Protection Regulation (GDPR) and the UK GDPR as the baseline for everyone whose personal data we handle as controller, and section 9 adds what the privacy laws of US states require. Where the law of your country gives you a further right, you have that right as well.

2. What we use, why, and on which legal basis

Using the website: IP address, browser, pages requested, country. To deliver and secure the site. Basis: legitimate interest in a working, secure website.

Site measurement: page, referrer, country, device class. To improve the site. No analytics or advertising tag runs before you consent where consent is required, and a Global Privacy Control signal is honoured. Basis: consent where required, otherwise legitimate interest. A visit from an AI assistant's answer is counted per day and landing page, without a cookie or identifier.

Cookie choices: your choice, its time, and the IP address and browser as keyed hashes. To prove consent. Basis: legal obligation.

zmle account and workspace sign-up: name, e-mail, company, country, password hash, sign-in methods. To provide the account. Basis: contract.

Billing: billing contact, company, tax number, invoices and payments. We do not receive or store card numbers. Basis: contract and legal obligation (tax and accounting).

Billing country and local prices: the country of the internet address of a visitor to our website, used only to show the likely local price and not stored for pricing; and, for a workspace, the country of its business tax number, the issuing country of the card that paid and the country of a local payment method that paid (received from the payment provider, never the card number), and the country chosen at sign-up. These are stored with the workspace to decide its billing country and price, shown to the owner on the Subscription page, and their changes are logged. Basis: contract (charging the right price), legitimate interest in preventing misuse of local prices, and legal obligation (tax evidence).

Automatic renewal consent: who switched automatic card charging on or off and when, how (order review or Subscription page), the exact text shown and its hash, the amount, interval, next date and card label (card brand and last four digits), and the internet address and browser. To prove consent to recurring charges and to handle disputes and chargebacks. Basis: legal obligation (automatic renewal laws) and legitimate interest in establishing and defending legal claims.

Usage meters: counts of the records and of the use of a workspace (for example documents, storage, e-mails sent, AI and API requests), computed from the workspace's own data without reading its content, to apply plan limits and fair use, to send the 80% and 100% notices and to estimate our costs. Basis: contract and legitimate interest in running the service at a sustainable cost.

Cancellations and messages to former customers: the reason chosen when cancelling, an optional note, the offer shown and the outcome; and, after a cancelled term has ended, up to two e-mails about what is new in zmle. To improve the product and to offer our own service again to former customers. Basis: legitimate interest, and for the e-mails the rules for messages to existing customers about similar services where the law allows them without prior consent; otherwise we ask for consent. Every such e-mail has a one-click unsubscribe, and you can object at any time.

Acceptance records: who accepted which version of which document and when, order summary, country, page, and the IP address and browser as keyed hashes. Basis: legitimate interest in proving the contract and defending legal claims.

Contact forms, demo requests, status and newsletter subscriptions: what you send us. To answer, follow up and send what you asked for. Basis: consent, or legitimate interest for business enquiries. You can unsubscribe at any time.

Website chat: what you write in the chat, and the name and e-mail if you give them. To answer you and pass you to a person if you ask. Basis: legitimate interest, or steps before a contract. See section 3.

Support: messages and attachments. Basis: contract.

Security and audit logs: IP address, browser family, country, action. To protect accounts and investigate misuse. Basis: legitimate interest.

Product statistics: when a workspace reached its first steps with zmle (workspace ready, first sign-in, setup steps, first invoice, payment, sale or booking, plan and app changes), stored with the workspace id and at most the user's role, never a name, e-mail address or the workspace's content. To see where new customers get stuck and improve the product. Recorded by zmle itself, without third-party analytics tools, and kept as monthly totals without the workspace id after 13 months. Basis: legitimate interest in improving the service. The workspace owner can switch it off under Subscription at any time, which deletes what was recorded.

Partners, affiliates, marketplace sellers: identity and bank details, referrals, payouts. Basis: contract and legal obligation.

Reports: notices of illegal content and security reports with the reporter's contact details. Basis: legal obligation and legitimate interest.

If you do not give the data a contract needs, we cannot provide the account or service; everything else is optional.

3. AI

The chat on this website is an AI assistant and says so at the start. It answers from our own published information and can pass you to a person. What you write is sent to an AI provider we engage (see the list at zmle.com/legal/subprocessors) to produce the answer, and the conversation is kept as stated in section 6. Please do not write sensitive data in the chat. zmle does not use your data to train AI models; the handling by the provider follows its terms for the account we use.

AI providers that a customer connects to its own workspace with its own keys are that customer's service providers, not ours.

We make no decisions about you based solely on automated processing that produce legal or similarly significant effects, apart from routine automated steps that follow published rules: blocking repeated failed sign-ins and abusive requests, and billing reminders and suspension for non-payment as described in the order terms. You can ask a person to review any of these.

4. Sharing

We share personal data only with service providers that help us run zmle (hosting, e-mail delivery, payment processing, security checks, and the AI providers that answer the chat on this website: what you write in that chat is sent to them to produce the answer), under contracts that protect it, with our advisers, or where the law requires. The current list, with each provider's location, is published at zmle.com/legal/subprocessors. A partner who referred a customer sees that referral and its status. We do not sell personal data and do not share it for cross-context advertising. If advertising tags are ever switched on, they appear in the cookie settings with a way to refuse them.

5. International transfers

Your data may be processed outside your country: where the operator and its staff work (the United States of America (State of Delaware)) and where the listed providers process it. Where data leaves the European Economic Area, the United Kingdom or Switzerland for a country without an adequacy decision, we use the European Commission's standard contractual clauses (Decision (EU) 2021/914), with the UK Addendum or the Swiss adaptations, or another safeguard the law allows. You can ask support@zmle.com for a copy. Where the law of another country also restricts transfers of personal data abroad, we rely on the same safeguards, or on another mechanism that law allows.

6. How long we keep it

How long each kind of website and customer record is kept:

Website chat and live chat: 90 days after the last message.

Site page views: 13 months.

IP addresses in activity logs: cleared after 12 months; the log entry itself stays.

API request logs: 90 days.

Growth and affiliate click records: 400 days.

Contact requests, leads and support conversations: as long as needed to handle them and follow up; there is no automatic deletion period for these yet, so ask us to delete them when you no longer need them. Newsletter and status subscriptions: until you unsubscribe; we keep the address on a suppression list so that we do not write to you again.

Account and billing records: for the life of the account and as long as tax and accounting law requires afterwards. The data of a workspace whose subscription ended is erased 30 days after the owner closed it, or 90 days after the subscription ended in another way (including after 60 days of suspension for non-payment). The export copy made before an erasure is deleted 90 days later, and backup copies within 30 days after the erasure.

Records of who accepted which version of our terms, and consent records, are kept as evidence for as long as legal claims about them can be raised, also after a request to erase other data. This includes the consent records for automatic renewal. The evidence of the billing country (the country of the card, the payment method and the tax number) is kept with the workspace's billing records. Cancellation answers are kept with the workspace's record; there is no automatic deletion period for them yet, so ask us to delete them when they are no longer needed.

7. Security

We protect data with access controls, encryption in transit, hashed passwords, two-step sign-in, audit logs, encrypted backups and separation of each customer's data. No system is perfectly secure. How we protect data, who can see it and what we do not claim yet: zmle.com/security. If a breach is likely to put you at risk we tell you and the competent authority as the law requires.

8. Your rights

Wherever you live, you have the right to access your data and get a copy, to correct it, to delete it, to receive it in a portable form, to restrict or object to its use, to withdraw consent at any time (this does not affect earlier use), and not to be subject to decisions based solely on automated processing that have legal or similarly significant effects on you. Some of these rights have limits set by law, for example where we must keep invoices; if we cannot meet a request we tell you why. You may object at any time to direct marketing.

To use these rights write to support@zmle.com. We may ask you to confirm who you are. We answer within one month, and may extend that where the law allows, telling you why. If you are unhappy, complain to us first at the same address: we acknowledge a complaint within 30 days and tell you the outcome. You can always complain to a data protection authority: in the EEA the one of your own country, in the UK the Information Commissioner, and elsewhere the authority of your country, where there is one.

Deleting an account: you can delete your zmle account yourself on the Security page of My zmle, where you can also export its data; if you own a workspace, close it or hand it over first. A customer account on a business's own website is deleted on that website's account page; invoices and orders the business must keep by law stay there under a pseudonym. Staff accounts belong to the workspace owner: the zmle apps send the owner a deletion request and remove the app's sign-ins and devices at once. How each works: zmle.com/account-deletion.

9. Addendum for residents of US states

United States: where a state privacy law such as the California Consumer Privacy Act applies, you have the rights to know, delete, correct and opt out of sale or sharing, and to limit the use of sensitive data, and we will not treat you worse for using them. In the past 12 months we collected the categories in section 2 (identifiers, commercial information, internet activity, approximate location, professional information, and contents of messages sent to us), for the purposes stated there. We did not sell or share them and do not knowingly sell or share data of anyone under 16. An authorised agent may act for you. A Global Privacy Control signal counts as an opt-out. If we refuse a request you can appeal by replying to our answer.

Other countries: we do not keep a separate privacy policy per country. Everyone has the rights in section 8. If the law of your country gives you a right that this policy does not describe, write to support@zmle.com; we handle the request under that law.

10. Children

zmle's own website and accounts are for adults acting for a business and are not directed at children. We do not knowingly collect children's data for ourselves; if you think we have, write to support@zmle.com and we delete it. A school, nursery or similar business may keep children's data in its workspace: that business is the controller and is responsible for the parental consent and safeguards the law requires.

11. Mobile and desktop apps

The zmle phone app (Android, iPhone) and desktop app (Windows, macOS, Linux) open your workspace. This section says what the apps themselves collect and why. What you enter in a workspace through an app is workspace data like any other: the business that owns the workspace decides about it, and we process it on its behalf (section 1).

Sign-in and secure storage. When you sign in, the app receives your name, e-mail address and user id from the workspace. Its sign-in token is kept in the device's secure storage (Android Keystore, iPhone Keychain or the computer's protected storage); the short-lived access token stays in memory only. On our servers app tokens are stored only as hashes. Android backup of the app's data is switched off. Signing out removes the sign-in, the device and its notification token. Requests of the apps are logged with path, status and IP address for security and deleted after 90 days.

Location and Duty mode. The phone app uses location only while it is in use and never asks for background (“always”) location permission. Couriers, drivers and field technicians share their location only by tapping Start duty: from then until the duty ends, the phone sends its precise position to the employer's workspace. While it does, Android shows a notification “On duty” with an End duty button, and iPhone shows its location indicator. Sharing stops at End duty, at sign-out, and by default after 3 hours without movement or 14 hours of duty.

Who sees the position: staff of that workspace who may see deliveries or field jobs, and the customer waiting for that delivery or visit, who sees an estimated arrival time and, on some tracking pages, the position on a map. The server keeps only the latest position of each person, no route history, and deletes it 30 days after its last update. Some workspace pages also ask for your location once, for a check-in such as a delivery, visit or patrol, only when you use that function. The desktop app does not use location.

Camera and photos. The camera is used only when you choose to: to scan a barcode or QR code, or to take a photo for a record or task. Barcodes are read on the device; only the code is sent to the workspace, no image. Photos you take or pick are uploaded to the workspace, and the server removes their metadata, including any GPS position. The app does not read your photo library; you pick files with the system picker.

Microphone. The phone app does not use the microphone and does not ask for that permission. In the desktop app, the voice input of the business assistant uses the microphone only after you press its microphone button, only to turn your words into text with the AI provider the workspace connected, and the audio is not stored.

Notifications. If you allow notifications, the app registers a notification token for the device, which we store encrypted. To deliver a notification, its title, its text and the token are sent to Google Firebase Cloud Messaging (Android), Huawei Push Kit (Huawei phones without Google services) or the Apple Push Notification service (iPhone). They act as our service providers only for that delivery. You can switch notifications off in the app or in the phone's settings.

Crash and diagnostic reports. The apps contain no crash-reporting, analytics or advertising SDK. When a workspace page in an app hits an error, a cleaned error report without your name, account, IP address or query string goes to our error log so that we can fix it. We count requests and errors per app version, as totals only, to decide whether a new version may reach more people. Libraries from Google (Firebase Cloud Messaging, ML Kit barcode scanning) and Huawei (Push Kit) inside the app may send their own anonymous diagnostic data to Google or Huawei. The desktop app keeps crash reports on the computer and does not send them.

No ads, no tracking. The apps show no advertising, contain no advertising SDK, do not use the advertising ID (Android advertising ID, Apple IDFA) and do not track you across other companies' apps or websites. We do not sell data from the apps.

Deleting your account. In the phone app: Me → Delete account; in the desktop app: Settings → Delete account. For a staff account the app sends the workspace's administrators a deletion request and at once removes every app sign-in, web session, device and notification token of the account; the account and the records of your work belong to your employer, who deletes the account. A workspace owner closes or hands over the workspace instead. How each kind of account is deleted, also without the app: zmle.com/account-deletion.

12. Cookies

Details of every cookie and how to change your choice: zmle.com/legal/cookies.

13. Changes

We may change this policy at any time, for example when our practices, the service or the law change. A change that uses personal data in a new way that you would not reasonably expect, or that reduces your rights, is announced at least 30 days before it takes effect: to workspace owners and account holders by e-mail and in the workspace, and to visitors by a notice on this page. Where the law requires your consent for a new use, we ask for it and do not rely on this notice. Other changes take effect when we publish them. A change may take effect sooner when it is required by law, a court or an authority; when it is needed to protect the security, integrity or availability of the service, of our customers or of other people; or when a provider we rely on (for example a payment, hosting or e-mail provider) changes or ends its own service. We then tell you as soon as we reasonably can, where possible before the change takes effect, and keep the change as small as we can. Every published version of this document stays available, with its effective date and a summary of what changed, at zmle.com/legal/privacy; each version has its own address (zmle.com/legal/privacy/v/1, /v/2 and so on).

Mobile and desktop apps

The English text above is the one that applies.

The zmle phone app (Android, iPhone) and desktop app (Windows, macOS, Linux) open your workspace. This section says what the apps themselves collect and why. What you enter in a workspace through an app is workspace data like any other: the business that owns the workspace decides about it, and we process it on its behalf (section 1).

Sign-in and secure storage. When you sign in, the app receives your name, e-mail address and user id from the workspace. Its sign-in token is kept in the device's secure storage (Android Keystore, iPhone Keychain or the computer's protected storage); the short-lived access token stays in memory only. On our servers app tokens are stored only as hashes. Android backup of the app's data is switched off. Signing out removes the sign-in, the device and its notification token. Requests of the apps are logged with path, status and IP address for security and deleted after 90 days.

Location and Duty mode. The phone app uses location only while it is in use and never asks for background (“always”) location permission. Couriers, drivers and field technicians share their location only by tapping Start duty: from then until the duty ends, the phone sends its precise position to the employer's workspace. While it does, Android shows a notification “On duty” with an End duty button, and iPhone shows its location indicator. Sharing stops at End duty, at sign-out, and by default after 3 hours without movement or 14 hours of duty.

Who sees the position: staff of that workspace who may see deliveries or field jobs, and the customer waiting for that delivery or visit, who sees an estimated arrival time and, on some tracking pages, the position on a map. The server keeps only the latest position of each person, no route history, and deletes it 30 days after its last update. Some workspace pages also ask for your location once, for a check-in such as a delivery, visit or patrol, only when you use that function. The desktop app does not use location.

Camera and photos. The camera is used only when you choose to: to scan a barcode or QR code, or to take a photo for a record or task. Barcodes are read on the device; only the code is sent to the workspace, no image. Photos you take or pick are uploaded to the workspace, and the server removes their metadata, including any GPS position. The app does not read your photo library; you pick files with the system picker.

Microphone. The phone app does not use the microphone and does not ask for that permission. In the desktop app, the voice input of the business assistant uses the microphone only after you press its microphone button, only to turn your words into text with the AI provider the workspace connected, and the audio is not stored.

Notifications. If you allow notifications, the app registers a notification token for the device, which we store encrypted. To deliver a notification, its title, its text and the token are sent to Google Firebase Cloud Messaging (Android), Huawei Push Kit (Huawei phones without Google services) or the Apple Push Notification service (iPhone). They act as our service providers only for that delivery. You can switch notifications off in the app or in the phone's settings.

Crash and diagnostic reports. The apps contain no crash-reporting, analytics or advertising SDK. When a workspace page in an app hits an error, a cleaned error report without your name, account, IP address or query string goes to our error log so that we can fix it. We count requests and errors per app version, as totals only, to decide whether a new version may reach more people. Libraries from Google (Firebase Cloud Messaging, ML Kit barcode scanning) and Huawei (Push Kit) inside the app may send their own anonymous diagnostic data to Google or Huawei. The desktop app keeps crash reports on the computer and does not send them.

No ads, no tracking. The apps show no advertising, contain no advertising SDK, do not use the advertising ID (Android advertising ID, Apple IDFA) and do not track you across other companies' apps or websites. We do not sell data from the apps.

Deleting your account. In the phone app: Me → Delete account; in the desktop app: Settings → Delete account. For a staff account the app sends the workspace's administrators a deletion request and at once removes every app sign-in, web session, device and notification token of the account; the account and the records of your work belong to your employer, who deletes the account. A workspace owner closes or hands over the workspace instead. How each kind of account is deleted, also without the app: zmle.com/account-deletion.

Histórico de versões

Todas as versões publicadas continuam disponíveis em seu próprio endereço.

  • Ler a versão 5

    Publicada em 20 de novembro de 2026 · Em vigor em 20 de novembro de 2026

    O que mudou: Draft for Zmle Technology, LLC (Delaware, United States): governing law and courts of the State of Delaware, the operator's country, US support hours (US Eastern Time, US federal public holidays) and US invoice wording, from the us-de legal profile. Includes the changes of revision 2026-11-02 and, for the privacy policy and the DPA, of revision 2026-11-05 (AI chat providers named as recipients, a retention line per kind of record, support access only with the owner's grant, SCCs or the UK IDTA, the security measures in Annex 2), and, for every document, of revision 2026-11-06 (one rule for changes: 30 days' notice for material changes, from the next renewal for paid subscriptions; the free plan, trials, fair use, add-on packs, optional automatic card charges, local prices, transaction fees, cancellation and pause; customer responsibility for content and lawful use, hosting role, copyright notices, indemnity). The privacy policy also keeps the section on the phone and desktop apps of revision 2026-11-17. Not reviewed by a lawyer: publish only after a US lawyer has read it.

  • Ler a versão 4

    Publicada em 18 de novembro de 2026 · Em vigor em 18 de novembro de 2026

    O que mudou: What changed: a new section on the zmle phone and desktop apps — sign-in and secure storage, location only in Duty mode (started by the person, with a visible notification; who sees it; only the latest position, kept 30 days), camera and photos, microphone, notification tokens and the services that deliver them (Google, Huawei, Apple), crash and diagnostic reports, no ads and no advertising ID, and how to delete an account in the apps. Where it was missing, the policy now also explains how each kind of account is deleted and that AI providers a customer connects to its own workspace are that customer's service providers. Notice only: how the service works does not change and nobody is asked to accept again. Not yet reviewed by a lawyer.

  • Ler a versão 3

    Publicada em 2 de novembro de 2026 · Em vigor em 2 de novembro de 2026

    O que mudou: The end of a free trial and the retention periods now match how the service works: a trial that ends without a paid plan moves to the free plan with one app (other apps switched off, their data kept) instead of being invoiced and paused; no renewal invoices are issued while a workspace is suspended; a subscription suspended for non-payment for too long ends and its data is erased later; the retention periods (including the export copies) are stated with their numbers. Not yet reviewed by a lawyer.

  • Ler a versão 2

    Publicada em 2 de novembro de 2026 · Em vigor em 2 de novembro de 2026

    O que mudou: Clarification: the placeholders of version 1 are filled with standard defaults (governing law, availability target and service credits, support times, refund window, taxes, price-change notice, payment, reminder and suspension timeline, data return and deletion periods, contact details). How the service works does not change. Not yet reviewed by a lawyer.

  • Ler a versão 1

    Publicada em 2 de novembro de 2026 · Em vigor em 2 de novembro de 2026

    O que mudou: First version (template, under legal review).