Security at Anliego

Our approach

Anliego is being built security-first. We are still pre-launch, so the items on this page describe the commitments and design principles we are engineering into the product rather than a finished compliance record. We would rather state honestly what we are building toward than claim certifications we do not yet hold.

Our guiding principles are simple: collect the minimum data needed to do the job, encrypt it everywhere, restrict who can touch it, and make it easy for you to export or delete. We treat the security of your review data and your customers' data as a core feature, not an afterthought.

Encryption

We protect data both while it moves and while it is stored.

• In transit: all connections to Anliego and its APIs are served over HTTPS using modern TLS. We do not accept unencrypted traffic.
• At rest: application data is stored in managed databases and object storage that provide encryption at rest by default.
• Secrets and credentials (such as API keys and OAuth tokens) are stored using managed secret storage and are never committed to source control or exposed in client-side code.
• Tokens used to access third-party services on your behalf are scoped, stored encrypted, and used only to perform the actions you have asked us to perform.

Access control and least privilege

Access to production systems and customer data is restricted to the smallest set of people and services that genuinely need it.

• Role-based access controls govern what each account and internal user can see and do.
• We grant least-privilege access by default and review access as the team and product evolve.
• Multi-factor authentication is required for staff access to administrative and infrastructure systems.
• Administrative and sensitive actions are recorded in audit logs so activity can be traced and reviewed.

Minimal Google permissions

To monitor and respond to a business's reviews, Anliego connects to Google through the Google Business Profile API and the Places API. We deliberately request the narrowest access that makes the product work.

• We request only the scopes needed to read and respond to reviews for the Google Business Profile locations you connect and authorize.
• We do not ask for access to unrelated Google data, and you can revoke our access from your Google Account at any time.
• Our use of data received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
• We use Google-provided data only to deliver and improve the review features you have enabled, never to build advertising profiles or to sell data.

Infrastructure and sub-processors

We build on established, security-conscious infrastructure providers rather than running our own data centers, so that hardening, patching, and physical security are handled by specialists. We engage a small number of reputable sub-processors to operate the service.

• Vercel for application hosting and content delivery.
• Neon (serverless Postgres) for our primary application database.
• Stripe for subscription billing and payment processing. Card details are handled by Stripe; Anliego does not store full card numbers.
• Reputable third-party email and SMS providers for transactional messages and review-request campaigns you choose to send.
• We choose providers with strong security track records and recognized compliance programs, and we limit the data each one receives to what it needs.

Multi-tenant data isolation

Anliego is a multi-tenant service, and keeping each customer's data separate is a primary design goal.

• Every record is associated with its owning account (tenant), and application queries are scoped so that one customer cannot read or modify another customer's data.
• Authorization checks are enforced on the server for every request, not just hidden in the interface.
• We design our data model and access paths around tenant isolation and test for it as the product grows.

Backups and resilience

We aim for your data to be durable and the service to recover gracefully from failures.

• Our managed database provider maintains automated backups with point-in-time recovery.
• Hosting and delivery run on resilient cloud infrastructure designed for high availability.
• We are building and refining our backup-restore and recovery procedures so we can respond to incidents without losing your data.

Secure development

Security is part of how we write and ship code, not a separate step at the end.

• Changes go through code review before reaching production.
• We use automated dependency scanning to catch known vulnerabilities in the libraries we rely on, and we update them promptly.
• We keep environments separated and avoid using real customer data in development and testing wherever possible.
• We follow established secure-coding practices to guard against common web application risks.

Monitoring and logging

We keep visibility into how the system is behaving so we can detect and respond to problems.

• We collect application and infrastructure logs to investigate errors and suspicious activity.
• We monitor availability and key operational signals across our hosting and database providers.
• We aim to retain logs only as long as they are useful for security and operations, and to limit access to them.

Data portability and no lock-in

Your data is yours. We design Anliego so you are never trapped in it.

• You can export your reviews, replies, and related data so you can keep your records or move elsewhere.
• If you close your account, we provide a way to retrieve your data and then delete it according to our retention practices.
• We avoid proprietary formats that would make your information hard to use outside Anliego.

Responsible disclosure

We welcome reports from security researchers and customers. If you believe you have found a vulnerability or a security issue in Anliego, please tell us so we can fix it.

• Email security@anliego.de with details and, where possible, steps to reproduce the issue.
• Please give us a reasonable opportunity to investigate and remediate before any public disclosure.
• Act in good faith: avoid privacy violations, data destruction, and service disruption while testing.
• We will acknowledge legitimate reports and keep you informed as we work through them.

Compliance posture

As a DACH-first product that also serves US customers, we design with both EU and US expectations in mind. We are pre-launch and do not currently hold formal certifications; the following describes our posture and direction.

• We build to be GDPR-ready: data minimization, a documented sub-processor list, support for data subject rights, and Data Processing Agreements where appropriate.
• Our review tools are designed to align with FTC guidance on consumer reviews and endorsements, including our compliance-by-design stance against suppressing or gating honest reviews.
• We follow industry-standard security practices and are designing toward recognized frameworks such as SOC 2 and ISO 27001, though we make no claim of being certified against them today.
• As Anliego matures, we intend to strengthen our controls and pursue independent validation, and we will update this page to reflect our actual status.

Contact

For security questions, vulnerability reports, or details about our practices and sub-processors, contact us at security@anliego.de. We will keep this page updated as our security program evolves toward and beyond launch.