Are the Media & Subscription records on this page real?

No. Every record on this page is synthetic, generated from a fixed seed by the pack's own generator; masked values come from the real masking engine. The masking example uses a fixed public sample key; your own data is masked with a key from your secret store.

How long does a first certified Media & Subscription dataset take?

Estimates, not guarantees — try the synthetic sandbox: minutes; install (or reuse) the agent: under an hour; connect a source: under an hour; review and approve policies: under an hour; first certified dataset: minutes.

Which test scenarios does the Media & Subscription pack include?

11 runnable scenarios (everyday streaming, trial conversions, trial abuse, dunning failures and more), plus 1 negative-test scenario kept apart from valid data.

Do Media & Subscription rows leave my network?

No. The DataNivra agent runs inside your environment: it reads the source, masks, subsets, generates and certifies there, and sends only metadata, aggregate counts and evidence to the DataNivra control plane (customer-resident processing, zero raw-production-data egress).

Industry packs

Media & Subscription industry pack

Synthetic account, subscription, billing and viewing-history test data with linked masking

Preview only · not activatable yet Version 1.0.0 · Complete

Try with synthetic data Notify me — tell us you need it

Everything on this page works without an account. Prefer a conversation? Request a demo (optional). Missing something? Request a feature.

This pack is installed and passes DataNivra’s pack conformance kit through the real engine, but it cannot be activated yet: no plan includes it yet, the standard agent image does not ship it, the control-plane catalogue does not list it and the hosted sandbox has no synthetic estate for it. You can explore its synthetic records, masking and scenarios on this page and in the browser demo. Tell us if you need it: demand decides which packs become activatable next.

Problems this pack solves

Masked data that still joins across 5 systems

9 cross-system relationships link billing, content_delivery, crm, identity and subscriber_mgmt; the pack's masking keeps one pseudonym per identity on every side. For example, identity.accounts.account_id and subscriber_mgmt.households.account_ref get the same pseudonym.

The cases production samples rarely contain

9 ready-made scenarios generate them on demand, for example: free trials ending within a month: most convert to an active paid plan, some are cancelled; households starting trial after trial and cancelling each before the first charge; failed renewals: declined attempts, past-due subscriptions and escalating dunning stages.

Sensitive fields found and masked before anyone sees them

32 columns across 12 entities are classified (credential, direct identifier, financial, payment, PII, quasi identifier and sensitive) and covered by 3 masking templates you review and approve.

Evidence that each dataset is fit to use

2 certification presets check masking coverage, referential integrity, orphans and row counts before a dataset can be provisioned; a failed dataset is never provisioned.

Entities and relationships

12 entities across 5 source systems, generated from the pack’s own entity model.

Arrows point from the referencing entity to the one it references. Solid: a foreign key inside one system. Dashed: a cross-system relationship — the pack keeps the same pseudonym on both sides, so masked data still joins.

All 14 relationships as a table

Relationships of the Media & Subscription pack
Entity	References	Columns	Kind
Device	Account	`account_id` → `account_id`	Within a system
Profile	Household	`household_id` → `household_id`	Within a system
Subscription	Household	`household_id` → `household_id`	Within a system
Entitlement	Subscription	`subscription_id` → `subscription_id`	Within a system
PaymentAttempt	Invoice	`invoice_id` → `invoice_id`	Within a system
Household	Account	`account_ref` → `account_id`	Across systems (pack relationship template)
ViewingEvent	Account	`account_ref` → `account_id`	Across systems (pack relationship template)
ViewingEvent	Profile	`profile_ref` → `profile_id`	Across systems (pack relationship template)
ViewingEvent	Device	`device_ref` → `device_record_id`	Across systems (pack relationship template)
Invoice	Subscription	`subscription_ref` → `subscription_id`	Across systems (pack relationship template)
Invoice	Account	`account_ref` → `account_id`	Across systems (pack relationship template)
SupportContact	Account	`account_ref` → `account_id`	Across systems (pack relationship template)
ConsentPreference	Account	`account_ref` → `account_id`	Across systems (pack relationship template)
PromotionRedemption	Subscription	`subscription_ref` → `subscription_id`	Across systems (pack relationship template)

Realistic synthetic records

Synthetic data. Every record on this page is synthetic, generated from a fixed seed by the pack's own generator; masked values come from the real masking engine.

