Logo.dev security: DPA, subprocessors, data retention
How Logo.dev handles data: SOC 2 status, DPA availability, subprocessors, retention, and GDPR. We process public brand data and minimal request metadata.
Logo.dev serves publicly available company logos and brand metadata. The
personal data we process is limited to account details, API request
metadata, billing (handled by Stripe), and website analytics. We process no
special-category data.
This page summarizes how Logo.dev handles data, for a security or procurement review. The binding terms are in our privacy policy, DPA, and subprocessor list. In a contract, refer to those documents, not to this summary.
A DPA is available and incorporates the EU Standard Contractual Clauses for international transfers. It applies once both parties sign it. Read the DPA, or email team@logo.dev to execute one.
We keep request logs and account data only while we need them to run the service, meet billing and legal obligations, and investigate abuse. The privacy policy covers retention by data type.
Logo.dev processes data mainly in the United States. The subprocessor list gives each provider’s location. For users in the EEA, UK, and Switzerland, transfers rely on the EU Standard Contractual Clauses in our DPA.
We process only the personal data listed above, and we never sell it. We support these data-subject requests: access, correction, deletion, restriction, objection, and portability. The privacy policy covers the legal bases and how to make a request. To delete your account and its data, see Delete your account.
Logo.dev does not yet hold SOC 2 or another formal security certification. We are working toward SOC 2 and run automated vulnerability scanning. Our infrastructure providers, including AWS, Vercel, and Cloudflare, maintain their own SOC 2 and ISO 27001 certifications.Data is encrypted in transit with TLS 1.2 or higher and at rest with AES-256. Access to infrastructure requires multi-factor authentication and follows least-privilege controls.