Skip to content
rogpe.tech
SolutionsHow we workCompanyProjects Discuss a challenge
PTENES

Privacy

We process only the data needed to respond and operate the relationship.

Form data is used for contact, triage, and service continuity. Umami records visits and navigation without receiving form fields. First-party events do not include free text, name, email, or company.

Updated September 13, 2026

Transparency is part of control. This policy explains what data rogpe.tech receives, why it uses it, and how to contact us about it.

1. Who is responsible

For data processed on this website, the rogpe.tech operation acts as controller: it determines the purpose of the contact form, support, and first-party metrics. For privacy questions or requests, write to rodolfo@rogpe.tech.

2. Data we receive

Contact and support forms receive your name, email, optional company, area of interest, and the context you choose to send. We also record the request date, reference, privacy confirmation, source, and language so we can respond and follow up.

For navigation measurement, the site uses Umami at analytics.rogpe.tech and first-party events. Those events cover only allow-listed actions, paths, locale, and a technical session identifier. Form text, name, email, and company are not sent to those metrics.

3. Why we use it

We use submitted data to respond, triage the request, prepare the next conversation, follow support, and preserve service continuity. The checkbox records consent to receive a response. If the conversation becomes a proposal or contract, processing follows that business relationship and its specific documents.

4. Storage and sharing

The site stores a request before attempting delivery to the operational CRM. When the CRM is configured, it receives the contact and request fields; if it is unavailable, a contingency copy stays queued until delivery can resume. Links to WhatsApp, email, or outside services take you to platforms with their own policies.

Navigation metrics are separate from contact records. We do not use form content to feed Umami or product events.

5. Retention and security

A delivered request's local contingency copy is removed under the operating retention setting — currently 365 days by default and never below 30 days. Pending requests can remain until delivered or handled. Retention in the CRM follows its configuration and the needs of the service.

The service applies request limits, restricted local file access, and security headers. No measure removes every risk; contact us if an incident involving your data needs to be checked.

6. Your choices and contact

To request access, correction, deletion where applicable, portability, information about sharing, objection, or withdrawal of consent, write to rodolfo@rogpe.tech with enough information to locate the contact. We may ask for identity confirmation to protect your data. Requests are handled under the applicable rules.

7. Changes

If the operation, data categories, or providers change materially, we will update this page and its date. This policy applies to rogpe.tech; products with their own operation may have specific notices.

rogpe.tech

Software and AI consulting and engineering for operations that need to evolve with control.

PrivacyTerms

© 2026 rogpe.tech