Entity

Account — `identity.accounts` (synthetic)
`account_id` sensitive	`login_email` sensitive	`mfa_phone` sensitive	`password_hash` sensitive	`country_code`	`signup_channel`	`status`	`created_at`
AC000000000001	veseth.wrenshaw1871@example.org	555-071-6618	<synthetic password_hash: 39 characters>	ZZ	MOBILE_APP	ACTIVE	2021-03-08T15:14:16
AC000000000002	alira.quarrridge9227@example.com	—	<synthetic password_hash: 39 characters>	ZZ	WEB	ACTIVE	2019-07-12T23:56:03

Masking: before and after

Template Linked media and subscription test data (MSB_LINKED_TEST_DATA) applied to a synthetic Account record from identity.accounts.

Synthetic record

Synthetic Account record before and after masking
Column	Classified as	Before (synthetic)	After masking
`account_id`	Direct identifier	`AC000000000001`	`AC304095231158`
`login_email`	PII, Direct identifier	`veseth.wrenshaw1871@example.org`	`luel.dunley8219@example.net`
`mfa_phone`	PII, Direct identifier	`555-071-6618`	`337-487-3778`
`password_hash`	Credential	`<synthetic password_hash: 39 characters>`	`—`

Same pseudonym in two systems. The identifier AC000000000001 appears in identity.accounts.account_id and in subscriber_mgmt.households.account_ref. Both become AC304095231158, so the masked systems still join (relationship MSB_HOUSEHOLD_ACCOUNT).

Masked with a fixed public sample key so this example is reproducible; your data is masked with your own key, referenced from your secret store.

Synthetic scenarios you can run

11 runnable scenarios. Preview them in your browser without an account; the hosted sandbox opens when the pack becomes activatable.

Everyday streaming

Normal MSB_EVERYDAY_STREAMING

Ordinary accounts, devices, households, profiles, plans, invoices and viewing sessions

Everyday, valid records: the baseline most tests expect. Children per parent record: 1–3.

Preview in the browser demo: Everyday streaming

Trial conversions

Rare MSB_TRIAL_CONVERSIONS

Free trials ending within a month: most convert to an active paid plan, some are cancelled

Valid but uncommon business situations that production samples often miss. Children per parent record: 1–2.

Preview in the browser demo: Trial conversions

Trial abuse

Rare MSB_TRIAL_ABUSE

Households starting trial after trial and cancelling each before the first charge

Valid but uncommon business situations that production samples often miss. Children per parent record: 3–6.

Preview in the browser demo: Trial abuse

Dunning failures

Rare MSB_DUNNING_FAILURES

Failed renewals: declined attempts, past-due subscriptions and escalating dunning stages

Valid but uncommon business situations that production samples often miss. Children per parent record: 1–3.

Preview in the browser demo: Dunning failures

Account sharing

Rare MSB_ACCOUNT_SHARING

Accounts streaming from many devices and many different network addresses

Valid but uncommon business situations that production samples often miss. Children per parent record: 4–8.

Preview in the browser demo: Account sharing

Binge sessions

Rare MSB_BINGE_SESSIONS

Very long playback sessions of one drama series within one weekend

Valid but uncommon business situations that production samples often miss. Children per parent record: 3–8.

Preview in the browser demo: Binge sessions

Consent withdrawn

Rare MSB_CONSENT_WITHDRAWN

Accounts that refused or withdrew consent for every purpose through the privacy centre

Valid but uncommon business situations that production samples often miss. Children per parent record: 2–5.

Preview in the browser demo: Consent withdrawn

Partner bundles

Rare MSB_PARTNER_BUNDLES

Entitlements and full discounts granted through bundling partners

Valid but uncommon business situations that production samples often miss. Children per parent record: 1–3.

Preview in the browser demo: Partner bundles

Retry limit

Boundary MSB_RETRY_LIMIT

Payment attempts exactly at the last retry before suspension, and one below it

Values at the edges of valid ranges (limits, thresholds, extremes). Children per parent record: 1–3.

Preview in the browser demo: Retry limit

Duplicate playback

Duplicate MSB_DUPLICATE_PLAYBACK

Playback events delivered twice by the client heartbeat with identical content under new ids

Records that repeat others under new keys (clean-up and matching tests). Children per parent record: 2–5.

