LnkAppSecurity
Security posture you can review
Review the posture without talking to sales: encryption, GDPR lifecycle, self-serve SSO, and certificate-fleet monitoring — all documented in public.
A security posture you can review
Everything a security review needs is documented in public: how data is encrypted, how the GDPR lifecycle works end to end, and how your team gets in. Each statement below is verifiable against the published documentation.
- AES-256-GCM envelope encryption; keys rotate without re-encrypting data Verifiable · quarterly
- Full GDPR lifecycle: deletion cascade and complete export Verifiable · quarterly · per-release
- SAML/SSO configured self-serve - no sales call required Verifiable · quarterly
In depth
This summary is written for the person who has to sign off. Every row is a verifiable statement backed by public documentation — read the source before you approve anything.
| Area | What holds | Where to verify |
|---|---|---|
| Encryption at rest | AES-256-GCM envelope encryption; keys rotate without re-encrypting data Verifiable · quarterly | Security documentation (encryption protocol) |
| Data lifecycle | Full GDPR lifecycle: deletion cascade and complete export Verifiable · quarterly · per-release | Security + GDPR documentation |
| Access | SAML/SSO configured self-serve - no sales call required Verifiable · quarterly | Security documentation |
Notes for review:
- Key rotation is designed in. Envelope encryption means keys rotate without re-encrypting stored data — rotation is an operation, not a migration.
- Deletion is a cascade, export is complete. The GDPR lifecycle covers both directions: erasure that propagates, and an export that holds everything.
- SSO does not gate on a sales call. SAML/SSO is configured self-serve, so your rollout timeline is yours.
Every certificate, watched
SSL certificates across all your domains, watched around the clock. You get alerted before expiry — before your client notices anything at all. The product shows the fleet whole: every domain, every certificate, its state and its clock.
- Every domain certificate watched around the clock, with alerts before expiry Verifiable · per-release
In depth
A certificate problem on a customer-facing domain is a trust problem, and it rarely announces itself in advance to the person who owns the consequence. The SSL fleet instrument exists so that it announces itself to you.
What the instrument shows:
- The fleet, whole. Every domain you run through LnkApp appears with its certificate state — one view, no per-domain spelunking.
- The clock. Time to expiry is tracked continuously for each certificate.
- The alert path. Warnings go out through your configured alert channels before expiry, while there is still time to act calmly.
This is shipped product behavior, not a roadmap item — it reflects the monitoring dashboards and alert channels as they exist in the product.
Service levels, measured
This is not a summary we wrote — service levels are measured continuously, straight from the product's own telemetry surface, and surfaced through its API. If you are deciding whether your traffic is safe with us, decide on the measurements, not on our adjectives.
- Service levels are measured and visible - watch them yourself Measured · live
In depth
Every service level we publish is measured continuously and surfaced through the product API. The measurement you act on is the current one, read straight from that surface in the product — with its source and timestamp, not a marketing snapshot. There is no separate feed for the website.
Two properties matter for a reliability review:
- The metrics are live. They come straight from product telemetry, so the figure you act on is the figure in production right now — not a number we typed.
- The metrics stay visible. Watching them is not an evaluation-day privilege — the point of the claim is that you can keep watching after you sign up.