How we protect your data

This is a courtesy translation provided for convenience. The Spanish version is the legally binding text.

01. Authentication and access

• Corporate emails authenticated with DKIM, SPF, and DMARC on the aiginer.com domain. This prevents third parties from spoofing internal addresses in phishing attempts.
• Two-factor authentication (2FA) mandatory on all internal administrative accounts (hosting panel, repositories, DNS, email accounts).
• Access to the production server only via SSH keys (no password). Keys are rotated when a collaborator no longer needs access.
• Client panel sessions protected with short-lived signed tokens and controlled refresh.

02. Encryption

• HTTPS enforced across the entire site via Cloudflare with TLS 1.2+ and active HSTS preload (HTTP is completely blocked).
• Sensitive data encrypted at rest within the production database, with the master key kept outside the repository.
• Authenticated symmetric encryption (AES-256-GCM) for third-party credentials that clients delegate to us to manage (a vault with data associated to the tenant to prevent cross-client exposure).

03. Per-client data isolation

• Multi-tenant PostgreSQL with Row-Level Security: every query is restricted to the rows of the authenticated tenant, even if the application had a logic flaw.
• Additional application-level check: every endpoint verifies the user's membership in the tenant before returning data.
• We never use one client's data to train models or to benefit another client.

04. Cryptographic traceability of actions

• Every sensitive action (configuration changes, administrative access, data exports) is logged in an audit_logs table.
• Each record includes a SHA-256 hash linked to the previous record. This forms an immutable chain: any tampering or subsequent deletion is detected when the verification is run.
• For regulated clients, these records constitute admissible evidence: we can demonstrate who did what and when, with no possibility of silent modification.

05. Backups and disaster recovery

• Full dump (pg_dump) of the production database every day.
• 3-2-1 rule: three copies, two different media, one geographically separate. The secondary copy is synchronized daily to a second physical location within the EU.
• Automated monthly restore drill: we load a full backup into an isolated environment and verify the integrity of the audit_logs hash chain. If the chain fails verification, the copy is discarded.

06. Network and anti-bot protection

• Cloudflare WAF active with a managed ruleset and custom rules that block known scanners (attempts on /wp-admin, /.env, /phpmyadmin, etc.).
• Bot Fight Mode enabled to mitigate basic automated traffic.
• Invisible Cloudflare Turnstile on all public forms (contact, audit). Combined with a hidden honeypot and minimum-fill-time validation, this blocks virtually all spam and form-scraping attacks.
• Rate limiting on the intake webhooks.

07. Monitoring and incident response

• Public status page at status.aiginer.com with 7 monitored services (API, panel, automations, email, etc.) and historical uptime.
• System watchdog every 2 minutes checking health and latency.
• Automatic escalation: a WARNING is issued after 4 minutes, the affected container is automatically restarted after 12 minutes, and it is escalated to CRITICAL with human intervention after 24 minutes.
• Real-time alerts sent to the internal channel so any degradation is addressed within minutes.

08. Confidentiality of the model stack

• Shara, our SaaS product, exposes models to clients using internal aliases (Prelude, Sonata, Symphony, Concerto). The actual provider behind each alias is confidential information.
• This protects you as a client: if a provider raises prices, degrades a model, or discontinues it, we replace it with an equivalent one without your team having to relearn anything.
• The stack details are only shared under NDA with Max and Local Plan clients, as part of the due diligence process.
• All models run on providers that comply with the GDPR and offer no-training clauses on client data.

09. Vulnerability reporting

• Dedicated addresses: security@aiginer.com (es) and security@aiginer.com (en).
• Committed response times: acknowledgment in under 24 business hours; substantive response with an action plan in under 5 business days.
• Patch deployed within 30 days for critical and high-severity vulnerabilities.
• Coordinated disclosure with the researcher: we give credit (if desired) and publicly announce the fix once it is in production.

10. Hardening roadmap (honest about what we don't have yet)

• SOC 2 Type II: in preparation. Timeline subject to product maturity and client volume.
• ISO 27001: under evaluation specifically for Local Plan clients (on-premise deployments where it adds differential value).
• Independent external penetration test: planned pre-GA of the product.
• Public bug bounty: planned after the external penetration test. In the meantime, we maintain a responsible disclosure channel.

Have specific questions about our security?

If you need additional information for a procurement questionnaire, an internal audit, or a risk analysis, write to us. We handle reasonable requests without requiring a prior contract.

Back to the Trust Center.