Privacy Policy

Bulrk is designed around business risk response, vendor exposure, evidence collection, Watchtower alerts, Impact Radius mapping, and emergency reporting. This Privacy Policy explains the types of information Bulrk may collect and how that information is used during beta.

1. Information Bulrk may collect

Bulrk may collect business signup details, account details, customer workspace details, vendor records, vendor contact information, risk events, Watchtower alerts, evidence request records, uploaded documents, generated emails, reports, audit logs, consent preferences, contact form messages, and administrative status information.

2. How Bulrk uses information

Bulrk uses information to provide Emergency Risk Shield workflows, vendor evidence requests, exposure summaries, Impact Radius maps, Watchtower alerts, risk score explanations, evidence logs, reports, beta onboarding, account administration, customer support, and product improvement.

3. Vendor evidence and documents

Customers are responsible for ensuring they have permission to upload, request, review, store, or share vendor evidence. Vendors should only submit documents approved for customer/security review. Bulrk is intended to help organize evidence, not to independently certify that evidence is complete, accurate, or legally sufficient.

4. Account and administrator access

Bulrk administrators may review account status, beta access, customer support requests, abuse signals, audit logs, email delivery status, and operational metadata to manage the beta safely. Customer access may be approved, placed under review, suspended, or restricted where needed.

5. Data storage

Data storage depends on deployment. In a Bulrk-hosted deployment, records are stored in Bulrk-controlled infrastructure. In a customer-controlled deployment, records remain in the customer's selected hosting environment. Customers should configure private storage, backups, user permissions, and secure email delivery before uploading sensitive documents.

6. Security posture

Bulrk is designed to support HTTPS, private document storage, role-based access, rate limiting, audit logs, secure sessions, password hashing, and secure email delivery. During beta, customers should validate their deployment before storing highly sensitive or regulated documents.

7. Cookies and consent

Bulrk may use essential cookies or similar settings to support login sessions, security, consent choices, and beta functionality. Optional preferences may help improve the user experience and product quality.

8. Retention and deletion

Customers should retain vendor records and evidence only as long as needed for business, audit, security, or legal purposes. Bulrk is designed to support review and deletion workflows as the beta matures.

9. Contact

Use the Suggestions / Contact page to submit privacy questions, beta feedback, or data handling concerns.