This page describes verified implementation and supplied hosting facts, not a certification or a completed security audit.
Reporting a concern
Our monitored security contact is hello@kibihq.com. Reports reach the Kibi team for investigation. Use the subject Security report for a suspected vulnerability or incident.
Include the affected service or page, when you noticed the issue, its possible impact and safe reproduction steps. Redact customer data and secrets from any screenshots. Do not access other customers’ records, disrupt service or send passwords, tokens or private files as evidence.
Kibi is operated by StritMedia, Aurora Waterfront, 12th Floor, Kolkata 700091, West Bengal, India. We do not promise round-the-clock monitoring or a fixed response time.
Access and workspace separation
Kibi authenticates users and checks workspace membership and role for protected operations. The backend uses scoped database access and row-level security to separate customer workspaces. Owner controls govern team access, exports and deletion. An audit history records supported administrative and record changes.
These controls reduce risk; they do not make every customer configuration safe or prove the absence of a vulnerability. We do not claim that every action is immutable, that all support access is impossible, or that a marketing page substitutes for a penetration test.
Connections and credentials
The public service uses HTTPS. Production sign-in uses protected session cookies, and provider credentials are encrypted in the application rather than placed in customer export archives. This is not a claim of end-to-end encryption: the service must process records and messages to provide the requested functions. We have not verified encryption at rest for every database, disk, export and backup, so do not represent that as a completed control.
Public quote, invoice and export links may grant access to their intended recipient. Treat a private link like a secret, share it only with the intended person and contact the business if it is disclosed. Export download links expire after 24 hours.
Hosting and resilience
The operator confirms primary US customer databases on Leaseweb US servers and Indian customer databases on Contabo servers in Mumbai. Cloudflare delivers/protects the websites; Brevo handles transactional service email. Provider and international-access details are in the provider register and privacy policy.
Ordinary on-server database backups use a 14-day rotation. Deleted workspace records may remain in those backups for up to 14 days after the actual purge, provided scheduled backup and cleanup jobs succeed. This does not establish off-host disaster recovery, uploaded-media coverage, manual/provider-copy deletion or the Mumbai backup schedule. Those items remain to be verified. We do not publish an uptime guarantee, recovery-time guarantee, SOC 2/ISO certificate or GDPR certification that has not been established.
Export and deletion
Workspace owners can request generated exports and schedule deletion in Data & privacy. See the deletion instructions for the 30-day cancellation window, remaining trial marker, provider limitations and backup exceptions.
How we handle an incident
Our basic response process is:
- Record and assess. Log the report and when it was received, identify the affected service and decide who needs to investigate.
- Contain the risk. Limit affected access or connections where needed, protect relevant evidence and avoid unnecessary exposure of customer information.
- Establish the impact. Determine what happened, which workspaces or data may be affected and the likely consequences for people. Record what is known and what is still being checked.
- Notify and update. If we become aware of a personal-data breach affecting data we process for a customer, inform that customer without undue delay. Share the known scope, likely effects, actions taken and practical next steps; provide further information as it becomes available.
- Fix and recover. Address the cause, check the affected service before restoring normal operation and monitor for recurrence.
- Review and document. Keep the incident timeline, evidence, decisions and remedial actions, including changes needed to reduce a repeat.
Where StritMedia acts as controller, we separately assess and make any required regulatory or individual notifications under the applicable law. Notification duties depend on our role and the incident; this is not a promise that every event requires a public announcement or that one deadline applies to every situation. See the ICO’s personal-data breach guidance for the UK controller/processor distinction.
What your team should do
Use individual authorised accounts, remove departing members, restrict owners to people who need that role, protect email accounts used for sign-in and revoke connections you no longer need. Import only necessary data, check who receives public document links, and configure messages and outcome signals with appropriate notices and lawful permissions.