Data Privacy Protocol

1.0 Data Ingestion

To generate binding cryptographic ledgers, the System ingests the following data points:
- Entity names and legal identifiers.
- Contact vectors (Email addresses, WhatsApp routing numbers).
- System metadata (IP addresses, browser signatures, UTC timestamps).
- Project parameters (Deliverables, financial values, deadlines).

2.0 Gateway Interfacing (Third Parties)

SOWRegistry does not store sensitive financial data (e.g., credit card numbers, UPI PINs). All financial processing is securely handed off to Razorpay.

Routing notifications are executed via the Meta WhatsApp Cloud API and highly secure SMTP servers. By utilizing the System, you authorize the transmission of node data through these specific, encrypted channels.

3.0 Public Ledger Visibility

Certain metadata points (such as the document Registry ID, execution timestamp, node entity names, and current status) may be visible on the public ledger interface to verify cryptographic authenticity. Strict project scope details and contact vectors remain locked and are only accessible to the Originator and Target nodes.

4.0 Data Retention

Because the core function of the System is to provide an immutable baseline for contracts, executed ledger entries and their associated PDF artifacts are stored indefinitely. If a document remains in the INITIATED or PENDING_SIGNATURE state for more than 30 days without execution, the system will automatically purge it to conserve server resources.