privacidade e seguranca

Terms of Use

HashData Platform Terms of Use

Translation note: this document is a translation of the original Portuguese version (“Termos de Uso da Plataforma HashData – v2.0”), provided for convenience. In case of any discrepancy or doubt of interpretation, the Portuguese version prevails.

Version: 2.0 · Effective date: from the date of publication on the Platform, as recorded in the version history · Previous version: fully superseded

Platform Owner: HASH PROJECTS INFORMÁTICA LTDA. (“HashData”), Brazilian Corporate Taxpayer ID (CNPJ) No. 29.580.686/0001-19, headquartered at Av. Deputado Jamel Cecílio, nº 3.455, Quadra C-09, Lotes 02/05-15, Edifício Flamboyant Parque Business, Sala 207, Jardim Goiás, Goiânia/GO, Brazil, ZIP Code 74.810-100.

1. Acceptance, applicability and hierarchy

1.1. These Terms of Use (“Terms”) govern access to and use of the HashData Platform by all Users, in any environment (production, staging, testing or demonstration) and through any means (web, mobile applications, desktop applications or API).

1.2. Acceptance of these Terms is express and individual. It takes place upon the Customer’s registration on the Platform, upon each User’s first access, and upon each new version, through an affirmative action on the acceptance screen (ticking a box and confirming). Access to the Platform remains blocked until acceptance.

1.3. HashData records each acceptance with the User’s identification, the linked Customer, date, time, IP address and the version accepted. The record is kept for as long as the contractual relationship lasts and for the applicable statute of limitations period, for evidentiary purposes.

1.4. Whoever accepts these Terms on behalf of the Customer represents that they have the authority to bind the Customer and that the registration data provided, including the CNPJ, are true. A User who does not agree with these Terms must not use the Platform and must inform the Customer’s administrator.

1.5. These Terms form part of the contractual framework consisting of: (i) the main agreement entered into between HashData and the Customer or, in its absence, the plan subscribed to on the Platform; (ii) the Data Processing Agreement (“DPA”), when executed; (iii) any Module Addenda; and (iv) the Privacy Policy, published at hashdata.app.

1.6. In case of conflict, the following prevail: the DPA and the Module Addenda, on matters of personal data protection; the main agreement, on commercial matters, pricing, terms and service levels; and these Terms, in all other cases. Commitments in these Terms that are more specific or more protective of the Customer or of data subjects, such as the incident notification deadline in Clause 9.3, prevail over generic or open-ended provisions of other instruments.

1.7. Where no DPA has been executed separately, Clauses 4 to 13 of these Terms constitute the Customer’s documented instructions to HashData and the data processing agreement between the parties, for the purposes of Article 39 of the LGPD.

2. Definitions

2.1. For the purposes of these Terms, the definitions below apply, without prejudice to those contained in Brazilian Law No. 13,709/2018 – General Data Protection Law (“LGPD”), the main agreement and the DPA.

  • Customer: a legal entity, identified by its CNPJ, that contracts the Platform, including through direct registration, and acts as Controller of the Customer Data.
  • User: a natural person aged 18 or over, authorized by the Customer with individual credentials. Includes administrators, managers, field data collectors and authenticated integrations.
  • Platform: the HashData solution offered as Software as a Service (SaaS), including forms, online and offline data collection, applications, dashboards, Advanced Analytics, Action Plans, Workflows, integrations, APIs and Artificial Intelligence modules.
  • Customer Data: data, files, images, audio recordings, signatures, coordinates and other content entered, collected, integrated or generated on the Platform by the Customer, its Users or its integrations.
  • Account and Usage Data: registration, authentication and access log data of Users, as well as technical data on the operation of the Platform, processed by HashData under Clause 5.
  • High-Risk Module: a feature whose use, by its nature, involves sensitive personal data or high risk to data subjects, such as facial recognition, audio recording and transcription, continuous geolocation and automated decisions.
  • Module Addendum: a specific instrument, executed between HashData and the Customer, that enables a High-Risk Module and sets out its purpose, legal basis, safeguards and retention periods.
  • Sub-processor: a third party engaged by HashData that processes Customer Data to enable the service.
  • Security Incident: a confirmed adverse event that compromises the confidentiality, integrity or availability of personal data.
  • Controller, Processor, Data Subject, Data Protection Officer (“Encarregado”) and Sensitive Personal Data: as defined in Article 5 of the LGPD.