Preview in the browser demo: Duplicate playback

Subscriber histories

Historical MSB_SUBSCRIBER_HISTORIES

Multi-year, referentially intact subscription, billing and viewing histories without gaps

Old records for archive, migration and retention tests. Children per parent record: 2–4.

Preview in the browser demo: Subscriber histories

Negative tests, kept apart. This scenario produces deliberately broken data for error handling and never passes certification as valid data:

MSB_BROKEN_REFERENCES — Dangling cross-system references and invalid values for error-handling tests

Sample schemas and representative outputs

The schema the pack expects in each system (also as CREATE TABLE DDL in the downloads). A run produces a masked or synthetic dataset with the same tables, a certification report with the gates of the chosen preset, and an evidence manifest with checksums — the rows stay in your environment.

Account — identity.accounts · 8 columns

A sign-in account (the natural subset root): one paying customer.

Column	Type	Required	Sensitive classes
`account_id` (key)	`VARCHAR(16)`	Yes	Direct identifier
`login_email`	`VARCHAR(128)`	Yes	PII, Direct identifier
`mfa_phone`	`VARCHAR(32)`	No	PII, Direct identifier
`password_hash`	`VARCHAR(64)`	No	Credential
`country_code`	`VARCHAR(2)`	Yes	—
`signup_channel`	`VARCHAR(12)`	Yes	—
`status`	`VARCHAR(10)`	Yes	—
`created_at`	`TIMESTAMP`	Yes	—

Device — identity.devices · 7 columns

A device registered to an account (TV, phone, browser, console, speaker).

Column	Type	Required	Sensitive classes
`device_record_id` (key)	`BIGINT`	Yes	—
`account_id`	`VARCHAR(16)`	Yes	Direct identifier
`device_identifier`	`VARCHAR(24)`	Yes	Direct identifier
`device_type`	`VARCHAR(10)`	Yes	—
`last_ip_address`	`VARCHAR(45)`	No	PII, Quasi identifier
`registered_at`	`TIMESTAMP`	Yes	—
`status`	`VARCHAR(14)`	Yes	—

Household — subscriber_mgmt.households · 5 columns

The household that shares an account's subscriptions.

Column	Type	Required	Sensitive classes
`household_id` (key)	`VARCHAR(12)`	Yes	Direct identifier
`account_ref`	`VARCHAR(16)`	Yes	Direct identifier
`postal_code`	`VARCHAR(10)`	No	PII, Quasi identifier
`household_size`	`INT`	No	—
`created_on`	`DATE`	Yes	—

Profile — subscriber_mgmt.profiles · 7 columns

A viewer profile inside a household (kids profiles carry a maturity limit).

Column	Type	Required	Sensitive classes
`profile_id` (key)	`BIGINT`	Yes	—
`household_id`	`VARCHAR(12)`	Yes	Direct identifier
`display_name`	`VARCHAR(48)`	Yes	PII, Direct identifier
`birth_year`	`INT`	No	Quasi identifier
`kids_profile`	`BOOLEAN`	Yes	—
`maturity_rating`	`VARCHAR(8)`	Yes	—
`language`	`VARCHAR(5)`	Yes	—

Subscription — subscriber_mgmt.subscriptions · 11 columns

A household's subscription to a plan, with trial, renewal and cancellation dates.

Column	Type	Required	Sensitive classes
`subscription_id` (key)	`VARCHAR(14)`	Yes	Direct identifier
`household_id`	`VARCHAR(12)`	Yes	Direct identifier
`plan_code`	`VARCHAR(12)`	Yes	—
`status`	`VARCHAR(10)`	Yes	—
`billing_cycle`	`VARCHAR(8)`	Yes	—
`max_streams`	`INT`	Yes	—
`started_on`	`DATE`	Yes	—
`trial_ends_on`	`DATE`	No	—
`renews_on`	`DATE`	No	—
`cancelled_on`	`DATE`	No	—
`cancel_reason`	`VARCHAR(20)`	No	—

Entitlement — subscriber_mgmt.entitlements · 6 columns

A right to content or a feature granted by a plan, add-on, promotion or partner bundle.

