Legal
Effective Date: June 10, 2026
This Privacy Policy describes how Blocklog ("we", "us") collects, uses, and protects information provided by users and trial participants ("you") when using our service at blocklogsecurity.com.
Blocklog is an early-stage AI forensic debugging and audit infrastructure product operated independently by its founder, based in Delhi, India, pending formal incorporation. We provide engineering and compliance teams with decision-time input snapshots, input staleness detection, counterfactual replay, causal chain tracing, and forensic audit report generation for AI agents — running in shadow mode with no impact on production behaviour.
Contact: founder@blocklogsecurity.com
When you integrate Blocklog into your AI systems, we collect the forensic and audit data your systems generate and send to our service. This may include:
You are responsible for ensuring that any data submitted to Blocklog is appropriate to share with a third-party service. Do not submit data containing raw personally identifiable information, authentication credentials, payment card data, government identification numbers, protected health information, or other regulated data. Log metadata, decision records, and agent operational data that does not contain the above categories is the intended use of the Service.
We collect basic operational and usage data to understand how the product is being used, including:
We use the data we collect to:
We do not sell your data.
We do not use your data for advertising.
Where applicable, including for users located in jurisdictions that require a legal basis for processing personal data, we process information on the following grounds:
Data is stored and processed using Amazon Web Services (AWS) cloud infrastructure. We implement technical and organisational safeguards appropriate for an early-stage software service, including encryption in transit, access controls, monitoring, and security best practices.
No internet-connected system can be guaranteed to be completely secure. We encourage trial and pilot participants not to submit sensitive or regulated data during this phase.
Blocklog is operated from India and uses infrastructure that may be located in the United States or other jurisdictions. By using the Service, you acknowledge that information may be transferred to, stored in, and processed in countries outside your country of residence, where data protection laws may differ. We take commercially reasonable measures to protect data during such transfers.
We retain email and communication data for as long as you are an active user and for a reasonable period thereafter.
Agent decision records, log data, and forensic report data submitted through the API are retained for the duration of your active use of the Service unless deletion is requested or operational needs require earlier removal.
We may retain limited information where necessary to comply with legal obligations, resolve disputes, or enforce agreements.
You may request:
Requests can be sent to: founder@blocklogsecurity.com
We will make commercially reasonable efforts to process requests within 30 days.
We use trusted third-party service providers to operate and improve the Service. These providers may process information only as necessary to provide their services to Blocklog:
We do not sell or rent personal information to third parties.
If we become aware of a material security incident affecting data under our control, we will make commercially reasonable efforts to notify affected users without undue delay via email, dashboard notices, or other appropriate channels. Notifications will include information regarding the nature of the incident, affected systems, and recommended actions where available.
Blocklog is not intended for individuals under 18 years of age. We do not knowingly collect personal information from minors.
We may update this Privacy Policy as the Service evolves. Active users will be notified of material changes via email at least fourteen (14) days before such changes become effective. The effective date shown at the top of this document reflects the latest version.
Questions, requests, or privacy-related concerns may be directed to: