Privacy Policy

1. Scope of this preliminary version

This page describes technical behaviour identified in the Nexiis Tools repository. It will be updated once vendors, purposes, retention periods and applicable requirements are confirmed.

2. Responsible company and contact

As confirmed by the project owner, the company responsible for the Nexiis Tools platform is FRENA SOLUCOES EM TECNOLOGIA DA INFORMACAO LTDA., Brazilian company registration number 51.080.069/0001-03, in Brazil.

Its physical address, the data-protection officer name, the legal controller qualification for each activity and other institutional information still require validation before final publication.

3. Images processed by the tools

Image tools select files on the user device and process them in the browser through APIs such as Image, Canvas, Blob and temporary object URLs. The image-tool pipeline does not upload image files to a Nexiis Tools server route.

Previews and results may use temporary Blob URLs, which are revoked when no longer needed. This does not remove technical requests required to load the site and cannot guarantee the behaviour of extensions, browsers, networks or third-party services.

4. Contact and technical data

The contact form submits name, email and message to the site contact route. That route also reads the IP address forwarded with the request, when available, solely to apply an in-memory technical request limit.

If Mailgun environment variables are configured, the route may forward form content to Mailgun for email delivery. Its effective use in each environment must be confirmed before final publication.

Hosting, proxy, CDN and external-provider logs cannot be determined from this repository alone and may handle technical data under their own settings and agreements.

5. Preferences, analytics and advertising

The consent choice is stored locally as `nexiis-consent-v1`. Essential categories remain active; analytics and advertising are optional and remain blocked until a valid decision exists.

The current code does not configure GA4, Google Tag Manager, Google AdSense or another provider. Permission in the banner does not activate an absent provider or queue earlier events.

6. Purposes and legal bases

Purposes and legal bases for personal-data processing require institutional and legal validation. This version does not presume a legal basis, does not claim legitimate interests and does not replace an assessment of each processing activity.

7. Sharing and international transfers

The repository confirms possible Mailgun use only when configured and plans future, currently inactive analytics and advertising services. Other sharing, subprocessors, data locations and international transfers depend on external configuration and contract review.

8. Security and retention

The project uses measures such as input validation, contact-form request limiting and security headers. There is not enough evidence to claim certifications, specific retention, immediate deletion or operational controls in every environment.

Retention periods for messages, logs and provider data must be defined and published after validation.

9. Rights and requests

Brazilian data-protection law provides rights relating to personal-data processing, including information, confirmation, access, correction, deletion where applicable, portability, objection and consent withdrawal. The application already lets visitors revoke optional categories through Privacy settings.

Privacy requests may be sent to the channel displayed on this page. The practical application of rights, requester identification and deadlines depends on legal review and actual processing.

• You can change optional preferences at any time through Privacy settings.
• The official ANPD reference below explains data-subject rights and their legal limits.

10. Children and teenagers

The repository does not define an audience, age verification or a specific workflow for children’s and teenagers’ data. This requires product decisions and legal review before final publication.

11. Changes to this policy

The final version must identify the responsible party, contact channel, effective date, versions and update procedure. Reading or changing this page must not be interpreted as consent to optional categories.