Column	Type	Required	Sensitive classes
`entitlement_id` (key)	`BIGINT`	Yes	—
`subscription_id`	`VARCHAR(14)`	Yes	Direct identifier
`entitlement_code`	`VARCHAR(20)`	Yes	—
`source`	`VARCHAR(16)`	Yes	—
`granted_on`	`DATE`	Yes	—
`expires_on`	`DATE`	No	—

Invoice — billing.invoices · 9 columns

A recurring invoice of a subscription.

Column	Type	Required	Sensitive classes
`invoice_id` (key)	`BIGINT`	Yes	—
`subscription_ref`	`VARCHAR(14)`	Yes	Direct identifier
`account_ref`	`VARCHAR(16)`	Yes	Direct identifier
`period_start`	`DATE`	Yes	—
`due_date`	`DATE`	Yes	—
`amount`	`DECIMAL(10,2)`	Yes	Financial
`tax_amount`	`DECIMAL(10,2)`	Yes	Financial
`currency`	`VARCHAR(3)`	Yes	—
`status`	`VARCHAR(12)`	Yes	—

PaymentAttempt — billing.payment_attempts · 9 columns

One collection attempt on an invoice; failed attempts move the account through dunning.

Column	Type	Required	Sensitive classes
`attempt_id` (key)	`BIGINT`	Yes	—
`invoice_id`	`BIGINT`	Yes	—
`attempt_number`	`INT`	Yes	—
`attempted_at`	`TIMESTAMP`	Yes	—
`outcome`	`VARCHAR(14)`	Yes	—
`dunning_stage`	`VARCHAR(14)`	Yes	—
`card_token`	`VARCHAR(24)`	No	Payment, Direct identifier
`card_last4`	`VARCHAR(4)`	No	Payment
`amount`	`DECIMAL(10,2)`	Yes	Financial

ViewingEvent — content_delivery.viewing_events · 11 columns

One playback session: who (account, profile, device) watched or listened to what, when.

Column	Type	Required	Sensitive classes
`event_id` (key)	`BIGINT`	Yes	—
`account_ref`	`VARCHAR(16)`	Yes	Direct identifier
`profile_ref`	`BIGINT`	Yes	—
`device_ref`	`BIGINT`	Yes	—
`title_id`	`VARCHAR(12)`	Yes	Sensitive
`genre`	`VARCHAR(12)`	Yes	—
`started_at`	`TIMESTAMP`	Yes	Quasi identifier
`watch_seconds`	`INT`	Yes	—
`completion_pct`	`INT`	Yes	—
`client_ip_address`	`VARCHAR(45)`	No	PII, Quasi identifier
`stream_quality`	`VARCHAR(6)`	Yes	—

SupportContact — crm.support_contacts · 8 columns

A customer-support contact (chat, phone or e-mail).

Column	Type	Required	Sensitive classes
`contact_id` (key)	`BIGINT`	Yes	—
`account_ref`	`VARCHAR(16)`	Yes	Direct identifier
`contact_email`	`VARCHAR(128)`	No	PII, Direct identifier
`channel`	`VARCHAR(6)`	Yes	—
`reason`	`VARCHAR(16)`	Yes	—
`opened_at`	`TIMESTAMP`	Yes	—
`status`	`VARCHAR(10)`	Yes	—
`transcript_excerpt`	`VARCHAR(300)`	No	Sensitive

ConsentPreference — crm.consent_preferences · 7 columns

The latest recorded choice of an account for one processing purpose.

Column	Type	Required	Sensitive classes
`consent_id` (key)	`BIGINT`	Yes	—
`account_ref`	`VARCHAR(16)`	Yes	Direct identifier
`purpose`	`VARCHAR(28)`	Yes	—
`granted`	`BOOLEAN`	Yes	—
`captured_at`	`TIMESTAMP`	Yes	—
`capture_channel`	`VARCHAR(14)`	Yes	—
`policy_version`	`VARCHAR(8)`	Yes	—

PromotionRedemption — crm.promotion_redemptions · 7 columns

A promotion or partner-bundle offer applied to a subscription.

Column	Type	Required	Sensitive classes
`redemption_id` (key)	`BIGINT`	Yes	—
`subscription_ref`	`VARCHAR(14)`	Yes	Direct identifier
`promo_code`	`VARCHAR(16)`	Yes	—
`partner_code`	`VARCHAR(14)`	No	—
`discount_pct`	`INT`	Yes	—
`redeemed_at`	`TIMESTAMP`	Yes	—
`status`	`VARCHAR(8)`	Yes	—