3. Service, eligibility and credentials

3.1. The Platform is a technology tool for corporate use (B2B). It allows data to be collected, organized, processed, visualized and automated according to the settings defined by the Customer.

3.2. HashData does not provide legal, accounting, labor, sanitary, auditing or compliance advice. Reports, indicators and automation results reflect the Customer’s data and parameters and do not constitute an opinion, certification or guarantee of results.

3.3. The Platform is not intended for natural persons acting as consumers, nor for minors under 18 as Users. The Customer must not authorize any underage User.

3.4. Each User receives personal, non-transferable credentials. The Customer is responsible for:

  1. creating, reviewing and revoking access, observing the principle of least privilege;
  2. immediately revoking the access of Users who have left or have no operational need;
  3. requiring its Users to use strong passwords and to log out at the end of use, in addition to the lockout after failed attempts and the session expiration for inactivity maintained by the Platform;
  4. instructing its Users on the proper use of the Platform and on these Terms.

3.5. Each User undertakes to keep their credentials confidential, not to share them, and to immediately notify the Customer’s administrator and HashData of any suspected misuse.

3.6. Acts performed with a User’s credentials are attributed to the Customer, unless a security failure under HashData’s control is proven.

4. Roles in the processing of Customer Data

4.1. With respect to Customer Data, the Customer is the Controller and HashData is the Processor (Article 5, VI and VII, of the LGPD). HashData processes such data only in accordance with the Customer’s documented instructions, the main agreement and the DPA (Article 39 of the LGPD).

4.2. As Controller, the Customer is responsible for:

  1. defining the purposes and legal basis of each form, collection and automation;
  2. informing data subjects about the processing, including audio recording, image capture and geolocation, where applicable;
  3. responding to data subject requests;
  4. notifying incidents to the Brazilian National Data Protection Authority (“ANPD”) and to data subjects, where required.

4.3. HashData does not use Customer Data for its own purposes. This includes advertising, sale, database enrichment, identified comparison between customers, and training of general-purpose Artificial Intelligence models or models of other customers. The only exception is that provided for in Clause 4.5.

4.4. If HashData identifies an instruction it considers contrary to the LGPD, it will inform the Customer and may suspend the corresponding processing until clarification.

4.5. Anonymized data. The Customer authorizes HashData to anonymize Customer Data and to use it, in aggregate form, for statistics on the use and performance of the Platform and for service improvement, under the following conditions:

  1. anonymization by reasonable and available technical means, without possibility of reversal (Article 12 of the LGPD);
  2. prohibition of any attempt at re-identification;
  3. results that do not identify data subjects, the Customer or its establishments;
  4. prohibition of the sale or transfer of anonymized data to third parties;
  5. exclusion of audio recordings, facial images and other data from High-Risk Modules;
  6. prohibition of use for training Artificial Intelligence models.

5. Account and Usage Data: HashData as Controller

5.1. HashData is the Controller of Users’ Account and Usage Data, which comprises:

  • name, e-mail, telephone, job title and linked company;
  • credentials, authentication records and records of acceptance of these Terms;
  • application access logs (IP address, date and time);
  • technical data on device, application version and performance.

5.2. Such data is processed to: (i) perform the contract and provide support (Article 7, V, of the LGPD); (ii) comply with legal obligations, including retaining application access logs for 6 (six) months (Article 15 of Brazilian Law No. 12,965/2014 – Brazilian Internet Civil Framework, and Article 7, II, of the LGPD); and (iii) ensure security, prevent fraud and maintain the operation of the Platform (Article 7, IX, of the LGPD).

5.3. HashData may generate aggregated technical metrics on the operation of the Platform, such as access volume, performance and errors. Such metrics do not include the content of Customer Data and do not identify data subjects.

5.4. The processing of Account and Usage Data is detailed in the Privacy Policy, which sets out retention periods, data sharing and data subject rights.

