Product document, published exactly as every Zevli CRM installation serves it.
ZEVLI CRM Privacy Policy
Version 1.5 — September 22, 2026
1. Identification of the Parties and Their Respective Roles
This privacy policy (hereinafter, the “Policy”) relates to ZEVLI CRM (hereinafter, interchangeably, “ZEVLI” or the “Software”), a computer program developed by Tele Network Solutions, LLC, a limited liability company organized under the laws of the State of Florida, United States of America (hereinafter, “TNS”).
The Software is acquired for a one-time payment, under a perpetual license to use the Software (hereinafter, the “License”), by the natural person or legal entity that obtains such License (hereinafter, the “Licensee”), and is installed on the Licensee’s own computer (hereinafter, the “Equipment”), with its own database. The copy of the Software installed on the Equipment, together with such database, is hereinafter referred to as the “Installation”. TNS and the Licensee are hereinafter referred to collectively as the “Parties”.
For the purposes of this Policy, a distinction is made between the members of the Licensee’s staff who use the Software (hereinafter, the “Users”) and the end clients served by the Licensee, whose personal data the Licensee processes by means of the Software (hereinafter, the “Data Subjects”).
The roles of the Parties are allocated as follows:
| Party | Role |
|---|---|
| TNS | Develops the Software. Has no access to the database of any Installation or to the data contained therein. Provides the services described in Section 5.2 and handles the data passing through them solely for the purpose of providing those services. It also processes the Licensee’s own data set out in Section 2.4. |
| Licensee | Is the party answerable for the personal data of Data Subjects. Decides what data is stored, for how long, and with which services the Installation is connected. |
| Data Subject | The person whose data the Licensee stores, such as their name, their case file and their conversations. |
The Licensee decides what data of the Data Subjects is collected, for what purpose, for how long it is retained and with which services the Installation is connected, and the Licensee is the party that maintains the relationship with the Data Subjects and is answerable to them. TNS takes no part in such decisions and handles only the data passing through the services described in Section 5.2, and solely for the purpose of providing those services, without prejudice to the data relating to the Licensee itself referred to in Section 2.4. This Policy describes the roles of the Parties in operational terms and does not assign to either of them any particular legal characterization for the purposes of any specific data protection law.
TNS does not receive a copy of the database of any Installation and cannot access it. Communication between the Installation and TNS infrastructure is limited to the following six cases: the processing of connection permissions with Meta, Google, Microsoft, Stripe, DocuSign and Twilio; incoming messages originating from Meta, where the Meta connection was made through Zevli Connect; authentication emails; technical error reports, for as long as their transmission is not disabled; obtaining the Installation’s licence, where the Licensee so requests; and the transfer of that licence to another Installation, where the Licensee so requests. Those cases are described in Section 5.2, to which reference is made, and the retention periods applicable to each of them are set out in Section 7.2. Outside those cases, no other information from the Installation is transmitted to TNS.
2. Data Stored by the Software
2.1 Users’ Data
The Software stores the following data relating to Users:
- Email address, name, photograph and time zone of each User.
- Role and permissions of each User in each of the companies managed within the Installation (hereinafter, each, a “Company”).
- A record of each User’s activity, indicating who created, modified or deleted each item, and when.
- The devices on which the User receives alerts, if the User enables notifications.
The Software does not store Users’ passwords. Passwords are held in the custody of the Installation’s own authentication system, in hashed and irreversible form.
2.2 Data Subjects’ Data
This category comprises the majority of the data stored, and its scope depends on the Licensee’s business. The Software may store the following data:
- Contact record: name, phone number, WhatsApp, email address, language, country of origin, tags, and the advertisement or form of origin.
- Case files: service type, dates, deadlines, status, amounts and balances. In the case of Licensees that provide immigration services, case files include USCIS forms, biometrics and interview dates, and immigration status.
- Documents: files uploaded by Users or by the Data Subject, such as passports, certificates, medical examinations, police records and tax returns.
- Complete conversations: WhatsApp, Instagram, Messenger, Telegram, SMS and email messages, with their full text.
- Payments: amounts, due dates and payment-provider identifiers.
- Contracts, appointments, quotes and responses to public forms.
2.3 Encrypted and Unencrypted Data
The following data is encrypted within the database using the AES-256-GCM algorithm: immigration status, internal notes and intake form responses.
Conversations, phone numbers, email addresses, names and the remainder of the case file are not encrypted. Such data is protected by the database’s access control, under which each Company may access only its own data, and by the security of the Equipment on which the Installation runs.
Encryption is applied at the time the data is saved. Consequently, data recorded prior to the introduction of this feature was retained in plain text. The Software currently provides, under Settings → General, an option that encrypts such historical records (immigration status, internal notes and form responses) without altering their content. This option does not run automatically; it is for the Licensee to initiate it at such time as the Licensee deems appropriate.
2.4 Licensee Data Processed by TNS
Apart from the data stored in the Installation, to which TNS has no access, TNS processes the following data relating to the Licensee itself:
- The Licensee’s identification and contact details.
- The documentation relating to the License.
- The record of the licence issued to the Installation, which Zevli Connect retains: the identifier of the purchased service, the identifier of the Installation, the purchase email address, the date until which maintenance extends, the date of the last verification of the purchase and, where applicable, the dates of revocation or of cancellation of the purchase.
- Licence transfer requests (Section 5.2): the purchase email address, the language chosen for the confirmation email, the identifiers of the source and destination Installations, a cryptographic fingerprint of the confirmation link—never the link itself—and the dates of request, expiry and confirmation.
Such data is processed solely for the purpose of evidencing the License, of providing the TNS services to the Installation and of complying with the legal, accounting and tax obligations of TNS. The applicable retention period is set out in Section 7.2. Such data does not comprise Data Subjects’ data or the contents of the Installation.
3. Purposes of Processing
The data is processed for the purpose of enabling the operation of the Licensee’s business, which includes serving Data Subjects, managing their case files, collecting payments, scheduling appointments and communicating with them.
TNS does not use Data Subjects’ data for any purpose of its own: TNS does not analyze it, sell it, disclose or transfer it, or use it to develop, improve or train artificial intelligence or machine learning models. The data passing through the services described in Section 5.2 is handled solely for the purpose of providing those services, namely delivering the message or the email to its recipient, processing the connection permission and correcting Software errors.
4. Artificial Intelligence
The Software includes artificial intelligence (hereinafter, “AI”) features: an assistant in the message inbox, contact record and conversation summaries, drafting assistance, and advertising analysis.
Such features remain disabled until the Licensee connects an AI service provider (hereinafter, the “AI Provider”). The Software does not include any AI Provider, and TNS does not supply any credentials.
4.1 Selection of the AI Provider
The AI Provider is selected by the Licensee, who enters its own API key under Settings → Integrations. Such key may correspond to Gemini (Google), OpenAI, Anthropic, Kimi/Moonshot, DeepSeek or OpenRouter. The key is stored in encrypted form and is never transmitted to the browser.
4.2 Data Accessed by the AI Model
Immigration status is not sent to the AI model under any circumstances. No setting of the Software permits such transmission, and the Software does not read that field when preparing the information to be transmitted.
Internal notes are likewise not sent, unless the Licensee expressly enables that option under Settings → Assistant → Privacy. The option is disabled by default.
The data transmitted to the AI Provider for each feature is as follows:
| Feature | Data Transmitted |
|---|---|
| Contact record summary | Name, phone number, email address, language and country of origin of the contact; up to 10 case files with dates and deadlines (and amounts, if the User executing the feature has permission to view them); 15 records from the communications log (messages sent from the Software and call notes), with their text; 5 appointments created in the Software; and 10 internal notes, only if the Licensee has enabled the aforementioned option. |
| Conversation summary | Up to 60 messages from the thread. Internal notes in the thread are excluded, unless the Licensee enables the same option. Email threads are never summarized. |
| Drafting, rewriting and translation | Only the text the User is drafting. |
| Inbox assistant | The conversation history and, if the assistant looks them up, case file details. The assistant does not act on email threads. |
| Advertising analysis | Spend and results of Meta campaigns. Google Ads campaigns are excluded. |
| Knowledge base | The text the Licensee has uploaded, converted into numerical representations so that it can be searched. |
Summaries are not stored; they are displayed on screen and are not retained.
Data received from Google (hereinafter, “Google User Data”) is not sent to any AI service provider, including the AI Provider, under any circumstances, as provided in Section 5.4.
The Licensee is responsible for obtaining the consent or the legal basis required by the law applicable to it in order to process Data Subjects’ data by means of the AI features, as provided in Section 13.
4.3 Processing of Data by the AI Provider
The processing of data by the AI Provider is governed by the contract entered into between the Licensee and such AI Provider, and not by the Software. The Software does not, and cannot, impose retention terms on an AI Provider selected by the Licensee and with which the Licensee contracts directly.
The Licensee is advised, prior to using the AI features with sensitive case files, to review such terms and to select a plan that does not retain or reuse its data. None of the data described in Section 5.4 forms part of the information received by the AI Provider.
5. Recipients of the Data
5.1 Services Connected by the Licensee (All Optional)
The third-party services the Licensee elects to connect to the Installation are hereinafter referred to as the “Third-Party Services”. If the Licensee does not connect any of the Third-Party Services listed below, the Software does not communicate with any third party, without prejudice to the provisions of Section 5.2.
| Service | Purpose | Data Transmitted |
|---|---|---|
| Meta (WhatsApp, Messenger, Instagram) | Messaging | Messages and contact details |
| Google (Drive, Calendar, Gmail, Google Ads) | Documents, calendar, email and advertising results | Files, appointments and emails, as provided in Section 5.4 |
| Microsoft 365 | The same as for Google | The same as for Google |
| Twilio | SMS and calls | Number and message content |
| Stripe | Payments | Amount, email address and invoice details |
| DocuSign / Documenso | Contract signing | The document and the signer’s details |
| AI Provider | Those described in Section 4 | Those described in Section 4 |
The handling of data by each Third-Party Service is governed by the contract entered into between the Licensee and such third party.
5.2 TNS Services (Operational Without the Licensee Connecting Any Service)
TNS provides the following two services.
Zevli Connect is the TNS intermediary service that enables Meta, Google, Microsoft, Stripe, DocuSign or Twilio to be connected without each Licensee being required to register its own application in the console of each such provider. Connection permissions are processed through Zevli Connect and, where the Meta connection was made through this channel, so are incoming messages from WhatsApp, Messenger and Instagram, which Zevli Connect forwards to the Installation.
In ordinary operation, Zevli Connect does not store the transmission: it signs it and delivers it to the Installation. Where the Installation is not reachable, the transmission is held at Zevli Connect in encrypted form, using the AES-256-GCM algorithm, solely for the purpose of retrying delivery, for a maximum period of seven (7) days in the case of messages and twenty-four (24) hours in the case of connection credentials. Upon expiry of the applicable period, the transmission is deleted. The TNS administration panel does not display the contents of such transmissions under any circumstances, and TNS does not consult such contents.
When the Licensee connects a service through Zevli Connect, the Installation attaches to the request an encrypted reference identifying, within the Installation itself, the company and the User that initiated the connection, so that the credentials obtained are stored in the correct company. That reference is encrypted with a key held solely by the Installation: TNS transports it and returns it with the credentials without being able to read it.
Zevli Connect also generates and sends, through Resend, authentication emails (password recovery, User invitations and email address change confirmations). Consequently, Users’ email addresses are transmitted through TNS and Resend infrastructure.
Sentry is the TNS error-reporting system, hosted by TNS. It receives Software errors for the purpose of correcting them before the Licensee notices them. Prior to transmission, each report passes through a filter that removes passwords, connection strings, email addresses and credentials. No IP addresses or cookies are transmitted. The sending of reports to Sentry may be disabled by removing its configuration from the Installation.
The Installation’s licence may be obtained through Zevli Connect. Solely where the Licensee expressly requests it from the Software’s licence screen, the Installation transmits to TNS the email address and the activation code entered by the Licensee, together with the Installation’s identifier. Using those data, TNS verifies the corresponding purchase and returns the signed licence. No data concerning Clients, concerning Users other than the requester, or concerning the content stored in the Installation is transmitted. If the Licensee does not use that function, the licence is entered manually and no communication with TNS takes place on this account.
The transfer of the licence to another Installation is likewise requested from within the Software, on the destination Installation. The Installation transmits to TNS the same data as for obtaining the licence, together with the language in which the confirmation email is to be written. TNS sends, through Resend, an email containing a single-use confirmation link to the purchase email address and, once the transfer has been confirmed, a second notification email. Consequently, that address is transmitted through TNS and Resend infrastructure, on the same terms as authentication emails.
The retention periods applicable to the services described in this Section are set out in Section 7.2.
5.3 Absence of Advertising and Analytics
The Software does not include advertising or analytics tools. It contains no pixels, no Google Analytics and no tracking tools. Its content security policy does not permit third-party scripts to be loaded. The only connections the browser is permitted to establish are those to the Installation’s own database and, where in-browser calling is used, to Twilio.
Fonts are served from the Licensee’s own domain, and no request is made to external servers.
5.4 Google User Data
When the Licensee connects Google, ZEVLI requests from Google the permissions set out in the following table and uses each of them exclusively for the purpose described in the corresponding row:
| Permission | Purpose of the Permission |
|---|---|
Google Drive (drive.file) | Saves the documents and encrypted backups stored by Users, and reads back only the files created by ZEVLI itself. It cannot access the remainder of the Licensee’s Google Drive. |
Google Calendar (calendar.events) | Writes the appointments created in the Software to the Licensee’s calendar and brings the events of such calendar into the Software’s agenda. |
Gmail, read (gmail.readonly) | Brings incoming emails into the Software’s inbox, together with the remainder of each Data Subject’s conversation. |
Gmail, send (gmail.send) | Sends the replies Users draft in the Software, from the Licensee’s own email address. |
Google Ads (adwords) | Reads the spend and results of the Licensee’s campaigns in order to display them in the advertising dashboard. |
| Sign in with Google | Name, email address and photograph of the User signing in. |
Google User Data is stored in the Installation’s own database, on the Licensee’s Equipment. Zevli Connect manages the permission; the content of emails, files and calendar is transmitted directly between Google and the Installation. TNS does not receive Google User Data and cannot read it.
Only Users have access to Google User Data, in accordance with the role assigned to each of them.
Google User Data is subject to the following restrictions:
- Under no circumstances is it sent to any AI service provider, including the AI Provider, or used to develop, improve or train artificial intelligence or machine learning models.
- Under no circumstances is it used for advertising purposes or sold. Nor is it, under any circumstances, transferred to advertising platforms, data brokers or information resellers, or used to determine creditworthiness or for lending purposes.
- It is not transferred to any other third party, except to the extent necessary to provide the features described in the preceding table, for security purposes or to comply with the law.
- No person at TNS reads Google User Data.
ZEVLI’s access to the Google account may be revoked by disconnecting Google from the Software or by removing ZEVLI from the permissions page of the Google account. Either action immediately terminates all further access. Google User Data already brought in remains in the Installation until the Licensee deletes it, as provided in Section 7.
ZEVLI’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Google Workspace APIs are not used to develop, improve, or train generalized AI and/or ML models.
The two preceding statements reproduce verbatim the text required by Google.
6. Cookies
The Software uses five cookies, all of which are necessary for its operation:
| Cookie | Purpose |
|---|---|
| Session | Keeping the session signed in. |
| Access verifier | Ensuring that the recovery link only works in the browser from which it was requested. |
| Language | Remembering whether Spanish or English is used. |
| Connection nonce | Preventing a third party from completing a connection on behalf of the User. |
| Portal session | Keeping the Data Subject’s session open after entry of their PIN. |
None of them serves an advertising or tracking purpose, which is why no cookie consent notice is displayed.
7. Retention Periods
7.1 Data Retained in the Installation
Data remains in the Installation for as long as the Licensee decides to retain it. TNS does not set retention periods for such data, since TNS has no access to it.
7.2 Retention Periods in the TNS Services
| Data or service | What is retained | Retention period |
|---|---|---|
| Installation | All data described in Section 2 | As decided by the Licensee, in accordance with Section 7.1. |
| Zevli Connect, ordinary operation | None of the contents of transmissions. The transmission is signed and delivered to the Installation without being stored. | Not retained. |
| Zevli Connect, licence record | The licence record data described in Section 2.4. | For as long as the License is in force and, thereafter, for as long as is necessary to evidence it and to comply with the legal, accounting and tax obligations of TNS. |
| Zevli Connect, licence transfer requests | The request data described in Section 2.4. The confirmation link expires after thirty (30) minutes. | The record of the request is retained together with the licence record, since it limits the frequency of transfers (one transfer every ninety (90) days). |
| Zevli Connect, messages pending delivery | The encrypted transmission containing the message, solely for the purpose of retrying delivery to the Installation. | A maximum of seven (7) days, upon the expiry of which it is deleted. |
| Zevli Connect, connection credentials pending delivery | The encrypted transmission containing the credential, solely for the purpose of retrying delivery to the Installation. | A maximum of twenty-four (24) hours, upon the expiry of which it is deleted. |
| Sentry (error reports) | The error report, once the filter described in Section 5.2 has been applied. No IP addresses or cookies are retained. | Ninety (90) days, upon the expiry of which they are deleted. The sending of reports may be disabled as provided in Section 5.2. |
| Resend (authentication and licence transfer emails) | The recipient’s email address and the record of the transmission. | Thirty (30) days, in accordance with the retention period that such provider applies to email data. |
| Commercial relationship with the Licensee | The Licensee’s identification and contact details and the documentation relating to the License. | For as long as is necessary to evidence the License and to comply with the legal, accounting and tax obligations of TNS. |
The contents of transmissions held by Zevli Connect are not displayed in the TNS administration panel, as stated in Section 5.2.
7.3 Audit Log and Deletion Requests
The audit log records who performed each operation in the Installation and when. Each change to the main tables generates a copy of the affected record, so that the operation can subsequently be verified, and the audit log is designed so that it cannot be deleted from within the Software, not even by the administrator. This feature is what ensures that no person can conceal the operations they have performed. Consequently, when a contact is deleted, their information may remain in such log.
There is therefore a tension, which is expressly stated here, between the function of the audit log and Data Subjects’ deletion requests. The resolution of such tension rests with the Licensee, within its own Installation: it is the Licensee that decides on the retention of the audit log and that handles deletion requests, assessing what the law applicable to it requires and what it permits. TNS cannot take part in that decision, since it has no access to the Installation.
The Software offers the Licensee two operations for giving effect to that decision: the deletion of a person’s data and the deletion of a company. In both cases, the Software deletes the corresponding operational data and replaces, in the audit log, the personal data contained in the copies of the affected records, retaining only structural information (which operation was performed, on which record, when and by whom). Backups made beforehand retain such data until the Licensee deletes them, and files stored in the cloud storage service connected by the Licensee are not deleted, as provided in Section 7.4.
7.4 Documents
Documents are not deleted automatically. When a case file is deleted, the associated files may remain in the Installation’s storage and in the cloud storage service the Licensee has connected. Their deletion rests with the Licensee.
8. Data Subjects’ Rights
The party answerable for Data Subjects’ data is the Licensee that uses the Software, and not TNS. Data Subjects shall contact the Licensee to request access to, rectification of or deletion of their data, on the terms provided in Section 13.
The Software includes a contact export feature that makes it possible to deliver a person’s data in a file. As of the date of this version, such export does not include conversations or appointments.
A Licensee that requires technical assistance in handling a request may contact TNS in writing.
9. Security
The Software applies the following measures:
- Isolation between Companies: where a single Licensee manages several Companies on the same Equipment, the database prevents, by design, one Company from accessing another Company’s data. This isolation is verified by automated tests on every change to the code.
- Role-based access: a User with the assistant role cannot view amounts or the communications history.
- A record of the operations performed by each User, which cannot be deleted from within the Software, as provided in Section 7.3.
- Encrypted backups, stored in the Licensee’s own Google Drive or OneDrive, with a key held solely by the Licensee (hereinafter, the “Encryption Key”). Neither TNS nor any third party can read such backups.
- Public registration closed: no person can sign up on their own; User accounts are created by the administrator.
The following measures depend on the Licensee:
- Encrypting the disk of the Equipment on which the Installation runs.
- Safeguarding the Encryption Key. If the Encryption Key is lost, the backups will be unrecoverable, including for TNS and for any third party.
- Reviewing Users’ permissions.
The Software does not perform antivirus scanning of uploaded files.
10. Minors
The Software is a work tool and is not directed at minors. The Installation may contain minors’ data where the Licensee handles such data (for example, in family case files); in such case, the Licensee is responsible for handling it correctly.
11. Amendments to the Policy
TNS shall announce any amendment to this Policy in the Software itself and in this document, indicating the date of the corresponding version. Amendments affecting data already collected shall be communicated in advance.
12. Contact
The contact details of TNS are as follows:
- Name: Tele Network Solutions, LLC
- Email: info@telenetworksolutions.com
- Address: 2731 Sheffield Cir, Kissimmee, FL 34746, United States
Data Subjects shall first contact the relevant Licensee, in its capacity as custodian of their data.
13. Privacy Obligations of the Licensee
The Licensee undertakes to:
- Comply with the privacy and data protection laws applicable to it, including the privacy laws of the States of the United States of America that apply to its business.
- Obtain and retain the consent or legal basis required by applicable law for sending communications by WhatsApp, Messenger, Instagram, Telegram, SMS and email through the Software, as well as for processing Data Subjects’ data by means of the AI features described in Section 4.
- Inform Data Subjects of the processing of their data and handle the requests for access, rectification, deletion, portability and objection that they submit to the Licensee, on the terms and within the periods established by applicable law.
- Keep its own privacy policy up to date.
TNS cannot discharge such obligations on the Licensee’s behalf, since TNS has no access to Data Subjects’ data or to the Installation, and maintains no relationship with the Data Subjects.
14. Notification of Security Incidents
In the event of a security breach affecting the TNS services described in Section 5.2, TNS shall notify the Licensee without undue delay, with the information available to it at that time and with such updates as result from the subsequent investigation.
Notification of the breach to Data Subjects and to the competent authorities rests with the Licensee, as the party that maintains the relationship with the Data Subjects and that knows the jurisdiction to which they and its own business are subject. TNS cannot give such notification on the Licensee’s behalf.
Security breaches affecting the Equipment or the Installation, rather than the services described in Section 5.2, rest with the Licensee, since TNS has neither access to nor control over the Equipment or the Installation. TNS shall cooperate, so far as it reasonably can, in the technical clarification of the incident.
15. Health Information
The Installation may contain information relating to the health of Data Subjects, such as medical examination reports, where the Licensee enters such information into case files. Such processing takes place exclusively in the Installation, to which TNS has no access.
The processing of protected health information through the TNS services described in Section 5.2, namely Zevli Connect and Sentry, is prohibited unless the Licensee and TNS have first entered into a Business Associate Agreement (“BAA”). In the absence of such an agreement, the Licensee undertakes not to route protected health information through either of those services.
Notice is expressly given that third-party messaging services, and in particular WhatsApp and the other Meta platforms, are not a suitable means of communicating protected health information, since their operators do not enter into agreements of that nature. Compliance with the health care laws applicable to the Licensee rests exclusively with the Licensee.
16. Requests from Authorities and Legal Process
TNS can produce only the information available to it, which is limited to the data of its own commercial relationship with the Licensee and the data held in the services described in Section 5.2, within the periods set out in Section 7.2. TNS cannot produce the contents of an Installation, or the Data Subjects’ data retained therein, since it has no access to such Installation. Any request seeking such contents must be directed to the Licensee.
Where applicable law permits, TNS shall notify the Licensee of the existence of legal process affecting its data.
17. Export Controls and Sanctions
The Licensee represents that it is not subject to economic or trade sanctions imposed by the United States of America, that it neither resides nor is established in a territory subject to a comprehensive embargo of that country, and that it does not appear on the restricted party lists maintained by its authorities. The Licensee undertakes not to use, export, re-export or make the Software available to third parties in contravention of the export control and sanctions laws of the United States of America.
The Software is intended for use in the United States of America. The acquisition or use of the Software outside that territory may be subject to additional privacy, data processing or export control requirements, compliance with which rests with the Licensee and may require specific prior review.
18. Governing Law and Dispute Resolution
This Policy is governed by the laws of the State of Florida, United States of America, excluding its conflict-of-laws rules.
Disputes arising in connection with this Policy are subject to the dispute resolution regime set out in the terms and conditions of use of the Software, which comprises, among other provisions, mandatory pre-suit negotiation for a period of thirty (30) calendar days, the exclusive forum of the state and federal courts located in Osceola County, Florida, the mutual waiver of trial by jury and of class and representative actions, and the following exceptions, which are available to both Parties alike: the right to bring in small claims court those claims that fall within the jurisdiction of such court, which shall be brought in the county of the Licensee’s domicile, and the right to seek urgent injunctive relief before any court of competent jurisdiction. The statutes of limitation established by applicable law govern; this Policy does not shorten any limitations period and does not establish any contractual period of repose.
18.1. WAIVER OF JURY TRIAL
EACH PARTY KNOWINGLY, VOLUNTARILY AND INTENTIONALLY WAIVES, ON A MUTUAL BASIS, ANY RIGHT TO A TRIAL BY JURY IN ANY PROCEEDING, ACTION, CLAIM OR COUNTERCLAIM, WHETHER IN CONTRACT OR IN TORT, ARISING OUT OF OR RELATING TO THIS POLICY, THE LICENSE OR THE SOFTWARE. EACH PARTY REPRESENTS THAT IT HAS READ AND UNDERSTOOD THIS WAIVER, THAT IT HAS HAD THE OPPORTUNITY TO CONSULT COUNSEL OF ITS CHOICE, AND THAT THIS WAIVER IS A MATERIAL INDUCEMENT TO THE CONTRACT BETWEEN THE PARTIES.
18.2. Class and Representative Action Waiver
Disputes arising in connection with this Policy shall be resolved solely on an individual basis. Neither the Licensee nor TNS shall bring or participate, against the other Party, in any class, consolidated, representative or private attorney general action, or act as a class representative or class member. Neither Party may consolidate the claims of more than one person in a single proceeding. If this waiver is held unenforceable as to a particular claim, that claim shall be litigated in the courts identified in this Section 18, and the remainder of this Section shall remain in full force and effect.
19. Language
This Policy is published in Spanish and in English. The English-language version is the version that prevails in the event of any discrepancy between them; the Spanish-language version is a courtesy translation and has no prevailing interpretive value.
This Policy corresponds to version 1.3 of this document.