Skip to content
Security Center

Security Center

Updated: March 2026

1. MINIMUM-TRUST ARCHITECTURE

RET Tecnologia treats external input as untrusted by default and applies controls proportional to the risk of the public portal.

  • Principle of Least Privilege: Sensitive variables do not use public prefixes, webhooks require secrets, and external integrations are centralized.
  • Separation of Responsibilities: Forms, analytics, payment provider, email, public policies, and commercial pages have clear data boundaries.
  • Continuous Review: Relevant changes go through tests, lint, build, and security checks before publication.

2. ABUSE PROTECTION

The public layer combines hosting protection with local controls on sensitive endpoints:

  • Edge filters: Blocking of automated patterns and abusive traffic where applicable.
  • Honeypot and lightweight PoW: Forms use invisible fields, lightweight proof-of-work, and browser signals to reduce spam.
  • Protected rate key: Request limits use an IP-derived hash key without exposing raw IPs in notifications.
  • Traffic-volume mitigation: Hosting absorbs part of abusive traffic; the portal still keeps local limits for sensitive endpoints.

3. CROSS-ORIGIN ISOLATION

Security headers implemented for protection against Spectre attacks and data exfiltration:

  • Cross-Origin-Embedder-Policy (COEP): configured to remain compatible with required external resources.
  • Cross-Origin-Opener-Policy (COOP): same-origin, isolates the browsing context against side-channel attacks.
  • Cross-Origin-Resource-Policy (CORP): same-origin, restricts resource access to the same domain.
  • X-Permitted-Cross-Domain-Policies: none, blocks Flash/PDF cross-domain policies.

4. SCRIPT AND CONTENT POLICY

The CSP reduces the chance of unexpected scripts running in the browser:

  • script-src uses a per-request identifier and strict-dynamic.
  • upgrade-insecure-requests forces HTTPS on resources.
  • frame-ancestors 'none' protects against improper iframe loading.
  • External sources are limited to approved domains.

5. DEPENDENCIES AND BUILD

Protection for the dependency chain used by the portal:

  • Versioned lockfile: package-lock.json makes CI/CD installation predictable.
  • npm audit: Critical/high vulnerabilities block the validation path.
  • License Audit: Production license checks reduce legal risk.
  • Dependency inventory: The installed tree remains traceable through the lockfile.

6. APPLICATION ENVIRONMENT

The portal is a Next.js application hosted in a managed environment. The release baseline avoids unnecessary privilege assumptions:

  • Reproducible Build: Versioned package-lock.json and predictable CI installation.
  • Lean Runtime: Public code, API routes, and external integrations are separated by responsibility.
  • No PWA: There is no manifest, install prompt, or offline app-shell. The /sw.js endpoint is only an uninstall tombstone for removing old service workers and caches.
  • No Frontend Secrets: Private payment, email, and automation keys must never appear in NEXT_PUBLIC_*.

7. LGPD CONTROLS & DATA PROTECTION

  • Data Minimization: We collect only what is strictly necessary for each operation.
  • IP Obfuscation: Abuse limits use a server-side hash; internal notifications do not carry raw IP addresses.
  • Strict Validation: Schema validation via Zod with rejection of undeclared fields (.strict()).
  • Data Subject Rights: Data-subject requests follow the applicable legal deadline, with initial triage and internal records.

8. PAYMENT AND DELIVERY SECURITY

  • Stripe Checkout: Card collection happens in Stripe's hosted environment. RET does not store full card numbers, CVV, or sensitive card authentication data.
  • Verified Webhooks: Payment events are checked by signature and timestamp tolerance before fulfillment.
  • Idempotency: Checkout-session creation uses an idempotency key to reduce duplicate-session risk during retries.
  • Private Delivery: Paid products stay outside the public folder and are delivered through temporary links with package manifests and checksums.
  • Checkout Terms: The customer accepts terms, privacy, and, where applicable, specific authorization before payment completion.

9. IMPLEMENTED SECURITY HEADERS

  • Strict-Transport-Security (HSTS): max-age=63072000; includeSubDomains; preload
  • X-Content-Type-Options: nosniff
  • X-Frame-Options: DENY
  • X-XSS-Protection: 0 (disabled in favor of modern CSP)
  • Origin-Agent-Cluster: ?1
  • X-DNS-Prefetch-Control: off
  • Cache-Control: no-store on sensitive routes and pages with language cookies.
  • Referrer-Policy: strict-origin-when-cross-origin
  • Permissions-Policy: Granular restriction of browser APIs (camera, microphone, geolocation)

10. EMAIL SECURITY (DMARC / SPF / DKIM)

Layered protection against spoofing, phishing, and identity forgery:

  • DMARC: v=DMARC1; p=reject, Full rejection policy. Unauthenticated emails are discarded at source.
  • SPF/DKIM: The root domain keeps Zoho as an authorized sender. Transactional email sent through Resend must use a provider-verified domain or subdomain with SPF, DKIM, MX/return-path, and DMARC alignment before any production send.
  • Monitoring: Forensic (ruf), aggregate (rua), bounce, complaint, and suppression signals are treated as operational evidence for blocking, secure reissue, or investigation.

11. VERIFIABLE PROOF

External seals and links, when shown, are point-in-time verification, not permanent guarantees:

  • SSL / Headers: Should be checked in public validators before relevant campaigns.
  • DMCA.com Protection: Content monitoring and takedown when active.
  • Google Safe Browsing / Reputation: Status can change and should be revalidated periodically.
  • Internal Record: Relevant security changes should leave evidence in CI, sanitized logs, and release checklists.

Verifiable security badges, click to audit

Security of this siteDMCA.com Protection Statuscheck it yourself · each seal opens a public test on our domain

Document maintained with security and privacy controls.

DMARC/SPF/DKIM · HSTS em produção · CSP com nonce por rota · logs sanitizados