6. Sensitive data, data of minors and High-Risk Modules

6.1. The processing of sensitive personal data requires a specific legal basis under Article 11 of the LGPD. Defining that basis is the Customer’s responsibility. The processing of data of children and adolescents must comply with Article 14 of the LGPD, including the best interests of the data subject.

6.2. High-Risk Modules are only enabled after a Module Addendum is executed. That instrument shall contain, at a minimum:

  1. the specific purpose and the legal basis indicated by the Customer;
  2. confirmation that the Customer has prepared or updated its Data Protection Impact Assessment (Article 38 of the LGPD);
  3. the applicable additional technical safeguards;
  4. the retention period and the method of data deletion.

6.3. Facial recognition. Biometric data is sensitive personal data (Article 5, II, of the LGPD). The Customer must ensure a valid legal basis, as a rule the specific and highlighted consent of the data subject (Article 11, I), and offer an alternative means of identification to those who do not consent, where the legal basis so requires.

6.4. Audio recording and transcription. The Customer must inform the data subject in advance that recording will take place. Audio recordings are retained for 90 (ninety) days and permanently deleted thereafter, unless otherwise instructed in the Module Addendum. The Customer may download a copy of the audio recordings before deletion.

6.5. Geolocation. The Platform records the device’s location at the time of each data collection and, when so configured, throughout the working day. The Customer must inform collecting Users of this recording and limit it to the defined operational purpose.

6.6. In free-text fields, the Customer must instruct its Users not to enter sensitive data or data of minors without necessity.

7. Artificial Intelligence and automated decisions

7.1. The AI features (image and text classification, anomaly detection, OCR, transcription, semantic search, text generation and summarization) produce probabilistic results and may contain errors. The Customer must validate the results before using them in relevant decisions.

7.2. If the Customer configures the Platform to make decisions based solely on automated processing that affect the interests of data subjects, it must guarantee the right to review and the provision of information on the criteria used (Article 20 of the LGPD). HashData will provide the Customer with the necessary technical information, subject to commercial and industrial secrecy.

7.3. Model fine-tuning with Customer Data occurs only upon the Customer’s express instruction. The resulting model is for the exclusive use of that Customer.

7.4. Where an AI feature uses an external provider, that provider will be included in the list of Sub-processors (Clause 10).

8. Permitted use and prohibited conduct

8.1. The Platform must be used only for lawful purposes compatible with the contract. The Customer and Users are prohibited from:

  1. entering data obtained unlawfully or without a legal basis;
  2. using the Platform for surveillance, discrimination or any abusive purpose in relation to data subjects;
  3. sharing credentials or allowing access by unauthorized third parties;
  4. attempting to access data, environments or accounts of other customers;
  5. performing intrusion tests, scans or exploitation of vulnerabilities without HashData’s prior written authorization;
  6. reverse engineering, decompiling or extracting source code;
  7. introducing malicious code or deliberately overloading the Platform;
  8. circumventing technical limits, security mechanisms or license restrictions.

8.2. Vulnerabilities identified in good faith must be reported to HashData through the channel lgpd@hashdata.app, without exploitation or public disclosure before they are fixed.

9. Information security and incidents

9.1. HashData maintains technical and administrative measures capable of protecting personal data, proportionate to the risk (Article 46 of the LGPD), described in its Information Security Policy. These include: encryption in transit and at rest, role-based access control, audit logs, backups, logical isolation between customers and vulnerability management.

9.2. The Customer maintains compatible controls in its own environment: protection of collection devices, access management and guidance to Users.

9.3. Upon becoming aware of a Security Incident affecting Customer Data, regardless of the severity assessment, HashData will notify the Customer within 48 (forty-eight) hours, through the registered security contact. The notification will include, to the extent already known:

  • the nature of the incident and the categories of data affected;
  • the estimated number of data subjects involved;
  • the containment and mitigation measures adopted;
  • the risks identified and the next steps.

9.4. HashData will supplement the information as the investigation progresses and will cooperate with the Customer so that the Customer meets the deadline for notification to the ANPD and to data subjects set out in the Security Incident Notification Regulation (ANPD Board Resolution CD/ANPD No. 15/2024).

