Legal document

Privacy Policy

This Policy explains what personal data Zyntello, S.R.L. processes through its app.zyntello.com platform and its website, for what purpose, who it shares it with, how long it keeps it and how you can exercise your rights, including the deletion request.

Last updated: 18 September 2026 In force: from its publication Version: 1.9 — see change log Original language: Spanish
This is a courtesy translation. The binding version of this document is the Spanish one. Read the Spanish version.

1. Data controller

Zyntello, S.R.L., a company incorporated and domiciled in the Dominican Republic, with commercial and support operations in the Dominican Republic, Venezuela, Colombia, Guatemala and Costa Rica.

This Policy forms an integral part of our Terms of Service.

2. Our dual role: controller and processor

Zyntello is a multi-company business software platform. That is why we act in two distinct roles, and it determines who you should exercise your rights with:

RoleOver what dataWho decides its use
Controller Subscriber account data: name, email, phone, credentials, billing details and technical usage records. Zyntello. This Policy applies directly.
Processor Data each Subscriber uploads about their own customers, employees, suppliers, residents, debtors or participants. The Subscriber. Zyntello only hosts and processes it in order to provide them the service.

If you are a customer, employee, resident, debtor or participant of a company that uses Zyntello, that company is the controller of your data and you must exercise your rights with them. If you write to us directly, we will route your request to that company and help them handle it, but we cannot decide on their behalf about data that is not ours.

3. What data we process and what for

CategoryDataPurposeLegal basis
Account and users Name, email address, irreversibly hashed password, role, permissions, company they belong to. If the User enables two-step verification: their authenticator app key (encrypted), their recovery codes (irreversibly hashed) and the record of failed attempts. None of this data is readable by Zyntello. Creating and managing the account, authentication, two-step verification (by email or authenticator app), access recovery, access control. Performance of the contract
Billing Legal name, tax identification, address, country, subscription and payment history. Charging the subscription, issuing receipts and meeting tax obligations. Contract and legal obligation
Payments We do not store full card numbers. Processors share only references with us: transaction identifier, charge status and last digits. Processing payments and managing the subscription. Performance of the contract
Subscriber operating data Everything the Subscriber records in their modules (see section 4). Providing the contracted service. Processed as a processor. Subscriber instructions
Technical records IP address, browser, device, date and time, actions performed (audit log). Security, fraud prevention, traceability of actions, support and diagnostics. Legitimate interest
Cookies Session cookie, form protection token and, if the user chooses, a remembered-session cookie. No advertising or third-party tracking cookies. Keeping you signed in and protecting the application. Strictly necessary
Support and contact Name, email, phone and the content of the message sent from the website form or by WhatsApp. Handling sales and support enquiries. Consent and pre-contractual steps
Marketing Email address and a record of the date, time and source of consent. Sending news and commercial communications, only with prior consent. Consent

The legal bases are expressed using the terminology of the European Union's General Data Protection Regulation because it is the most precise; the equivalent concepts apply under the local laws listed in section 10.

4. Data by module

Each Subscriber decides what information they upload. These are the categories each module allows them to record, always processed by Zyntello in the capacity of processor:

ModuleData categories
Invoicing · Accounts Receivable · CRM · Cash RegisterName or legal name, tax identification, address, phone, email, purchase and collection history, credit terms, balances and sales management notes.
Purchasing · Accounts PayableSupplier data and their contacts, tax identification, bank accounts for payment, withholdings and tax documents received.
Payroll · PSAEmployee identification, identity document, date of birth, sex, address, job title, pay and deductions, bank accounts, social security, dependants, absences and supporting documents, timesheets, clock-in and clock-out records and, where the employer enables those checks, geographic location and a photograph of the face.
Zyntello EventsName, identity document, email, phone, organisation, photograph where captured, and access and attendance records.
CondominiumsResident and owner data, unit, ownership share, account statement, common-area bookings, incident reports with photographs and votes at general meetings.
PrestamelloApplicant and guarantor data, identity documents, declared income and outgoings, assets, references, credit bureau search results, collateral and its documents, payment history and the geographic location of collection staff on their rounds.
Route PlannerCustomer delivery and visit addresses and their geographic coordinates; carrier, vehicle and assigned driver data; and, where the Subscriber enables tracking, the driver's location recorded repeatedly throughout the working day (every 30 seconds by default), together with the arrival and departure time at each stop and the outcome of each delivery or visit.
Car WashCustomer and vehicle data: plate, make, model, colour, odometer, photographs of the vehicle and service history.
ConstructFlowStaff assigned to a site, documents and progress photographs.
Inventory · Fixed AssetsAsset owners and custodians, stocktake and physical inventory records.
Accounting · BankingCompany bank accounts, payees of cheques and transfers, and journal entries referring to third parties.

