Security
Effective date: November 19, 2026
Get AI Explanation
Need help understanding this document? Get an AI-powered explanation from your favorite AI models.
This page describes how Signa protects your account, your API keys, and the searches you run. It lists the controls we have in place today and the ones we are still working towards.
What we protect
Most of the trademark data Signa serves is public. It comes from official trademark registries and public corporate-data sources. What is not public is how you use it: the names you search, the marks you watch, your account details, and your API keys. Your searches can reveal plans that have not been announced, such as a product name or a mark a client intends to file. We treat that as confidential.
- Your searches, watches, and request logs are scoped to your organization. No other customer can see them.
- We do not sell or publish customer queries. We pass customer content to service providers only where that is needed to deliver a feature you use or to run the service, as our sub-processors page describes.
Infrastructure
Signa's API runs on Amazon Web Services (AWS) in the US East region. Our website and dashboard are served through Vercel.
Data residency: API request logs, query data, watches and the other content you create through the API are stored in AWS US East. Sign-in and account records are stored with Neon, our database provider for authentication, also in the US East region. Content you send to AI-assisted features is also sent to the model provider and can pass through Vercel on the way.
Network: Databases, search clusters, and caches run in private subnets and are not reachable from the internet. Traffic to the API through AWS CloudFront is filtered by a web application firewall (WAF).
Encryption
In transit: All connections to the Signa API and website use TLS 1.2 or higher. HTTP requests are redirected to HTTPS.
At rest: Our database, search cluster, cache, and object storage are encrypted at rest with AES-256, using AWS-managed keys.
API keys: API keys are stored only as hashes. We cannot see or recover your key after it is created. If you lose a key, revoke it and create a new one.
Access control
Customer accounts: API access requires an API key. You can sign in with email and password, or with Google, which uses your Google account's security settings, including multi-factor authentication where you have turned it on.
Internal access: Access to production is limited to the people who need it to run the service. The AWS root account is protected by multi-factor authentication. Deployments run through our CI/CD pipeline using short-lived credentials rather than stored keys.
Third parties: Our infrastructure and authentication providers operate the systems that store production data, under their service agreements. Sub-processors receive only the data they need for their function. The full list is on our sub-processors page.
Application security
Development: Every change goes through a pull request and automated checks before it is deployed.
Dependencies: Third-party dependencies are scanned for known vulnerabilities whenever they change and every six hours against our main branch, from which production is deployed.
API protections: The API authenticates requests with API keys and applies rate limiting and input validation.
Patching: We fix vulnerabilities based on severity. Our targets, counted from when a fix is available, are goals and not guarantees:
| Severity | Target remediation time |
|---|---|
| Critical | 24 hours |
| High | 7 days |
| Medium | 30 days |
| Low | Next release cycle |
Monitoring and incident response
Logging: API requests are logged. A daily job removes search text, IP addresses, user agents and error details from log records more than 90 days old, and the rest of each record is kept for up to five months. Network access logs at our edge do not record the URL path or query string of a request. Zero data retention for API requests is available by agreement. Administrative actions on our AWS account are recorded in an audit log.
Alerting: Automated alerts cover errors and service health.
Incident response: We have a written procedure for detecting, containing and investigating security incidents and for telling affected customers.
Breach notification: If a personal data breach affects data we process for you, we will notify you without undue delay and within 48 hours of becoming aware of it, as our DPA provides. Where the GDPR requires it, we will also notify the Office of the Commissioner for Personal Data Protection of the Republic of Cyprus. See our Privacy Policy for details.
Backups and availability
Backups: Our database is backed up continuously with point-in-time recovery, and backups are kept for 7 days. Backups are encrypted.
Recovery objectives (planning targets):
| Metric | Target |
|---|---|
| Recovery Point Objective (RPO) | 1 hour |
| Recovery Time Objective (RTO) | 4 hours |
Uptime: Current and historical uptime is on our status page at status.signa.so.
Compliance
| Framework / Regulation | Status |
|---|---|
| GDPR (EU General Data Protection Regulation) | Applies. Our Privacy Policy and DPA set out how we meet it |
| UK GDPR | Our DPA covers customers who are subject to it. Transfers from the UK to Signa are transfers to the EEA, which UK law permits; the DPA includes the UK International Data Transfer Addendum as a fallback |
| Cyprus Data Protection Law (Law 125(I)/2018) | Applies |
| EU AI Act | Monitoring |
| SOC 2 Type II | Planned, no date set. Not held today |
| ISO 27001 | Planned, no date set. Not held today |
| Independent penetration test | Planned, no date set. Not done yet |
Our infrastructure providers, including AWS, hold their own SOC 2 and ISO 27001 certifications.
Security reviews
If your organization has a vendor security questionnaire, send it to security@signa.so and we will answer the questions relevant to your use of the service. We may do so with existing documentation. Our Data Processing Agreement and sub-processor list are public, and we can send a countersigned copy of the DPA on request.
Responsible disclosure
If you find a security vulnerability in Signa, please report it to us.
How to report: Email security@signa.so with a description of the issue, steps to reproduce, and any supporting evidence.
What we commit to:
- Aim to acknowledge your report within 2 business days
- Aim to give an initial assessment within 5 business days
- Keep you informed while we fix it
- Not pursue legal action against researchers who act in good faith and follow this policy
What we ask:
- Give us reasonable time to fix the issue before public disclosure
- Do not access, modify, or delete other customers' data
- Do not run denial-of-service tests against production
- Do not use social engineering against Signa staff
Contact
Signa Technologies Ltd
Registration No. HE 495212
Fellachoglou 35, Mouttallos
8016 Paphos, Cyprus
Security: security@signa.so Privacy: privacy@signa.so Legal and DPA requests: legal@signa.so
This page was last updated on November 19, 2026.