9.5. In incidents affecting Account and Usage Data, HashData, as Controller, will directly make the notifications required by Article 48 of the LGPD.

9.6. Users must immediately notify HashData of any suspected incident, loss of a collection device or compromise of credentials.

10. Sub-processors

10.1. HashData uses Sub-processors for the infrastructure and features of the Platform. The current list, with the activity and country of processing of each, is set out in the table below and will be updated in these Terms upon each addition or replacement.

Sub-processorActivityCountry of processing
ContaboApplication servers, main databases and Advanced Analytics moduleUnited States (US East)
Amazon Web Services (AWS)Storage of photos, files and audio recordings (S3) and backup copiesUnited States

10.2. HashData requires each Sub-processor to comply with data protection obligations equivalent to those assumed towards the Customer and remains liable to the Customer for the acts of Sub-processors within the contracted scope.

10.3. The addition or replacement of a Sub-processor will be communicated to the Customer at least 30 (thirty) days in advance. The Customer may object on reasonable grounds within that period.

10.4. Integrations activated by the Customer itself (for example, Google, Microsoft, Slack or webhooks to the Customer’s systems) are destinations chosen by the Customer and do not constitute HashData Sub-processors.

11. International data transfer

11.1. Personal data may be stored or processed outside Brazil, in the countries indicated in the list of Sub-processors.

11.2. International transfers comply with Articles 33 to 36 of the LGPD and the International Data Transfer Regulation (ANPD Board Resolution CD/ANPD No. 19/2024). Where based on contractual clauses, they adopt the standard contractual clauses approved by the ANPD.

12. Data subject rights and Data Protection Officer

12.1. Data subjects may exercise the rights under Article 18 of the LGPD: confirmation and access, correction, anonymization, blocking or deletion, portability, information on sharing, withdrawal of consent and objection.

12.2. Requests concerning Customer Data must be addressed to the Customer, as the Controller. If HashData receives such a request, it will forward it to the Customer within 2 (two) business days and instruct the data subject to address the request to the Customer, without confirming the existence of processing or providing any data.

12.3. HashData will provide the Customer with the technical means to respond to data subjects, including locating, exporting, correcting and deleting records.

12.4. Requests concerning Account and Usage Data are handled directly by HashData within 15 (fifteen) days.

12.5. HashData’s Data Protection Officer (Encarregado): Hiury Duarte Correia · E-mail: lgpd@hashdata.app · Phone/WhatsApp: +1 970 581 9678.

13. Retention, return and deletion

13.1. Customer Data is kept for the term of the contract, for the periods defined by the Customer. Minimum periods required by regulations applicable to the Customer may be formalized in an Addendum.

13.2. Deletion of records on the Platform. A record deleted by a User is moved to the Customer’s trash and may be restored by the administrator for 30 (thirty) days. At the end of that period, it is permanently deleted from active environments. The audit log retains only the record of the event (user, date, time and record identifier), without the deleted content.

13.3. Deletion at a data subject’s request. When the Customer instructs the deletion of data to respond to a data subject (Article 18, VI, of the LGPD), HashData will permanently delete the indicated data, without passing through the trash, within 15 (fifteen) days, and will provide the Customer with evidence of the deletion.

13.4. Upon termination of the contract, the Customer will have 30 (thirty) calendar days to export its data in a structured, commonly used format (for example, XLS, CSV, PDF or via API). After that period, HashData will permanently delete the Customer Data from active environments, including data in the trash.

13.5. Backup copies are encrypted and protected against alteration (write-once). They are automatically deleted at the end of the technical retention cycle, the duration of which is provided to the Customer upon request. Until then, they remain inaccessible for operational use. If a restoration is required for disaster recovery, deletions carried out after the date of the copy will be reapplied before the environment is released.

13.6. HashData may retain data only in the cases set out in Article 16 of the LGPD, such as compliance with a legal obligation or the regular exercise of rights. Upon request, it will provide the Customer with a statement of the deletion carried out.

14. Intellectual property and license