Compatible connectors

Verified with this pack version: PostgreSQL and Local files (Parquet / CSV). 17 more connectors are compatible by capability: they support what the pack needs, but have not been verified with this pack yet.

Connector	Status with Media & Subscription
Local files (Parquet / CSV)	Verified with this pack
PostgreSQL	Verified with this pack
Amazon S3 / S3-compatible storage	Compatible by capability (not yet verified with this pack)
Apache Kafka (connector in preview)	Compatible by capability (not yet verified with this pack)
Azure Blob Storage / Data Lake Storage	Compatible by capability (not yet verified with this pack)
Databricks	Compatible by capability (not yet verified with this pack)
Generic SQL (SQLAlchemy)	Compatible by capability (not yet verified with this pack)
Google BigQuery	Compatible by capability (not yet verified with this pack)
HTTP APIs (connector in preview)	Compatible by capability (not yet verified with this pack)
IBM Db2 (connector in preview)	Compatible by capability (not yet verified with this pack)
Mainframe files (EBCDIC / copybook) (connector in preview)	Compatible by capability (not yet verified with this pack)
MariaDB	Compatible by capability (not yet verified with this pack)
Microsoft SQL Server	Compatible by capability (not yet verified with this pack)
MongoDB (connector in preview)	Compatible by capability (not yet verified with this pack)
MySQL	Compatible by capability (not yet verified with this pack)
Oracle Database	Compatible by capability (not yet verified with this pack)
Parquet files	Compatible by capability (not yet verified with this pack)
Snowflake	Compatible by capability (not yet verified with this pack)
SQLite (developer evaluation) (connector in preview)	Compatible by capability (not yet verified with this pack)

Prerequisites and expected setup effort

You need

This pack is not in any plan yet.
One DataNivra agent inside your network (outbound HTTPS only) that ships Media & Subscription 1.0.0.
Read-only access to a compatible source (verified with this pack: PostgreSQL, Local files (Parquet / CSV)).
A non-production target environment the agent may write test data to.
A masking key in your own secret store, referenced as vault://…, azure-kv://… or env://… (DataNivra only ever sees the reference).
For production sources, a second person who approves policies (separation of duties).

A DataNivra agent that reports its installed industry packs (releases after agent 0.3.0); the control plane runs a pack job only on an agent holding the exact active pack version with the catalogued integrity digest.

Expected setup effort (estimates)

Step	Estimate
Try the synthetic sandbox No install: sign up and open the sandbox.	Minutes (estimate)
Install (or reuse) the agent One Docker command or a Helm chart; outbound HTTPS only.	Under an hour (estimate)
Connect a source Register a read-only source through the existing connector workflow.	Under an hour (estimate)
Review and approve policies Create drafts from the Media & Subscription templates, review and approve them.	Under an hour (estimate)
First certified dataset Run the first job; certification and evidence are produced automatically.	Minutes (estimate)

Certification presets in plain language

`MSB_STRICT`

Every gate; full masking coverage; zero orphaned devices, households, profiles, subscriptions, entitlements, invoices, payment attempts, playback sessions, contacts, consent records or redemptions; exact row counts. Default for masked subscription test data.

Masking coverage of at least 100% of sensitive columns
No orphaned child records
Empty-value ratio may rise by at most 5%
Row counts must match exactly

16 gates it requires

POLICY_COVERAGE: every sensitive column is covered by an approved policy
MASKING_COMPLETION: masking finished on every covered column
REFERENTIAL_INTEGRITY: every reference still points at an existing record
SCHEMA_VALIDATION: the output schema matches the source schema
DATA_QUALITY: empty-value ratios stay within the preset’s drift limit
ROW_COUNT_RECONCILIATION: row counts match the plan within the tolerance
ORPHAN_DETECTION: no child record lost its parent
PROVENANCE: every row is tagged masked or synthetic
MANIFEST: a manifest lists every output table with checksums
POLICY_VERSION: the exact approved policy versions are recorded
ENGINE_VERSION: the engine version is recorded
CHECKSUMS: output checksums are recorded for later verification
IDENTITY_CONSISTENCY: linked identifiers got the same pseudonym in every system
SOURCE_READ_ONLY: the source was only read, never written
EGRESS_GUARD: no row-level data left the agent
CONNECTOR_HEALTH: the connectors stayed healthy during the run

