Frequently Asked Questions

1. General Overview & Purpose

A data clean room is a secure collaboration environment that allows multiple participants to leverage data assets for mutually agreed-upon use cases while ensuring strict data access limitations.

Data Clean Rooms help organizations address key challenges in data sharing, including:

  • Consumer Trust – Ensures privacy while enabling actionable insights.
  • Loss of Scale in Addressability – Adapts to a privacy-first world without diminishing audience reach.
  • Risk to Business & Reputation – Reduces exposure to regulatory violations or misuses of data.
  • Secure data collaboration between owners and partners.
  • Compliant data monetization while protecting consumer privacy.
  • Audience enrichment & sharper targeting through privacy-preserving data operations.
2. Privacy & Compliance

Saptharushi’s multi-party federated clean room:

  • Implements SHA-256 hashing for Personally Identifiable Information (PII).
  • Enforces differential privacy controls with configurable security settings.
  • Uses distributed queries to prevent direct data exposure.
  • Records all transactions immutably on blockchain for transparency.

Yes, Saptharushi DCR is GDPR-compliant, adhering to Section 30 (data provenance requirements), and also meets HIPAA guidelines for secure data processing in healthcare use cases.

No, hashed PII data prevents reidentification and is classified as non-PII under regulations like CCPA.

Users can incorporate three levels of noise/distortion (High, Medium, Low), to the queries ensuring varying levels of non-traceability to the consumer data while extracting valuable insights from the datasets.

  • SHA-256 hashing prevents unauthorized data access.
  • Federated queries eliminate direct exposure of raw data.
  • Blockchain ledger maintains immutable transaction records.
  • Merkle proofs ensure data provenance and integrity checks.
3. Data Ownership & Storage

Data remains fully under control of the data owner, stored in an off-chain database within their private cloud environment.

No, at no point does PII data leave the owner’s infrastructure—ensuring security and compliance.

The data owner retains complete control over their data within the Private Configuration (PQS) setup.

No, Saptharushi acts only as a technology provider and does not store any participant data.

4. Architecture & Technology

Saptharushi DCR combines blockchain-based transparency with federated data processing, ensuring privacy while enabling multi-party collaboration.

  • Client Agent – A Private Querying Server (PQS) – Houses hashed first-party data with consent strings, a provenance node and chosen ETL pipelines, fully controlled by the data owner.
  • Federated Agent – A Federated Querying Server (FQS) – Offers various analytical applications through querying multiple PQS instances enabling audience discovery, engagement and attribution.

FQS allows multiple participants to collaborate in a privacy-first manner, enabling secure matching without raw data exchange.

Blockchain is used to:

  • Maintain immutable records of data operations.
  • Validate audience matching queries via cryptographic proofs.
  • Ensure compliance with data regulations by providing a transparent audit trail.
5. Data Collaboration & Permissions
  • PII data must be hashed before collaboration.
  • Private Configuration (PQS) must be hosted in the data owner’s cloud.
  • A mutually agreed identifier must be selected.

The Federation collectively owns the FQS node, ensuring no single entity has undue control.

Yes, upon approval from existing federation members, new collaborators can be integrated.

No, Saptharushi never has direct access to any form of participant data.

6. Federated Queries & Audience Matching

No, only hashed identifiers meeting specific query criteria are transferred for matching operations.

Matching occurs through federated queries, ensuring privacy-preserving computation across multiple datasets

Yes, predictive models can be hosted in the federated configuration or external systems, with audience matching seed data accessible via APIs.

Yes. The Private Query Server is designed to integrate Model Context Protocol that helps connect to Agentic Applications on the Federated Layer where predictive models can be built.

7. Operational Processes & Security Measures
  • All affected parties are immediately notified.
  • A mitigation plan is executed, including forensic analysis.
  • The party responsible may be held liable for legal and regulatory costs.
  • Blockchain-based provenance tracking ensures auditability.
  • Differential privacy prevents reidentification risks.
  • Multi-factor authentication & role-based access control safeguard data handling.
8. Platform Availability & Implementation

Yes, it is cloud-neutral, supporting AWS, GCP, and Azure. And On-Premise data sets as well.

Standard deployment is completed within one business day.

  • Cloud-specialized DevOps engineers for setup.
  • Data scientists for advanced analytics use cases.
9. Trust & Transparency Mechanisms

No, direct access to raw data is not permitted—ensuring compliance and trust.

Yes, a full provenance trail of access and query activity is available to all participants.

10. Investment & Business Use Cases

By enabling:

  • Privacy-compliant audience activation.
  • Secure data collaborations with federated access.
  • Monetization of insights via tokenized data exchange.

Saptharushi DCR supports:

  • Audience Identity Resolution
  • Profile Enrichment
  • Insights & Analytics
  • Audience Attribution & Measurement
  • Marketplace Integration