Updated 18 Nov 2026 · Version 2026-11-18-ts1
Security
1. Protection and responsible use
Intake applies field validation, size limits, expiring signed tokens, origin checks, basic abuse prevention and retry identifiers. Administrative access requires WordPress permissions. Integration secrets remain server-side, not in public code.
2. Limits and availability
We do not claim security certification, completed penetration tests, encryption at rest or invulnerability. Hosting, accounts, updates, backups and HTTPS depend on operational configuration. Security is continuous and failures remain possible.
3. Report an issue
Email angariar@angariar.com with subject Security. Provide the page, observed behavior and minimal reproduction steps. Do not include passwords, private keys, tokens, other users’ data or destructive exploitation. Do not access others’ accounts or copy data to prove an issue.
4. Incidents and follow-up
Reports are assessed for relevance and urgency. Where required, incidents and notifications are handled under applicable law. This is not a bounty program, promise of immediate response or permission for intrusive testing.
5. Anti-bot verification
We use Cloudflare Turnstile to protect this form against abuse. Your browser loads the Cloudflare component, which processes technical connection and browser data to verify access. Our server sends the verification token to Cloudflare without your name, email, company or message. A random request identifier binds verification to submission. We do not store the token in the commercial record or send it to HubSpot. The service may involve international processing; see Cloudflare privacy information. Its purpose is security, not audience analytics or advertising.