`MSB_SCENARIO_TESTING`

Every gate, with slightly relaxed NULL-ratio drift for scenario datasets whose business states (trials without renewal dates, cancelled subscriptions, partner-free promotions) leave optional fields empty.

Masking coverage of at least 100% of sensitive columns
No orphaned child records
Empty-value ratio may rise by at most 15%
Row counts must match exactly

16 gates it requires

POLICY_COVERAGE: every sensitive column is covered by an approved policy
MASKING_COMPLETION: masking finished on every covered column
REFERENTIAL_INTEGRITY: every reference still points at an existing record
SCHEMA_VALIDATION: the output schema matches the source schema
DATA_QUALITY: empty-value ratios stay within the preset’s drift limit
ROW_COUNT_RECONCILIATION: row counts match the plan within the tolerance
ORPHAN_DETECTION: no child record lost its parent
PROVENANCE: every row is tagged masked or synthetic
MANIFEST: a manifest lists every output table with checksums
POLICY_VERSION: the exact approved policy versions are recorded
ENGINE_VERSION: the engine version is recorded
CHECKSUMS: output checksums are recorded for later verification
IDENTITY_CONSISTENCY: linked identifiers got the same pseudonym in every system
SOURCE_READ_ONLY: the source was only read, never written
EGRESS_GUARD: no row-level data left the agent
CONNECTOR_HEALTH: the connectors stayed healthy during the run

Activation status

What is missing before you can activate the Media & Subscription pack yourself:

no plan includes it yet
the standard agent image does not ship it
the control-plane catalogue does not list it
the hosted sandbox has no synthetic estate for it

Until then, preview it in the browser demo and download its synthetic asset bundle below.

Tell us you need the Media & Subscription pack or request a feature for it.

Downloads

Version 1.0.0, 68 files (218.9 KB), all synthetic and generated from the pack itself. Every file’s SHA-256 is listed in MANIFEST.json.

Start here (2)

QUICKSTART.md 3.0 KB · SHA-256 dc8a6695f5a9…
TROUBLESHOOTING.md 4.7 KB · SHA-256 c0c267cf0b19…

Entity–relationship diagram (2)

er-diagram.mmd 4.6 KB · SHA-256 1696ad7cdf86…
er-diagram.svg 8.8 KB · SHA-256 8f60a43c5178…

Sample schemas (6)

schema/billing.sql 1.5 KB · SHA-256 f25e383ee42f…
schema/content_delivery.sql 997 B · SHA-256 918e878ade5a…
schema/crm.sql 1.7 KB · SHA-256 f8c9bb3a6712…
schema/entities.json 30.6 KB · SHA-256 2d20f53ec90a…
schema/identity.sql 1.4 KB · SHA-256 5515fb8a540c…
schema/subscriber_mgmt.sql 2.4 KB · SHA-256 9386846caa70…

Policy templates (9)

policies/MSB_ANALYTICS_UNLINKED.json 13.3 KB · SHA-256 5401643efeab…
policies/MSB_BEHAVIOUR_MINIMISED.json 14.4 KB · SHA-256 43607437ca9b…
policies/MSB_CLASSIFICATION.json 203 B · SHA-256 08c8e5005e8d…
policies/MSB_LINKED_TEST_DATA.json 14.6 KB · SHA-256 f42f00de8ae8…
policies/MSB_REFRESH_WEEKLY.json 190 B · SHA-256 e54930bed540…
policies/MSB_SCENARIO_TESTING.json 549 B · SHA-256 a0728ad1a443…
policies/MSB_STRICT.json 549 B · SHA-256 df479db4f4bb…
policies/MSB_SUBSET_DEFAULT.json 112 B · SHA-256 d46c49c10d7c…
policies/README.md 1.3 KB · SHA-256 b508795ea54b…

API, CLI, SDK and CI/CD examples (10)

