Encrypted connections
Your browsing on this website uses HTTPS/TLS to protect information during transmission.
How we protect the data we handle, how we run our clients' infrastructure, and what commitments we hold in writing. No invented certifications.
Encryption in transit and at rest, least-privilege access control, patch management, backups with defined RTO/RPO, and a documented incident response process.
See security practicesThe status of our services is published in real time, never edited after the fact.
See live statusAn active GDPR program, ISO 27001 alignment in progress (not yet certified), and a clear stance on NIS2 to help our clients meet it.
See compliance in detailThe real vendors that touch data in our operation, with purpose and data location disclosed — no surprises.
See the full listResponse times by severity, maintenance windows and service credit, published by tier — Essential, Professional, Enterprise.
See SLAs by tierHow to report a security flaw to us responsibly: scope, what to expect and how fast we respond.
Read the disclosure policyWe don't hold a third-party certification yet, and we won't display a seal we haven't earned. What we can do is publish the actual posture and tell you how to check each point yourself, without asking us for anything.
HSTS with includeSubDomains and preload: the browser refuses to connect over HTTP even before the first visit.
How to check it: Check the Strict-Transport-Security header in developer tools, or the domain on hstspreload.org.
Payment happens on Stripe and MercadoPago. No card number passes through our servers or lands in our logs.
How to check it: At checkout the URL switches to the gateway's domain. The card form is never on ditap.io.
Google Consent Mode v2 starts fully denied, with ads data redaction on. Until you accept, no measurement cookie is written.
How to check it: Open the site in a private window and inspect cookies before touching the banner: there is no _ga.
Error monitoring uses the European data residency, in Germany. No transfer outside the EEA for that processing.
How to check it: It's declared in full on the sub-processors page.
Content-Security-Policy, X-Frame-Options set to DENY, nosniff, Referrer-Policy, and Permissions-Policy blocking camera, microphone and geolocation.
How to check it: Paste ditap.io into securityheaders.com and read the result.
Emails carry List-Unsubscribe with one-click POST (RFC 8058): opting out is immediate and doesn't depend on someone processing it by hand.
How to check it: In Gmail, the unsubscribe button appears next to the sender.
Service-specific scope
Service-specific scope
Service-specific scope
1 SLA tiers · 9 sub-processors — See compliance in detail
Not yet. We align with ISO 27001's control domains and operate with that discipline, but we don't hold a third-party certification — and we won't claim we do. Detail at /trust/compliance.
It depends on the vendor: hosting on Vercel, database on Supabase, DNS on Cloudflare, payments on Stripe/MercadoPago. Full detail, with data location per vendor, at /trust/sub-processors.
Through our responsible disclosure policy at /security/disclosure, with a direct contact channel and a committed response timeframe.
Each managed-service tier defines a service credit for missed response times, detailed at /trust/sla. The signed contract with each client takes precedence over this public page.
Security questionnaires, a DPA draft, or the technical detail of a specific project — write to us and we'll coordinate it.
Email hola@ditap.ioPEOPLE, PROCESS AND SUPPORT
A clear first conversation. A written proposal. Next steps agreed together.
We discuss your needs and set out objectives, deliverables, timelines and costs in the proposal.
We agree on responsibilities, stages and the information needed to move forward. Launch and training are defined for each project.
We agree on support channels, hours and scope so you know whom to contact.
A written proposal with scope, deliverables, stages, pricing and terms, including any additional services you choose.
We define contact channels, hours and support scope in the proposal, so you know what is included and how to request help.
We review what information is needed, who can access it and how it is shared. For software systems, we also agree on backup, retention and export conditions.
TECHNOLOGY THAT SUPPORTS YOUR TRUST
Your browsing on this website uses HTTPS/TLS to protect information during transmission.
Vercel, this website’s hosting provider, documents AES-256 encryption for data stored on its infrastructure.
Each project defines its services and the protection needs of information and operations.