Security
Security position, stated with its evidence
No certifications, audits or SLAs
Toros Ricos OÜ holds no security certification for Bobby DB, has commissioned no penetration test, publishes no audit report and offers no uptime or support commitment. Any such claim found elsewhere would be untrue.
Design principles
The properties the implementation is required to satisfy as it is built.
- Workspace is the isolation boundary
- Every collection, group, entry, release and key belongs to exactly one workspace. Authorization is designed to resolve the caller's workspace first, so a query cannot accidentally span tenants.
- Row-level authorization, not application filtering
- Access rules are intended to live in the database as row-level security policies rather than in application query builders, so a forgotten filter in application code cannot expose another tenant's rows.
- Keys are hashed, shown once
- An API key is intended to be stored only as a hash. The plaintext is displayed once at creation and never again, so a database read cannot recover usable credentials.
- Keys never travel in a URL
- Keys are accepted only in a request header. URLs leak into server logs, proxy logs, referrer headers and browser history; headers do not.
- Least-privilege scopes
- A key carries read scope or write scope for one workspace. A public read client never needs a write-capable credential.
- Encryption in transit
- All traffic is served over HTTPS. Plain HTTP is intended to redirect rather than serve.
- Human review before publication
- A release is created by an explicit human review step, so bad automated input cannot silently become the data every consuming application reads.
- Immutability as a safety property
- Because a published release cannot be edited, a compromised or mistaken write cannot rewrite history that consumers already pinned.
- No secrets in values
- Bobby DB is not a secrets manager. Customers are instructed not to store credentials, tokens or payment card data in entry values, and the product is not designed to protect them.
Control status today
Every row states what is true now, not what is intended. “Planned” means designed but absent.
| Control | Status | Evidence |
|---|---|---|
| HTTPS-only public website | Implemented | Served over HTTPS by the hosting platform today. |
| No account, session or credential surface on this site | Implemented | Nothing on the public site signs a user in or issues a key, so there is no credential to steal here. |
| No analytics, advertising or tracking cookies | Implemented | The site sets none, so there is no third-party tracking surface. |
| Backend platform provisioned, no schema or data | Implemented | A managed backend is connected. No tables, no policies, no rows, no users, no keys exist yet. |
| Row-level security policies | Planned | Cannot exist yet: there are no tables to protect. |
| Hashed API keys with one-time display | Planned | No key issuance exists. |
| Rate limiting and metering | Planned | No API is deployed to meter. |
| Audit trail of reviews and releases | Planned | No review or release pipeline exists. |
| Penetration test | Not available | None has been carried out. No report exists. |
| SOC 2, ISO 27001 or similar certification | Not available | None held, none in progress, and none claimed. |
| Uptime SLA or availability commitment | Not available | None offered. No uptime figure is published because none has been measured. |
| Published sub-processor list and transfer safeguards | Not available | Final production configuration is not fixed, so a truthful list cannot be published. |
What this means for you
Nothing of yours is here yet
There is no way to create an account, upload content or issue a key, so Bobby DB holds no customer data of any kind.
Evaluate the model, not a promise
The isolation and key-handling model above is what to scrutinise now. Ask for evidence before trusting any control at launch.
Reporting a problem
No security contact address or disclosure programme is published yet. Publishing one before it is monitored would be worse than publishing none.
This page will be revised as controls are implemented. A control moves from Planned to Implemented only when it can be demonstrated, not when it has been designed.