api/curl.sh 2.6 KB · SHA-256 232abd01c75d…
api/dataset-request.json 1.5 KB · SHA-256 a6b9aceebd4a…
api/policy-approval.json 155 B · SHA-256 d55e632a5036…
api/policy-drafts.json 162 B · SHA-256 1e25229c4597…
api/provision.json 63 B · SHA-256 7f02a6a87792…
api/sandbox.json 46 B · SHA-256 2af3958d129e…
ci/README.md 501 B · SHA-256 cf4d014c1938…
ci/github-actions.yml 1.9 KB · SHA-256 057807cfeb16…
cli.md 1.8 KB · SHA-256 1d7b70accedb…
sdk_example.py 1.6 KB · SHA-256 72a77b6fdfe8…

Synthetic sample data (CSV, JSON, Parquet) (37)

synthetic/SYNTHETIC_MANIFEST.json 2.8 KB · SHA-256 eaf2b17f5c1e…
synthetic/billing.invoices.csv 1.6 KB · SHA-256 ba0ab0277447…
synthetic/billing.invoices.json 5.3 KB · SHA-256 4a6a1509df22…
synthetic/billing.invoices.parquet 3.1 KB · SHA-256 e8c834cfdad1…
synthetic/billing.payment_attempts.csv 2.0 KB · SHA-256 9963af94c8c2…
synthetic/billing.payment_attempts.json 6.8 KB · SHA-256 df634dbf956d…
synthetic/billing.payment_attempts.parquet 3.7 KB · SHA-256 e364fd2388f5…
synthetic/content_delivery.viewing_events.csv 3.7 KB · SHA-256 4cd233ab3fe6…
synthetic/content_delivery.viewing_events.json 13.7 KB · SHA-256 14c08a704123…
synthetic/content_delivery.viewing_events.parquet 5.0 KB · SHA-256 50af5faeda23…
synthetic/crm.consent_preferences.csv 2.4 KB · SHA-256 9737fd6b3ea2…
synthetic/crm.consent_preferences.json 6.7 KB · SHA-256 c2f8c495eef3…
synthetic/crm.consent_preferences.parquet 2.9 KB · SHA-256 fd379662b65d…
synthetic/crm.promotion_redemptions.csv 399 B · SHA-256 45a7aecce8f3…
synthetic/crm.promotion_redemptions.json 1.0 KB · SHA-256 312a8fe9ce39…
synthetic/crm.promotion_redemptions.parquet 2.5 KB · SHA-256 9f6908aed9ab…
synthetic/crm.support_contacts.csv 953 B · SHA-256 bd05f1be28fb…
synthetic/crm.support_contacts.json 1.8 KB · SHA-256 fb1f38a55235…
synthetic/crm.support_contacts.parquet 3.5 KB · SHA-256 d22daa151573…
synthetic/identity.accounts.csv 737 B · SHA-256 1933e065557b…
synthetic/identity.accounts.json 1.6 KB · SHA-256 b3d05c790091…
synthetic/identity.accounts.parquet 3.0 KB · SHA-256 e2af9470fb77…
synthetic/identity.devices.csv 1.2 KB · SHA-256 e896fc6eeee3…
synthetic/identity.devices.json 3.4 KB · SHA-256 b602203c60c9…
synthetic/identity.devices.parquet 2.9 KB · SHA-256 ec46ce79fbca…
synthetic/subscriber_mgmt.entitlements.csv 873 B · SHA-256 6e842f6d96a2…
synthetic/subscriber_mgmt.entitlements.json 2.9 KB · SHA-256 6515bab332eb…
synthetic/subscriber_mgmt.entitlements.parquet 2.3 KB · SHA-256 f8a803bd4015…
synthetic/subscriber_mgmt.households.csv 358 B · SHA-256 420415a3b271…
synthetic/subscriber_mgmt.households.json 1003 B · SHA-256 95f4d83a11eb…
synthetic/subscriber_mgmt.households.parquet 1.9 KB · SHA-256 1683e17549a6…
synthetic/subscriber_mgmt.profiles.csv 714 B · SHA-256 277c2609ef67…
synthetic/subscriber_mgmt.profiles.json 2.8 KB · SHA-256 56fa02002fdc…
synthetic/subscriber_mgmt.profiles.parquet 2.5 KB · SHA-256 6dc5f7d303b7…
synthetic/subscriber_mgmt.subscriptions.csv 589 B · SHA-256 834abac3ff14…
synthetic/subscriber_mgmt.subscriptions.json 1.8 KB · SHA-256 4fb6348207cc…
synthetic/subscriber_mgmt.subscriptions.parquet 3.3 KB · SHA-256 56d8fa6a23c9…