14.1. The Platform, its code, architecture, algorithms, trademarks and documentation belong to HashData or its licensors.

14.2. During the contractual term, the Customer receives a limited, non-exclusive, non-transferable and revocable license of use, for internal purposes and within the contracted limits.

14.3. The Customer remains the owner of the Customer Data and of the results generated from it. HashData receives only the technical permissions necessary to provide the service.

14.4. Improvement suggestions submitted by the Customer may be incorporated into the Platform without any obligation of remuneration, provided they do not contain Customer Data or confidential information.

15. Confidentiality

15.1. The parties shall keep confidential any non-public information to which they have access as a result of the use of the Platform, including Customer Data, technical documentation, security architecture and commercial terms.

15.2. The duty of confidentiality binds the parties’ employees and service providers and remains in force for 5 (five) years after the termination of the contract, with no time limit for Customer Data and trade secrets.

16. Availability, maintenance and support

16.1. Availability levels, support hours and channels and response times are those defined in the main agreement or, in its absence, in the subscribed plan. Support is provided Monday to Friday, from 9 a.m. to 6 p.m. (Brasília time), via the e-mail suporte@hashdata.com.br.

16.2. Scheduled maintenance will be communicated with reasonable advance notice, preferably outside business hours. The infrastructure is designed for updates without interruption whenever technically possible.

16.3. HashData is not liable for unavailability caused by the Customer’s connection, network or devices, nor for failures of third-party services integrated at the Customer’s choice.

16.4. Offline data collection keeps the data on the device until synchronization. The Customer must instruct its Users to synchronize regularly and to protect their devices.

17. Liability

17.1. Each party is liable for the obligations incumbent upon it as Controller or Processor, under Articles 42 to 45 of the LGPD.

17.2. HashData is not liable for damages arising from: (i) the content, origin or legal basis of the Customer Data; (ii) settings, permissions and integrations defined by the Customer; (iii) misuse of credentials by Users; (iv) decisions made by the Customer based on reports or AI results that have not been validated.

17.3. The monetary limits of liability are those set out in the main agreement or, in its absence, the amount paid by the Customer in the 12 (twelve) months preceding the event giving rise to the claim. Indirect damages and loss of profits are excluded, except in cases of willful misconduct or gross negligence.

17.4. Nothing in these Terms limits liabilities that the law does not allow to be excluded, nor the rights of data subjects before the Controller and the Processor.

18. Suspension and termination

18.1. HashData may suspend, proportionately and preferably restricted to the User or feature involved, any access that poses a security risk, violates these Terms or is subject to a legal order. Whenever possible, the Customer will be notified in advance; in urgent cases, immediately after the suspension, with an indication of the reason.

18.2. Termination of the contract, including by cancellation of the plan on the Platform, ends access for all Users, subject to Clause 13 regarding data export and deletion.

18.3. The clauses on confidentiality, intellectual property, liability and data deletion survive termination.

19. Amendments to these Terms

19.1. HashData may update these Terms for legal, regulatory, technical or security reasons. Each version will have a number and an effective date and will be available at hashdata.app, together with the history of previous versions.

19.2. Material changes will be communicated to the Customer’s administrators at least 30 (thirty) days in advance and will require new acceptance by Users, in accordance with Clause 1.2. Changes required by law or for security reasons may take effect immediately.

19.3. Amendments to these Terms do not reduce the guarantees provided in the DPA and in the main agreement without the Customer’s consent.

20. General provisions, governing law and jurisdiction

20.1. The invalidity of any clause does not affect the others. Tolerance of any breach does not imply waiver or novation.

20.2. Communications relating to these Terms will be made through the contacts registered on the Platform or in the main agreement.

20.3. These Terms are governed by the laws of the Federative Republic of Brazil, in particular the LGPD and the Brazilian Internet Civil Framework.

20.4. The courts of the Judicial District of Goiânia, State of Goiás, Brazil, are elected to settle any disputes arising from these Terms, unless otherwise provided in the main agreement.

Contact: HASH PROJECTS INFORMÁTICA LTDA. · lgpd@hashdata.app · hashdata.app

Scroll to Top