Data of special impact. The Payroll, PSA, Prestamello and Route Planner modules allow the processing of identity documents, pay, information related to health-related absences, photographs of the face, staff geographic location and credit history. It is the Subscriber's responsibility to inform the data subjects beforehand, to have a legal basis or consent, and to enable only the checks that are strictly necessary.

Continuous tracking of a worker's location. Two things worth telling apart, even though both are location. In Payroll, PSA and Prestamello what is recorded is a single point at a specific moment: when clocking in or out, when attending a work order or when handling a collection. The Route Planner, by contrast, can record the driver's position repeatedly for as long as the route lasts, which makes it possible to reconstruct their day's journey. That is a more intrusive form of processing and is therefore switched off by default: it only works if the Subscriber turns it on and the driver starts the route from their device. Before enabling it, the Subscriber must tell the person affected what is recorded, for how long and what for, and must have a legal basis or their consent. Outside the working day or the route, no location is recorded.

Public lookup portals. Some modules generate links or QR codes that can be consulted without signing in (the status of a job, a resident's account statement, an event ticket, an asset record). They are reached through a random identifier, show only the minimum information needed, and whether they are enabled is up to the Subscriber.

5. Who we share data with

We do not sell, rent or transfer personal data to third parties for advertising purposes.

We share data only with the following recipients and for the purposes stated:

RecipientWhat they receiveWhat for
Hosting provider (United States)The data hosted on the Platform and its backups.Infrastructure, storage and backup.
StripePayment transaction data.Processing subscriptions and online payments. Policy
PayPalPayment transaction data.Processing subscriptions and online payments. Policy
Mercado PagoPayment transaction data.Processing online payments. Policy
WhatsApp / Meta PlatformsThe recipient's phone number and the content of the message, only if the Subscriber enables the integration.Sending messages initiated by the Subscriber. Policy
Outbound email providerThe recipient's address and the content of the message.Delivery of transactional emails and documents.
Artificial intelligence providersThe image or text of the document to be read, when the Subscriber enables that feature with their own credentials.Assisted extraction of invoice data (see section 16).
Tax authoritiesThe tax document data required by law.Validation and transmission of electronic tax documents.
Credit bureausThe applicant's identification, using the Subscriber's own credentials and under their own authorisation.Credit history searches in the Prestamello module.
Map provider (OpenStreetMap, Google Maps, HERE or Mapbox, as the Subscriber chooses)The addresses and coordinates of a route's stops. Neither the customer's name nor the contents of the order are sent to them.Turning an address into coordinates, calculating distances and plotting the journey, when the Subscriber uses the Route Planner.
Web3FormsName, email and message from the website form.Delivering sales enquiries to our mailbox.
Content delivery networks and web fonts (jsDelivr, Cloudflare cdnjs, unpkg, Google Fonts and Bunny Fonts)The device's IP address, the browser and the screen the resource is requested from. They do not receive account data, screen contents or session identifiers.Delivering to the browser the libraries, fonts and icons that make up the interface. They load on every screen of the Platform. The detail of each component is in the Third-party software notices.
QuickChartAn event's public registration link. No personal or account data is sent to them.Generating the QR code image for an event when the Platform cannot compose it by itself. Only in the Events module.
Exchange rate service (exchangerate-api)The IP address of the visitor to the public website zyntello.com. It plays no part in the Platform.Showing converted prices on the solutions page.
Competent authoritiesStrictly what a valid legal order requires.Compliance with legal obligations.
Professional advisersStrictly what is necessary.Accounting, auditing and legal defence.

All providers act under their own confidentiality and security commitments. The credentials the Subscriber configures to integrate with third parties are stored encrypted in our database.

The last three recipients receive nothing that we send them. When a screen needs a font or a library served from a third party's server, it is the user's own browser that requests it directly, and that request carries their IP address, as with any visit to a website. It is inherent to loading an external resource: it is not a transfer of data that Zyntello decides to make with account information, and that is why these providers see no customer, no invoice, no employee and nobody's session.

They are declared because they receive a piece of personal data —the IP address— and because the subscriber has a right to know, not because there is any flow of business data towards them.

6. WhatsApp and Meta

The Platform lets the Subscriber communicate with their own contacts through WhatsApp, in two ways: via a conversation link the Subscriber opens manually, or via the WhatsApp Business API when the Subscriber configures their credentials.

6.1. What is transmitted

When a message is sent, the recipient's phone number and the content of the message are transmitted, which may include the contact's name, a document's number and status, amounts, and links to documents or lookup portals.

6.2. Who is responsible

The Subscriber is the sender and the one responsible for the message: they determine its content, its recipients and its purpose, and must have the recipient's prior consent to contact them through that channel. Zyntello does not send commercial communications to its Subscribers' contacts on its own initiative.

6.3. Purpose of the messages

Messages sent from the Platform are operational or transactional in nature: invoices and quotes, receipts and vouchers, account statements, payment and maintenance reminders, queue or service-status notices, meeting calls and approval notifications.

6.4. Right to opt out

If you receive messages from a company that uses Zyntello and do not wish to keep receiving them, you can reply asking to opt out, block the number, or tell that company directly, and they must act on it immediately. The Platform provides mechanisms to record that preference per contact. If you need help identifying the sender, you can write to us at info@zyntello.com and we will point you in the right direction.

6.5. Applicable policies

The processing of information by WhatsApp LLC and Meta Platforms, Inc. is governed by their own policies, including the WhatsApp Privacy Policy and the WhatsApp Business Policy. Zyntello does not control the processing carried out by those companies.

7. International transfers

Our servers are hosted in the United States. By using the Platform, data is transferred to and stored in that country. The payment processors, the outbound email provider, WhatsApp and Meta, and the artificial intelligence providers may also process data outside the Subscriber's home country.

The same applies, to a lesser extent, to the content delivery networks and web font providers in section 5: their servers are spread around the world and the browser connects to the nearest one, so the user's IP address may be processed outside their country. It is the only data they receive.

For data subjects covered by the European Union's General Data Protection Regulation, these transfers rely on standard contractual clauses or on whatever transfer mechanisms each provider has in place. You can ask us about the applicable mechanism by writing to info@zyntello.com.

8. Retention periods

DataRetention period
Subscriber account and operating dataFor as long as the subscription is active, plus 30 days after termination to allow export. They are then deleted.
Billing data and tax documents10 years, or whatever period the applicable tax rules impose if different.
Position history of a route (Route Planner)90 days from the closing of the route. After that only the route summary is kept —stops, arrival and departure times, distance and the outcome of each delivery or visit—, which is what compliance reports need, and the point-by-point trail is deleted, which is the data that would allow a person's journey to be reconstructed. If the Subscriber does not enable tracking, no position history is generated at all.
Technical records and audit log12 months, unless they are needed longer to investigate a security incident.
Demonstration accountIt is deleted automatically every day by a scheduled process.
BackupsA 30-day rotation cycle. Deleted data disappears from the backups once the cycle completes.
Self-service backups downloaded by the SubscriberThe 5 most recent are kept on the server; earlier ones are deleted. The record of their generation and download is kept for the duration of the subscription. Copies already downloaded remain under the Subscriber's sole control (see 9.4).
Record of marketing consent and opt-outFor the duration of the relationship, plus 5 years as evidence of the consent or the opt-out.
Rights requests and our response3 years from being handled, as evidence of compliance.

9. Your rights and data deletion

9.1. Rights you can exercise

You may request at any time:

  • Access: to know what data of yours we process and for what purpose.
  • Rectification: to correct inaccurate or incomplete data.
  • Erasure or cancellation: to delete your data when it is no longer needed.
  • Objection: to object to processing based on legitimate interest.
  • Portability and restriction of processing, where the applicable law provides for them. If you are the Subscriber, you can exercise portability yourself and at any time from Settings → Data backup (see 9.4).
  • To withdraw a consent given previously, without retroactive effect.

9.2. How to exercise them

Write to info@zyntello.com from the registered email address or proving your identity, clearly stating which right you are exercising. We will reply within a maximum of 15 working days (or one month if the European Union's General Data Protection Regulation applies to you).

9.3. Request for data deletion

Detailed instructions on their own page: zyntello.com/eliminacion-datos/ — it covers the step-by-step procedure, the deadlines, what is deleted, what must be kept by legal obligation and how to stop receiving messages.

To request the deletion of your personal data, send an email to info@zyntello.com with the subject “Data deletion request”, stating:

  • your full name;
  • the email address or phone number you registered with or were contacted on;
  • where applicable, the name of the company that contacted you or registered you on the Platform.

We will acknowledge receipt and process the request within a maximum of 30 days. We will inform you of the outcome in writing, including what data was deleted and what we must keep by legal obligation.

If your data was uploaded by a Subscriber company —because you are their customer, employee, resident, debtor or participant— that company is the data controller. In that case we will route your request to them, let you know, and help them handle it, but the final decision on deletion rests with that company.

Limits. Erasure does not apply to information we must keep by legal, accounting or tax obligation (for example, tax documents already issued), nor to what is needed to defend legal claims. In those cases the data is blocked and its processing restricted until the legal retention period expires.

If you believe your rights were not properly handled, you may lodge a complaint with the data protection authority or the competent court in your country.

9.4. Self-service backup and portability

The Subscriber can generate and download, whenever they want and without asking, a complete copy of their companies' data from Settings → Data backup. The file is a ZIP containing the dump in SQL format, a manifest detailing what was included, and restore instructions.

Guaranteed isolation. The file contains only the rows of the Subscriber generating it. It is not a dump of Zyntello's database and under no circumstances does it include information from other Subscribers. Also excluded is the technical data common to the whole Platform —sessions, recovery tokens and notifications—, which belongs to no Subscriber in particular. The file itself states which tables were omitted and why.

Responsibility for the downloaded copy. Once downloaded, the file is under the Subscriber's sole control, and they become responsible for safekeeping it, for encrypting it if they judge it necessary, and for deleting it. Zyntello cannot recover, trace or erase copies that have already left the Platform. If the file contains personal data of third parties —customers, employees, residents—, the Subscriber remains the controller of its processing under section 2.

Generated backups are kept on the server only so they can be downloaded: the 5 most recent per Subscriber are kept and earlier ones are deleted. The record that a backup was generated and downloaded is kept, so that the exercise of portability can be evidenced.

10. Rules by country

  • Dominican Republic — Law No. 172-13 on the Protection of Personal Data: rights of access, rectification, cancellation and objection; claims before the competent courts.
  • European Union and European Economic Area — Regulation (EU) 2016/679 (GDPR), where applicable: the legal bases in section 3, the extended rights in section 9, breach notification to the supervisory authority within 72 hours, and the right to complain to the local supervisory authority.
  • Colombia — Law 1581 of 2012 and its implementing decrees (the habeas data regime): enquiries and complaints under the procedures of the Superintendence of Industry and Commerce.
  • Costa Rica — Law 8968 on the Protection of the Individual with regard to the Processing of their Personal Data (PRODHAB).
  • Venezuela — the constitutional right of habeas data (article 28 of the Constitution) and applicable rules.
  • Guatemala — in the absence of a general data protection law, the constitutional guarantees apply, together with this Policy as an enforceable contractual commitment.
  • Mexico, where applicable — the Federal Law on the Protection of Personal Data Held by Private Parties: rights of access, rectification, cancellation and objection, through the contact in section 1.

In the event of conflict, the mandatory rule of the data subject's country prevails.

11. Security

We apply technical and organisational measures proportionate to the risk, among them:

  • passwords stored with robust hashing algorithms, never in plain text;
  • encryption of traffic in transit using TLS;
  • strict data isolation between subscribers and between companies of the same subscriber, applied automatically on every query;
  • access control with two distinct scopes: the Subscriber's own users reach every company in the account with the permissions of their role, whereas internal users —intended for temporary or external staff— are assigned to a single company, and their permissions, configured module by module, reach only that company's data;
  • two-step verification that the user can enable, by email or through a phone authenticator app (TOTP standard), with single-use recovery codes, temporary lockout after several failed attempts, and an email notice of any change to it;
  • database encryption of third-party integration credentials;
  • an audit log of actions on documents and settings;
  • periodic backups with integrity verification and a copy off the main server;
  • the Subscriber's self-service backup applies the same isolation: it is built by filtering their rows alone, excludes the technical data common to the Platform, and states in its manifest what was left out;
  • the session ends when the browser is closed, and in any case expires on the server after seven days;
  • a connected devices screen from which the user can remotely close sessions open on other machines.

No system is completely foolproof. Should a breach affecting your data occur, we will notify it in accordance with section 14.

12. Access by Zyntello support staff

To handle an incident it may be necessary for a Zyntello support agent to enter the Subscriber's workspace and see their data. This section explains the limits under which that happens and how the Subscriber can check it for themselves.

  • On what basis. It is an operation necessary to perform the service contract: without it we could not diagnose or fix a fault affecting the Subscriber's data. Zyntello acts here as processor, following the instructions of the Subscriber, who is the controller (see section 2).
  • Under what identity. The agent never uses the username or password of a person at the Subscriber. They sign in with a separate technical account, and every action is signed with the name of the actual agent, not that of the technical account nor that of a customer's user.
  • With what scope. The support session starts read-only. To change any data the agent must elevate it by stating a specific reason, and that elevation expires on its own after 30 minutes.
  • What is recorded. For each access we store the agent, the date and time of entry and exit, the stated reason, the IP address, whether the access was authorised by the Subscriber or was an emergency, and —if the session was elevated— the detail of every piece of data changed.
  • Emergency access. When prior authorisation cannot be obtained and the incident demands it, the agent may enter by stating the reason. That access is flagged as unauthorised and the account owner is notified.
  • How the Subscriber audits it. The account owner can consult the full history at any time under Settings → Support access, without having to ask us for it.
  • What we do NOT do. We do not access a Subscriber's data for commercial, statistical or model-training purposes, and we do not extract copies of their information beyond what is needed to resolve the incident.
  • Credential handling. The technical account cannot be used by typing credentials: it only opens from the support tool itself, which requires the agent to have verified their identity in two steps.

12.1. The help desk and its attachments

When the Subscriber opens a support case, the subject, the description, the whole subsequent conversation and the files they attach are stored.

  • The attachment is what demands most care. To explain a problem it is common to attach a screenshot of the system itself, and personal data of the Subscriber's customers or employees can appear there: names, identification numbers, amounts or balances. Zyntello processes that information as a processor, solely to resolve the case.
  • They are kept in private storage, not reachable by a public address: to download a file you must be signed in and belong to the Subscriber who owns the case.
  • Share only what is needed. If a screenshot contains data that is not needed for the diagnosis, we recommend masking it before attaching. The Subscriber decides what they send.
  • Internal notes. The support team may add working notes to the case that the Subscriber does not see —preliminary diagnoses, internal coordination—. They form part of the case file and are kept with it.
  • Retention. Cases and their files are kept for the duration of the contractual relationship and for the general period in section 8; they are then deleted along with the rest of the Subscriber's data.
  • Email sent to support enters the system. A message addressed to soporte@zyntello.com is added automatically to the case: its text and any attached files are stored in the file, with the same handling and the same protections described above. We point this out because an email is written with less caution than a form, and it usually drags along the previous thread and attachments that were sent for something else. The quoted previous message is trimmed so as not to duplicate information, and a file exceeding the permitted size is not stored: its name is noted in the case so the agent can request it another way.
  • The artificial intelligence assistant. The platform includes an assistant that answers questions about how to use it. When you ask it something, only two things are sent to an artificial intelligence provider (Anthropic, acting as a sub-processor): the text of your question and Zyntello documentation about the module you are asking from.
    • NO data about your business or your customers is sent. No names, no amounts, no balances, no records from your database. The text that is sent is built exclusively from our manuals: the component that assembles it does not query the database, and that is verified by an automated test that fails if it ever did.
    • The only thing of yours that travels is what you write in the question. That is why we ask you not to include third parties' personal data in it: to explain how an invoice is issued you do not need the customer's name.
    • Answers are stored so the provider is not queried again for the same question. That store contains only usage questions and answers based on our documentation.
    • The assistant performs no actions and does not change your information: it only explains.
  • Emails that cannot be identified. If a message arrives at the support mailbox and it cannot be determined which Subscriber it comes from —because the sender does not match any registered user—, it is not added to any case: it stays in a separate review inbox, apart from any Subscriber's data, precisely so as not to add information of unverified origin to a customer's account. An email can forge its sender, and that is why the message saying so is not enough.

13. Communications and marketing

  • Transactional communications (identity verification, access codes, billing notices, security alerts, maintenance notices and contractual changes) are sent as part of the service and require no additional consent while a contractual relationship is in force.
  • Zyntello's commercial communications (news, newsletters, offers) are sent only with prior consent, collected through an unticked box. We keep a record of when and how it was given.
  • Opting out: every commercial email includes a one-click unsubscribe link. You can also request it by writing to info@zyntello.com. The opt-out is processed within a maximum of 72 hours and does not affect the service's transactional communications.
  • Communications sent by Subscribers: if a company that uses Zyntello sends you messages by email or WhatsApp, that company is responsible for having your consent and for acting on your opt-out (see section 6).

14. Cookies

The Platform uses only cookies that are strictly necessary for it to work:

  • Session cookie: keeps the user authenticated while browsing.
  • Form protection token: prevents fraudulent requests being submitted from third-party sites.
  • Remembered-session cookie: only if the user ticks that option when signing in.
  • Last location preference: allows work to resume where it was left when the session is picked up again.

We do not use advertising, profiling or third-party tracking cookies, nor do we embed social media or ad platform pixels in the Platform. For that reason no cookie consent banner is required for its use.

You can delete or block cookies from your browser settings, bearing in mind that doing so will prevent you from signing in to the Platform.

14.1. Resources served from third parties

A different matter from cookies, and one worth not confusing with them: some of the fonts, icons and interface libraries are served from the third-party servers listed in section 5. None of them installs cookies or returns any user identifier to us, but the connection exists, and the user's IP address travels in it.

We say so because the absence of advertising cookies is not the same as the absence of third-party connections, and a policy that spoke only about cookies would leave out what actually happens when a screen opens.

15. Security incident notification

If a security breach affecting personal data occurs, we will assess the risk and notify:

  • the affected Subscribers, without undue delay, with the information available on the scope, the categories of data compromised and the measures taken;
  • the competent authorities where the law requires it —within 72 hours of becoming aware, in the case of the GDPR—;
  • the data subjects, where the breach entails a high risk to their rights and freedoms and the applicable law requires it.

Where we act as processor, the notification is addressed to the controlling Subscriber, who is responsible for informing the data subjects and the authority.

16. Minors

The Platform is intended exclusively for companies and professionals, and is not aimed at anyone under 18. We do not knowingly collect data about minors as users of the service. If a Subscriber records data about minors in the course of their activity, it is their responsibility to have the authorisation of the parents or guardians under the applicable law.

17. Automated decisions and artificial intelligence

Some modules offer artificial intelligence assisted features, mainly the extraction of data from invoices and documents and statistical suggestions based on historical information.

  • We make no automated decisions with legal effects about people. Any assessment with consequences —for example, approving a loan in the Prestamello module— requires the intervention and the decision of a human user.
  • Human review is mandatory: the model's output is presented as a draft and produces no accounting, tax or inventory effects until a user validates it.
  • The feature is optional, is off by default, and requires the Subscriber to enable it with their own credentials from the artificial intelligence provider.
  • We do not use Subscribers' data to train models of our own. Processing by the artificial intelligence provider is governed by the terms the Subscriber has accepted with that provider.

18. Changes to this Policy

We will publish any change on this same page, updating the last-updated date. If the change is substantial, we will notify it by email or through a prominent notice in the Platform at least 30 days before it takes effect. Previous versions are available on request.

19. Contact

For any query or request relating to privacy and data protection:

See also our Terms of Service and the data deletion instructions.

20. Change log

A complete, cumulative record of every version of this Policy since it was first published. Each entry states the version, the date it took effect and what changed. Earlier entries are neither amended nor deleted.

How to read the versions. A minor version change (1.0 → 1.1) adds or clarifies information —a new module, a recipient, a category of data— without altering the purposes or the legal bases of the processing. A major version change (1.x → 2.0) alters purposes, legal bases, recipients, retention periods or your rights, and is notified 30 days in advance under section 17.

VersionDateChanges
1.9 In force 18 September 2026 The third parties that receive the IP address when a screen loads. Section 5 did not declare three recipients that do exist, and they are now included: (1) the content delivery networks and web font providers —jsDelivr, Cloudflare cdnjs, unpkg, Google Fonts and Bunny Fonts—, from which the interface's libraries, fonts and icons are served; they load on every screen of the Platform and receive the IP address, the browser and the screen requested, never account data or session identifiers. (2) QuickChart, which generates the QR code image for an event and receives only the public registration link, in the Events module alone. (3) the exchange rate service queried by the public website, which receives the visitor's IP and plays no part in the Platform. An explanation is added after the table of why these three are not a transfer of business data: it is the user's own browser that requests the resource, and that request carries their IP as in any visit to a website. Section 7 extends international transfers to these providers, whose servers are spread around the world. Section 14.1 clarifies that none of them installs cookies, and that the absence of advertising cookies is not the same as the absence of third-party connections. The technical detail of each component is in the Third-party software notices, published with version 1.7 of the Terms. Purposes, retention periods, data subject rights and the legal bases of processing are unchanged.
1.8 11 September 2026 The Route Planner and tracking a driver's location. The Route Planner module enters section 4, with the data it processes: addresses and coordinates of the stops, carrier, vehicle and assigned driver, and the driver's location during the route. An explanation that was missing, and that is no mere nuance, is added to section 3: recording a point when clocking in —which Payroll, PSA and Prestamello already did— is not the same as recording the position repeatedly throughout the working day, because the second makes it possible to reconstruct a person's journey. It is stated that this tracking starts switched off and that no location is recorded outside the route. Section 5 declares a new recipient: the map provider (OpenStreetMap, Google Maps, HERE or Mapbox, at the Subscriber's choice), to which the addresses and coordinates of the stops are sent —not the customer's name or the contents of the order—. And section 8 sets a retention period of its own for the point-by-point trail: 90 days after the route closes, after which only the summary the reports need is kept and the detailed journey is deleted.
1.7 9 September 2026 The artificial intelligence assistant. Section 12.1 is expanded to declare a new feature and the sub-processor involved: when the assistant is used, only the text of the question and Zyntello documentation for the relevant module are sent to Anthropic. It is expressly stated that NO business or personal data of the Subscriber is sent —no names, no amounts, no balances, no database records— because the component that assembles that text does not query the database, and that this is verified by an automated test that fails if it ever did. It warns that the only thing of the Subscriber's that travels is what they write in the question themselves, states that answers are stored so queries are not repeated and that this store contains only usage questions and answers based on our documentation, and that the assistant performs no actions. Purposes, legal bases, retention periods and data subject rights are unchanged.
1.6 9 September 2026 Email sent to support enters the system. Section 12.1 is expanded with an entry route the previous version did not cover: a message addressed to soporte@zyntello.com is added automatically to the case, and its text and attachments are stored in the file with the same handling and the same protections already described. It is pointed out because an email is written with less caution than a form and usually drags along the previous thread and attachments sent for something else; it is stated that the quoted previous message is trimmed and that a file exceeding the permitted size is not stored, its name being noted instead. It also states what happens with emails whose sender cannot be identified: they are not added to any case, but stay in a review inbox separate from any Subscriber's data, because an email can forge its sender and the message saying so is not enough. Purposes, legal bases, recipients, retention periods and data subject rights are unchanged.
1.5 7 September 2026 The help desk and its attachments. Section 12.1 is added, documenting a category of data the previous version did not cover: the content of support cases and, above all, the files the Subscriber attaches. It makes clear that a screenshot may contain personal data of the Subscriber's customers or employees and that Zyntello processes it as a processor, solely to resolve the case; that attachments are kept in private storage and require being signed in and belonging to the Subscriber who owns the case in order to be downloaded; that the support team may add internal notes that form part of the file; and the retention period. It also recommends masking from the screenshot anything not needed for the diagnosis. Purposes, legal bases, recipients and data subject rights are unchanged.
1.4 6 September 2026 Access by Zyntello support staff. Section 12 is added, documenting an operation the previous version did not describe: when an incident requires it, a Zyntello support agent may enter the Subscriber's workspace and see their data. It specifies on what basis this is done, that the agent never uses the credentials of a person at the Subscriber but a technical account of their own, that the session starts read-only and that elevating it to write requires stating a reason and expires on its own, what is recorded for each access, how emergency access is flagged, and where the Subscriber audits it themselves (Settings → Support access). Sections 12 to 19 of the previous version are renumbered 13 to 20; their content is unchanged. Purposes, legal bases, retention periods and data subject rights are unchanged.
1.3 5 September 2026 Scope of access for each class of user. Section 11 now specifies that access control has two distinct scopes: the Subscriber's own users reach every company in the account with the permissions of their role, whereas internal users —intended for temporary or external staff— are assigned to a single company and their permissions reach only that company's data. The previous wording spoke of “granular roles and permissions by module” without distinguishing how far each one goes. The categories of data processed, the retention periods, the recipients and the data subject rights are unchanged.
1.2 4 September 2026 Two-step verification with an authenticator app, and session policy. Added to the table in section 4 is the data stored when the User enables two-step verification by app: the app key (encrypted), the recovery codes (irreversibly hashed) and the record of failed attempts; none of it is readable by Zyntello. The measures in section 11 are updated with the new method, the temporary lockout after failed attempts and the email notice of any change to the verification. The description of the session policy is corrected, as it said “automatic close on inactivity”: since 3 September 2026 the session ends when the browser is closed, expiring on the server after seven days, and there is a connected devices screen to close them remotely.
1.1 31 August 2026 Self-service backup and portability. This documents the feature that lets the Subscriber generate and download a complete copy of their companies' data by themselves: new section 9.4 (what the file contains, guaranteed isolation from other Subscribers, technical data left out, and responsibility for the copy once downloaded), a mention in 9.1 as a way of exercising portability without a prior request, its own retention period in the table in section 8, and a clarification in section 11 that the backup applies the same isolation between Subscribers. The purposes, the legal bases and the recipients of the processing are unchanged.
1.0 28 July 2026 First publication. Initial document with 19 sections: data controller, dual controller/processor role, data processed and its legal basis, data by module, recipients and sub-processors, WhatsApp and Meta, international transfers, retention periods, rights and the data deletion procedure, rules by country, security, communications and marketing, cookies, incident notification, minors, automated decisions and artificial intelligence, changes to the Policy, contact and change log.

You may request a copy of the full text of any earlier version by writing to info@zyntello.com.