Troubleshooting

The reason codes you can meet on the way, with the recovery step. Every code is also in the error-code catalog.

SANDBOX_PACK_NOT_OFFERED — Synthetic estate not offered: A requested synthetic estate (industry pack) is not available in the hosted sandbox. What to do: Start the sandbox with the default estates.
ENTITLEMENT_REQUIRED — Plan does not include this: Your plan does not include this feature or industry pack. What to do: Upgrade in Billing & Plan.
PACK_INTEGRITY_UNVERIFIED — Pack integrity not verified: This pack version was registered without an integrity digest, so it cannot be activated (fail closed). What to do: Ask your operator to re-register the pack catalogue with the current control-plane image (register-pack), then activate again.
PACK_DEPENDENCY_INACTIVE — Required pack not active: This pack depends on another industry pack that is not active for your organization. What to do: Activate the packs this pack depends on first, then activate it again.
AGENT_PACK_MISSING — No agent can run this industry pack: The job's agent does not report the pack (older agents report no packs at all), so the job was not sent. What to do: Upgrade the agent to a release that reports its installed packs and ships this pack, then run the request again.
AGENT_PACK_VERSION_INCOMPATIBLE — Industry pack version differs on the agent: The agent holds a different version of the pack than the one the job was approved for. What to do: Deploy an agent with the pack's active version, or roll the pack back in Industry packs.
AGENT_PACK_INTEGRITY_MISMATCH — Agent pack differs from the catalogue: The agent reports the pack's version with a different integrity digest than the catalogued one, so the job was not sent. What to do: Redeploy the agent from the official signed image for this release, then run the request again.
PACK_TEMPLATES_UNAVAILABLE — Pack templates not registered: This pack version was registered without its policy templates. What to do: Ask your operator to re-register the pack catalogue (register-pack); create policies manually meanwhile.
PACK_TEMPLATE_KEY_REF_REQUIRED — Masking key reference required: A selected template keeps identities linked across systems and needs your masking key reference. What to do: Provide key_ref, e.g. vault://your-vault/tdm-masking-key, then create the drafts again.
PACK_NOT_ENABLED — Industry pack not enabled: The industry pack is not enabled for this tenant. What to do: Enable the pack (if your plan includes it).

Frequently asked questions

Are the Media & Subscription records on this page real?: No. Every record on this page is synthetic, generated from a fixed seed by the pack's own generator; masked values come from the real masking engine. The masking example uses a fixed public sample key; your own data is masked with a key from your secret store.
Can I activate the Media & Subscription pack myself?: This pack is installed and passes DataNivra’s pack conformance kit through the real engine, but it cannot be activated yet: no plan includes it yet, the standard agent image does not ship it, the control-plane catalogue does not list it and the hosted sandbox has no synthetic estate for it. You can explore its synthetic records, masking and scenarios on this page and in the browser demo. Tell us if you need it: demand decides which packs become activatable next.
Which databases and files does the Media & Subscription pack work with?: Verified with this pack version: PostgreSQL and Local files (Parquet / CSV). 17 more connectors are compatible by capability: they support what the pack needs, but have not been verified with this pack yet.
How long does a first certified Media & Subscription dataset take?: Estimates, not guarantees — try the synthetic sandbox: minutes; install (or reuse) the agent: under an hour; connect a source: under an hour; review and approve policies: under an hour; first certified dataset: minutes.
Which test scenarios does the Media & Subscription pack include?: 11 runnable scenarios (everyday streaming, trial conversions, trial abuse, dunning failures and more), plus 1 negative-test scenario kept apart from valid data.
Do Media & Subscription rows leave my network?: No. The DataNivra agent runs inside your environment: it reads the source, masks, subsets, generates and certifies there, and sends only metadata, aggregate counts and evidence to the DataNivra control plane (customer-resident processing, zero raw-production-data egress).

Learn the concepts, then come back to activate

Regulatory context

The Media & Subscription pack covers data that laws and industry rules often treat as sensitive. It supports your privacy and governance programmes by keeping those records inside your environment and producing certification evidence; it does not, by itself, make any system or organisation compliant with any law, regulation or standard.

Try with synthetic data Notify me — tell us you need it

Everything on this page works without an account. Prefer a conversation? Request a demo (optional). Missing something? Request a feature.