Sovereign Intellectual Property Authority
Privacy Policy & Data Usage Disclosures
This comprehensive Privacy Policy transparently explains how Sovranly IP collects, utilizes, safeguards, retains, and disseminates user information across our decentralized intellectual property management suite, smart contract infrastructure, and web applications.
EFFECTIVE: January 15, 2026LAST MODIFIED: September 4, 2026 GDPR & CCPA/CPRA COMPLIANT
Table of Contents & Quick Navigation
Executive Summary & Privacy Pillars 1. Google API Services User Data Policy & Limited Use 2. Information We Collect (Detailed Taxonomy & Vectors) 3. CCPA/CPRA Statutory Notice at Collection & Disclosures 4. How We Use and Process Your Data (Comprehensive Purpose Matrix) 5. Artificial Intelligence (AI) & Machine Learning Usage 6. Legal Bases for Processing & Non-Profiling (GDPR Arts. 6, 9 & 22) 7. Third-Party Subprocessors & Service Providers 8. Blockchain Immutability & Public Ledger Disclosures 9. Information Sharing & Zero Data Monetization 10. Data Storage Topology & Technical Security Measures (TOMs - Art. 32) 11. Data Retention, Archival & Deletion Schedules 12. Data Deletion, Export & Google Access Revocation Guide 13. Your Statutory Rights & Recourse (GDPR Arts. 15-22 & CCPA/CPRA) 14. Zero Trust Cryptographic Security & Breach Protocols (GDPR Arts. 33-34) 15. International Transfers & Cross-Border Safeguards (SCCs & DPF) 16. Children’s Online Privacy Protections (COPPA & GDPR Art. 8) 17. Storage & Cookie Governance Matrix 18. Data & Privacy Frequently Asked Questions (FAQ) 19. Contact Information & Data Protection Officer
[00] Executive Summary & Core Privacy Pillars
At Sovranly IP, our architectural foundation is built on Zero Trust and Cryptographic Data Minimization. Unlike legacy media distributor platforms that harvest and commercialize personal user data, Sovranly IP is engineered so that creators maintain sovereign ownership and continuous control over their intellectual assets.
No Data Monetization
We do not sell, license, rent, or trade your personal data, catalog items, or contact lists to data brokers or AI scraping crawlers.
Non-Custodial Security
We never prompt for or store private keys or wallet seed phrases. You hold sole cryptographic possession of your Web3 signing credentials.
Auditable Transparency
Every consent vector, cookie signature, and on-chain royalty execution is recorded with verifiable, auditable timestamps.
[01] Google API Services User Data Policy & Limited Use Disclosure
Mandatory disclosure regarding access, handling, storage, and transfer of Google user data.
GOOGLE OAUTH COMPLIANCE
Sovranly IP integrates with Google Identity Services and Google OAuth 2.0 (via Firebase Authentication and Google Cloud Platform) to offer secure, passwordless authentication and continuous creator identity verification. We maintain strict compliance with Google's developer ecosystem policies.
Google API Limited Use Requirements Compliance Statement
Sovranly IP's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Specific Google User Data Accessed, Collected & Processed
When you choose to sign in to Sovranly IP with your Google Account, we request only the minimal necessary OAuth scopes (openid, profile, and email). Specifically, we access and process:
- Google Account Primary Email Address: Used to uniquely identify your creator account, verify rights ownership, prevent duplicate accounts, and send vital transactional notifications (royalty payouts, smart contract deployments, and licensing disputes).
- Basic Profile Information: Display name, given name, family name, and profile picture avatar URL. Used to personalize your creator profile interface and attribute intellectual property registrations.
- Google User Unique Identifier (sub / UID): An immutable unique string generated by Google that securely ties your session tokens and database records to your verified identity across logins.
- OAuth Access & Refresh Tokens: Short-lived cryptographic tokens issued during sign-in, used exclusively to validate active sessions under our Zero Trust security model.
Purposes of Google User Data Processing
1. Authentication & Session Verification
Authenticating your identity securely without requiring or storing passwords on our servers, preventing credential stuffing attacks.
2. Intellectual Property Rights Attribution
Associating your verified creator identity with registered track catalogs, digital split sheets, and autonomous licensing contracts.
3. Transactional & Royalty Alerts
Dispatching automated electronic notices regarding completed royalty payouts, license purchase agreements, or counter-claims.
4. Zero Trust Security & Anti-Abuse Defense
Detecting bot networks, preventing sybil account generation, and defending our decentralized licensing registry from unauthorized tampering.
Strict Safeguards & Prohibitions on Google User Data
NO AI/ML Model Training
We do NOT use Google user data to train, retrain, fine-tune, or improve generalized artificial intelligence (AI), machine learning (ML), or large language models (LLMs).
NO Sale, Lease or Data Brokering
We do NOT sell, rent, lease, or transfer Google user data to third-party data brokers, marketing intermediaries, or ad platforms under any circumstances.
NO Targeted Advertising
Google user data is NEVER used to serve targeted advertisements, retargeting pixels, or behavioral marketing promotions.
Strict Human Access Restrictions
Humans (including Sovranly IP staff) do NOT read your Google data unless you give explicit affirmative consent for technical troubleshooting, for security investigations (e.g., malware or fraud), or to comply with applicable statutory law.
Storage, Retention & How to Revoke Google Access
Google user data is encrypted in transit using TLS 1.3 and at rest using AES-256 within Google Cloud Firestore. It is retained solely for the duration of your active Sovranly IP account tenure and is purged within 30 calendar days upon account deletion.
Revoke Sovranly IP's Google Account Access at Any Time: You can instantly disconnect Sovranly IP from your Google Account via Google's centralized permissions portal.
[02] Information We Collect (Detailed Taxonomy & Vectors)
Comprehensive classification of all active, passive, on-chain, integrated, and telemetry data collection vectors.
DATA COLLECTION VECTORS
At Sovranly IP, our data architecture enforces strict Cryptographic Data Minimization and Zero Trust Authorization. We never harvest extraneous user data, engage in cross-context tracking, or monetize personal information. Depending on how you interact with Sovranly IP (browsing creative registries, authenticating an account, linking an on-chain Web3 wallet, uploading audio masters, notarizing intellectual property, or executing automated license agreements), we collect and process data through seven distinct, transparent collection vectors:
Vector 1: Direct Creator Submissions & Profile Data
DIRECT ACTIVE
Information provided directly by you when creating or customizing your creator profile on the Sovranly IP platform:
- Creator Moniker & Profile Bio: Public stage name, pseudonymous artist moniker, legal creator alias, professional biography, and designated creative genres.
- Social Verification Links: Optional external creator profile links (e.g., Spotify Artist URI, Apple Music ID, X/Twitter handle, Soundcloud profile, GitHub profile) used for provenance verification and anti-impersonation badge issuance.
- Contact & Notification Preferences: Direct contact email address, SMS notification preferences (where opted in for instant royalty disbursement alerts), and membership tier designations (Founders Beta, Rights Holder, Enterprise Catalog Manager).
- Age & Majority Attestation: Mandatory self-attestation confirming you are at least 18 years of age (or legal age of majority in your jurisdiction) in strict compliance with COPPA and global legal capacity requirements.
Vector 2: Google Identity & OAuth 2.0 Integration Vectors
OAUTH 2.0 FEDERATED
When you sign in to Sovranly IP using Google Identity Services (via Firebase Authentication), we receive and process standard OpenID Connect federated claims:
- Google Primary Verified Email Address: Used as your unique sovereign creator identifier, preventing account hijacking and ensuring secure transactional notifications.
- Basic Profile Metadata: Full display name, given name, family name, and profile avatar URL used to render your creator dashboard interface.
- Google Unique Subject Identifier (UID / sub): Immutable federated identifier mapped cryptographically to your internal Firestore account ledger.
- Short-Lived Session Tokens: Cryptographically signed JWT access and refresh tokens used exclusively to validate active sessions under our Zero Trust security model.
- Limited Use Commitment: All data received through Google APIs strictly complies with the Google API Services User Data Policy, including the Limited Use requirements. We never use Google user data to train AI/ML models or transfer it to data brokers.
Vector 3: Intellectual Property Catalog, Master Audio & Creative Assets
MEDIA & RIGHTS INGESTION
Data ingested when you register, notarize, split, or license intellectual property assets through our smart contract infrastructure:
- Master Audio Recordings & Stems: High-resolution lossless audio masters (WAV 24-bit/48kHz/96kHz, FLAC, AIFF), MP3 reference previews, and individual multitrack stems (drums, bass, vocals, synths, instruments).
- Visual Artwork & Documentation: High-resolution album/single cover art (PNG, JPG, SVG, WebP), music video clips, track liner notes, and legal contract attachments (PDF, DOCX).
- Standardized Statutory Rights Identifiers: International Standard Recording Codes (ISRC), International Standard Musical Work Codes (ISWC), Universal Product Codes (UPC), and Performing Rights Organization (PRO) affiliation records (ASCAP, BMI, SESAC, PRS, SACEM, GEMA).
- Split Sheet & Publishing Terms: Co-creator legal names, pseudonym aliases, contributor email addresses, publisher designations, and mechanical/performance royalty distribution split percentages (e.g., 50% Producer / 50% Vocalist).
- Commercial Licensing Rules: Pricing terms, territory restrictions, synchronization usage parameters, broadcast streaming limits, non-exclusive / exclusive license tiers, and automated revocation conditions.
Vector 4: Web3 Blockchain & Cryptographic Signature Vectors
NON-CUSTODIAL WEB3
Data generated during interaction with decentralized EVM networks (Ethereum, Arbitrum, Base, Optimism, Polygon):
- Public EVM Wallet Addresses: Hexadecimal public wallet addresses (e.g.,
0x71C...a49B) read from client-side Web3 providers (MetaMask, Coinbase Wallet, WalletConnect). Sovranly IP operates strictly non-custodially and never receives, requests, or stores private keys or seed phrases. - Cryptographic Media Fingerprints (SHA-256 / keccak256): Deterministic cryptographic checksums computed directly in your browser prior to cloud upload, anchoring proof of prior art on-chain.
- InterPlanetary File System (IPFS) CIDs: Decentralized content identifiers generated when pinning encrypted metadata manifests and preview assets.
- EIP-712 & EIP-191 Cryptographic Signatures: Off-chain typed structured data signatures signed by your Web3 wallet to authorize gasless permit approvals, license releases, and split modifications.
- On-Chain Transaction & Event Logs: Smart contract deployment hashes, block numbers, gas fees, and automated royalty disbursement event emissions.
Vector 5: Financial, Payment & Statutory Accounting Vectors
PCI-DSS TOKENIZED
Information processed when purchasing platform subscriptions, minting licenses, or receiving automated royalty payouts:
- Tokenized Payment Gateways: All credit/debit card numbers are tokenized directly through certified PCI-DSS Level 1 payment processors. Sovranly IP stores only masked customer IDs, payment intent IDs, card brand, last four digits, billing postal codes, and invoice receipts. Sovranly IP never sees, processes, or stores complete card numbers or CVV/CVC codes.
- Cryptocurrency Payment Transactions: Stablecoin (USDC, USDT) and native cryptocurrency (ETH) transfer hashes, sender/recipient addresses, and token settlement values.
- Tax & Statutory Accounting Disclosures: VAT/sales tax identification numbers (for EU/UK creators), business registration numbers, and 1099/W-8BEN tax filing records required under IRC § 6050W.
Vector 6: Automated Telemetry, Network Headers & Security Diagnostics
PASSIVE LOGGING
Technical telemetry automatically recorded by cloud infrastructure to maintain uptime, triage cyber threats, and optimize performance:
- Server & Gateway Logs: Truncated/masked IP addresses (preserving anonymity while preventing DDoS and brute-force attacks), browser user-agent strings, operating system, HTTP method, response codes, referrer URLs, and ISO-8601 timestamps.
- Google Analytics 4 Telemetry: Anonymized interaction events (page view sequences, button click interactions, session durations) collected via measurement ID
G-ZGGTSS0QFNwith IP anonymization enforced. - Zero Trust Web3 Diagnostics: RPC node round-trip latency, gas estimation benchmarks, and Web3 connection reliability metrics used to ensure real-time transaction finality.
Vector 7: Direct Inquiries, Support Tickets & DMCA Copyright Claims
INBOUND INQUIRIES
Data collected during direct creator communications and legal rights administration:
- Technical Support Communications: Inbound support emails, bug reports, feature requests, and feedback messages submitted to
create@sovranlyip.comor in-app support modules. - DMCA Copyright Infringement Notices: Formal statutory copyright infringement claims, counter-notices, rights holder legal names, contact information, and sworn affidavits submitted pursuant to 17 U.S.C. § 512.
- Data Subject Access Requests (SARs): Formal identity verification tokens, request types (Access, Rectification, Erasure, Portability), and correspondence records retained to fulfill statutory compliance obligations.
Data Collection Vectors — Technical Ingestion & Storage Specification Matrix
| Vector Channel | Ingestion Mechanism | Data Payload Elements | Transport Security | Storage Destination | Default Retention |
|---|---|---|---|---|---|
| V1: Creator Profile | Direct User Form Input | Moniker, bio, genres, social links, role designations | TLS 1.3 / HTTPS | Firestore (US-WEST1) | Duration of Account Tenure |
| V2: Google OAuth 2.0 | Federated OIDC Flow | Primary email, name, avatar URL, Google UID (sub), JWT tokens | TLS 1.3 / mTLS | Firebase Auth / Firestore | Duration of Account Tenure |
| V3: Media Masters & Splits | Direct Chunked Upload / Split Engine | Audio masters (WAV/FLAC), stems, artwork, ISRC, ISWC, split %s | TLS 1.3 / AES-256 CMEK | Cloud Storage Buckets & IPFS | Until Asset De-Registration |
| V4: Web3 Wallet Signatures | EIP-1193 / EIP-712 Signatures | Public EVM address, keccak256 checksums, EIP-712 permits | Client-Side Web3 RPC | EVM Blockchains & Firestore | On-Chain Immutable / Off-Chain 30d |
| V5: Payment & Invoices | PCI-DSS Tokenized Gateway | Customer token ID, payment intent ID, last 4 digits, tax VAT IDs | TLS 1.3 / PCI Tokenization | Payment Processor / Encrypted DB | 7 Years (Statutory Fiscal Laws) |
| V6: Server Telemetry & GA4 | Cloud Logging & GA4 Stream | Truncated IP, User-Agent, referrer URL, error stacks, page views | TLS 1.3 | Google Cloud Logging / GA4 | 90 Days to 14 Months |
| V7: Support & DMCA | Direct Email & In-App Forms | Email, ticket text, attachments, copyright ownership declarations | TLS 1.3 / S/MIME | Encrypted Support Repository | 3 Years (Statute of Limitations) |
[03] California Consumer Privacy Act (CCPA/CPRA) Notice at Collection & Statutory Disclosures
Formal disclosures pursuant to Cal. Civ. Code §§ 1798.100, 1798.110, 1798.115, 1798.121 & 11 CCR §§ 7010-7031.
CALIFORNIA RESIDENTS DISCLOSURE
This section provides additional disclosures required under the California Consumer Privacy Act of 2018, as amended by the California Privacy Rights Act of 2020 (collectively, 'CCPA/CPRA'). The disclosures below describe our practices regarding the collection, use, disclosure, and sale/sharing of Personal Information in the preceding 12 months.
| CCPA Statutory Category (§ 1798.140(v)(1)) | Collected (Past 12 Mos) | Categories of Sources | Business / Commercial Purpose | Categories of Third Parties Disclosed To | Sold or Shared (§ 1798.140(ad)/(ah)) |
|---|---|---|---|---|---|
| A. IdentifiersName, email, unique UID, IP address, EVM wallet address. | YES | Direct from consumer, Google OAuth, Web3 browser wallets. | User authentication, creator catalog attribution, security defense, transaction notices. | Cloud infrastructure (Google Cloud/Firebase), authorized payment processor. | NONE SOLD / NONE SHARED |
| B. Customer Records (Cal. Civ. Code § 1798.80(e))Name, signature, masked payment tokens (last 4 digits). | YES | Direct from consumer, payment processor. | Executing licensing contracts, subscription billing, payout accounting. | Authorized payment processor, banking gateways. | NONE SOLD / NONE SHARED |
| C. Protected ClassificationsAge (18+ verified threshold only; no race/gender). | YES (Age 18+ only) | Direct consumer attestation upon registration. | COPPA and platform terms enforcement; age-verification. | None. | NONE SOLD / NONE SHARED |
| D. Commercial InformationRegistered works, licensing terms, royalty receipts. | YES | Direct from consumer, EVM blockchain transactions. | Publishing rights registries, smart contract splits, commercial licensing. | Public decentralized EVM blockchains, IPFS nodes. | NONE SOLD / NONE SHARED |
| E. Biometric InformationVoiceprints, facial geometry, retina scans. | NO | N/A (None collected). | N/A | None. | NONE SOLD / NONE SHARED |
| F. Internet & Network ActivityBrowsing history on app, clicks, telemetry, RPC latency. | YES | Automated server logs, GA4 (measurement ID G-ZGGTSS0QFN). | Security threat triage, DDoS defense, debugging, performance analysis. | Google Cloud Logging, Google Analytics. | NONE SOLD / NONE SHARED |
| G. Geolocation DataCoarse country/region location via IP address (no precise GPS). | YES (Coarse only) | IP address network routing lookup. | Territorial licensing compliance, VAT/sales tax calculations. | Authorized payment processor / tax calculation engine. | NONE SOLD / NONE SHARED |
| H. Audio, Electronic & Visual InfoAudio masters (WAV/FLAC), stems, cover art, contracts. | YES | Direct creator uploads. | Checksum anchoring, cloud master storage, preview playback, licensee delivery. | Google Cloud Storage, IPFS pinning clusters. | NONE SOLD / NONE SHARED |
| I. Professional / Employment InfoPRO affiliations (ASCAP/BMI), publisher, label. | YES | Direct creator profile settings. | Rights management attribution, split sheet contract execution. | Smart contract signers, public registry. | NONE SOLD / NONE SHARED |
| J. Non-Public Education InfoTranscripts, student records (FERPA). | NO | N/A (None collected). | N/A | None. | NONE SOLD / NONE SHARED |
| K. Inferences Drawn from DataConsumer profiles, purchasing tendencies, behavior. | NO | N/A (No consumer profiling conducted). | N/A | None. | NONE SOLD / NONE SHARED |
| L. Sensitive Personal Information (SPI)Account login credentials, statutory tax IDs for payouts. | YES | Direct from consumer, Google OAuth credentials. | Authentication security; statutory 1099/W-8BEN tax filings when required by IRC § 6050W. | Authorized payment processor, IRS / statutory tax authorities. | NONE SOLD / NONE SHARED |
Zero Sale or Sharing of Personal Information
In the preceding 12 months, Sovranly IP has NOT sold or shared (for cross-context behavioral advertising) any Personal Information of California consumers as defined by Cal. Civ. Code §§ 1798.140(ad) and 1798.140(ah). We have no actual knowledge of selling or sharing personal information of consumers under 16 years of age.
Limitation on Use of Sensitive Personal Information
Under Cal. Civ. Code § 1798.121 and 11 CCR § 7027(m), Sovranly IP collects and processes Sensitive Personal Information (e.g., account credentials and tax identifiers) exclusively for permissible business purposes: providing the platform services requested, maintaining cybersecurity, verifying accounts, and complying with statutory fiscal laws. We do not use SPI to infer characteristics or for any secondary commercial purposes. Consequently, the statutory 'Right to Limit the Use of Sensitive Personal Information' is not triggered.
Global Privacy Control (GPC) & Opt-Out Signals
Pursuant to 11 CCR § 7025, Sovranly IP recognizes and honors universal opt-out preference signals, including the Global Privacy Control (GPC). If your browser broadcasts an affirmative GPC signal, our client-side scripts automatically disable non-essential telemetry and analytics cookies across your session without requiring manual configuration.
Authorized Agent Representation Protocol
Under 11 CCR § 7026, California consumers may designate an authorized agent to submit requests under the CCPA on their behalf. The agent must provide: (1) written authorization signed by the consumer or a valid power of attorney pursuant to California Probate Code §§ 4000-4465; and (2) verification of the consumer's own identity directly with Sovranly IP. Requests should be transmitted to create@sovranlyip.com.
California 'Shine the Light' Disclosure (Cal. Civ. Code § 1798.83): California Civil Code Section 1798.83 permits California residents to request annually certain information regarding our disclosure of Personal Information to third parties for their direct marketing purposes. Sovranly IP never discloses personal information to third parties for direct marketing. For inquiries, contact create@sovranlyip.com.
[04] How We Use and Process Your Data (Comprehensive Purpose Matrix)
Granular mapping of data elements to specific operational features, lawful bases, and retention terms.
| Data Category | Operational Purpose & Feature | Lawful Basis (GDPR / CCPA) | Third Parties / Processors | Retention Horizon |
|---|---|---|---|---|
| Google OAuth & Profile | Account authentication, creator profile creation, session verification, sending critical notifications. | Contractual Necessity (Art. 6(1)(b)) | Google Cloud, Firebase Auth | Duration of account tenure; purged within 30 days of deletion request. |
| Creative Assets & Stems | Generating media hashes, storing masters/stems, enabling preview playback, and delivering licensed audio to buyers. | Contractual Necessity (Art. 6(1)(b)) | Google Cloud Storage, IPFS Nodes | Retained while registered; deleted upon verified asset removal. |
| Cryptographic Checksums | Anchoring tamper-proof proof of existence and prior art to public distributed ledgers. | Legitimate Interests (Art. 6(1)(f)) | Ethereum, Arbitrum, Base, Polygon | Indefinite (permanent on-chain cryptographic proof). |
| Web3 Public Wallets | Deploying licensing contracts, receiving direct split payouts, signing authorization permits. | Contractual Necessity (Art. 6(1)(b)) | Public EVM Blockchains, RPC Nodes | Stored in profile until removed; on-chain history is permanent. |
| Billing & Payment Records | Processing subscription fees, managing license purchases, issuing invoices, statutory accounting. | Legal Obligation (Art. 6(1)(c)) & Contract | Authorized Payment Processor | 7 years following transaction date (statutory tax requirement). |
| Server & Telemetry Logs | Defending against DDoS, bot attacks, fraud detection, and evaluating user experience performance. | Legitimate Interests (Art. 6(1)(f)) & Consent | Google Cloud Logging, Google Analytics | 90 days rolling window for server logs; 14 months for GA4. |
1. Autonomous Licensing & Proof-of-Existence
We compute cryptographic media checksums (SHA-256 and keccak256) of uploaded creative masters and broadcast them to public consensus ledgers. This generates an immutable timestamp proving you possessed the asset prior to any third-party claim, creating legally defensible evidence of prior art.
2. Real-Time Royalty Dispersal
Smart contract logic uses registered wallet addresses and split percentages to route licensing revenues automatically to collaborators in real-time without centralized banking holds or payment delays.
3. Continuous Zero Trust Authentication
Every API call and state mutation verifies cryptographic JSON Web Tokens (JWTs) and validates caller ownership before executing. Identity claims are validated against Google OAuth and verified EVM wallet signatures.
4. Platform Reliability, Fraud Defense & Anti-Sybil
Telemetry and access logs are monitored in real-time to detect anomalous traffic, prevent unauthorized automated scraping of creator catalogs, block smart contract reentrancy exploits, and mitigate volumetric DDoS attacks.
5. Account & Billing Administration
Managing platform subscriptions, generating invoices, processing upgrade or renewal cycles, and fulfilling mandatory statutory corporate tax, audit, and accounting requirements.
6. Customer Care & Operational Alerts
Delivering critical service notifications, security advisories, policy revisions, and responding directly to support tickets, DMCA copyright notices, and licensing disputes.
[05] Artificial Intelligence (AI) & Machine Learning Usage Policies
Strict terms governing AI features, creator ownership, and training prohibitions.
ZERO AI TRAINING GUARANTEE
Sovranly IP may provide opt-in, creator-directed AI tools (powered by server-side Gemini API endpoints) to assist creators with metadata tagging, license agreement summarization, and rights verification. Our usage of AI adheres to the following non-negotiable principles:
1. No Foundation Model Training
Your audio masters, stems, lyrics, metadata, Google user data, and personal communications are NEVER used to train, retrain, fine-tune, or develop general artificial intelligence models, foundation models, or third-party generative algorithms.
2. Ephemeral Processing
AI analysis requests are executed via secure, stateless server-side API calls. Data sent to the model is processed strictly in-memory to generate the immediate user-facing output and is not cached or retained by AI infrastructure providers.
3. 100% Creator Ownership
You retain exclusive, unencumbered intellectual property ownership over all prompts, uploaded content, and AI-assisted metadata outputs generated through Sovranly IP.
4. Search Engine & Google Verification Bot Access
All verified search engine crawlers, platform verification bots, and indexers (including Googlebot and Google-InspectionTool) are explicitly whitelisted and granted uninterrupted, challenge-free access to all public pages, legal notices, and documentation. Sovranly IP does not serve bot challenges, captchas, rate limits, or login walls to verified search and verification services.
[06] Legal Bases for Data Processing & Non-Profiling (GDPR Arts. 6, 9 & 22)
Lawful grounds under the EU General Data Protection Regulation (GDPR) and UK GDPR.
| Legal Ground | Applicable Processing Activities | Scope & User Safeguards |
|---|---|---|
| Contractual Necessity (Art. 6(1)(b)) | Executing licensing agreements, distributing royalties, maintaining user account authentication, and recording IP notarizations. | Required to provide the core services requested by the creator. |
| Legitimate Interests (Art. 6(1)(f)) | Enforcing Zero Trust platform security, network threat mitigation, preventing piracy and copyright fraud, and optimizing app performance. | Balanced against your individual privacy rights under a documented Legitimate Interests Assessment (LIA); strict data minimization observed. |
| Explicit Consent (Art. 6(1)(a)) | Non-essential analytical cookies (Google Analytics GA4), marketing communications, and personalized preferences. | Freely given, granular, and revocable at any time via the Storage & Cookie Governance Matrix or browser GPC signals. |
| Legal Obligation (Art. 6(1)(c)) | Tax and corporate accounting records, response to valid judicial warrants or subpoenas, and DMCA copyright dispute compliance. | Retained strictly for periods mandated by applicable statutory law (e.g., 7-year fiscal statutes). |
Special Categories of Personal Data (GDPR Art. 9)
Sovranly IP does NOT process Special Categories of Personal Data under GDPR Article 9(1). We do not collect, solicit, or infer personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health, or data concerning a natural person's sex life or sexual orientation. Users are instructed not to submit special category data to the platform.
Automated Decision-Making & Profiling (GDPR Art. 22)
Sovranly IP does NOT subject users to automated decision-making or profiling that produces legal effects concerning them or similarly significantly affects them pursuant to GDPR Article 22. All intellectual property registrations, licensing terms, royalty distribution split sheets, and access decisions are explicitly configured, reviewed, and authorized by human creators or counterparties.
[07] Third-Party Subprocessors & Service Providers
Verified infrastructure partners contracted to deliver platform capabilities.
| Subprocessor | Role & Activity | Data Elements Handled | Jurisdiction & Safeguards |
|---|---|---|---|
| Google Cloud & Firebase | Cloud hosting, serverless edge functions, Firestore database, and OAuth authentication. | Email, User ID, authentication tokens, IP metadata, catalog records. | United States / Global (ISO 27001, SOC 2, EU Standard Contractual Clauses). |
| Google Analytics (G-ZGGTSS0QFN) | Anonymized site traffic diagnostics and interaction analytics. | Aggregated page views, browser user-agents, anonymized IP telemetry. | United States (Opt-out available via cookie settings or browser DNT headers). |
| Authorized Payment Gateways | Fiat payment gateway, subscription management, automated invoicing. | Billing address, email, card brand/last 4, subscription plan IDs. | United States / Global (PCI-DSS Level 1 Certified). |
| IPFS Gateways & Pinning Nodes | Decentralized peer-to-peer storage of hashed creative assets. | Cryptographic file hashes (CIDs), encrypted media chunks. | Decentralized Global Network (Public Swarm). |
| Decentralized EVM Blockchains | Public consensus ledger for smart contracts and royalty settlements. | Public wallet addresses, contract bytecode, royalty shares, tx hashes. | Decentralized Peer-to-Peer Networks (Ethereum, Arbitrum, Optimism, Base, Polygon). |
[08] Blockchain Immutability & Public Ledger Disclosures
Crucial architectural distinction between off-chain and on-chain records.
Notice Regarding Decentralized Ledger Permanence
When you deploy a smart contract, register an intellectual property claim, or execute a royalty split on a decentralized blockchain network (such as Ethereum, Arbitrum, Polygon, Base, or Optimism), that transaction is permanently written to a publicly auditable distributed ledger.
- Inability to Modify or Erase: Neither Sovranly IP nor any single party possesses the cryptographic authority to edit, overwrite, roll back, or delete data once broadcast to a public blockchain network.
- Public Visibility: Anyone with a blockchain explorer can observe your public wallet address, transaction amounts, timestamps, and contract parameters.
- Interactions with 'Right to be Forgotten': Statutory deletion rights under GDPR Article 17 and CCPA apply to off-chain records hosted in our centralized systems, but cannot technically or physically alter decentralized blocks confirmed by thousands of independent network validators.
[09] Information Sharing & Zero Data Monetization
Sovranly IP maintains an unyielding commitment: We do not sell, rent, monetize, or disclose your personal data or creative work to third parties for commercial exploitation or advertising purposes.
Information is strictly disclosed only in the following bounded circumstances:
Authorized Subprocessors
Shared exclusively with vetted technical vendors (cloud infrastructure, payment processors) strictly to perform operational functions under contractual confidentiality.
Public Blockchain Networks
Broadcast to distributed ledgers when you deliberately initiate an on-chain registration, licensing agreement, or royalty payout.
Mandatory Legal Compliance
Disclosed only when compelled by enforceable court orders, subpoenas, statutory tax authorities, or to defend against imminent intellectual property infringement.
[10] Data Storage Topology & Technical and Organizational Security Measures (TOMs - GDPR Art. 32)
Multi-tier zero-trust infrastructure, cryptographic key management, automated backup cycles, media sanitization, and continuous audit protocols.
STORAGE & ARCHITECTURE
Sovranly IP implements state-of-the-art Technical and Organizational Measures (TOMs) pursuant to GDPR Article 32, NIST SP 800-53 (Rev. 5), and ISO/IEC 27001 standards to ensure a level of cybersecurity appropriate to the risk of unauthorized access, accidental destruction, alteration, or disclosure of creator data and intellectual property.
Tier 1: Operational NoSQL State Store (Cloud Firestore)
GCP US-WEST1
Structured creator accounts, authentication sessions, catalog metadata profiles, and digital split sheet drafts reside in Google Cloud Firestore with multi-region replication. Every read and write transaction is evaluated by continuous Zero Trust server-side security rules, least-privilege IAM roles, and AES-256 server-side encryption with automated cryptographic key rotation.
Security Controls: Granular collection security rules, caller UID token validation, rate limiting, and zero-implicit-trust request filters.
Tier 2: Encrypted Binary Object Storage (Cloud Storage CMEK)
SIGNED URLS
Audio master recordings (lossless WAV, 24-bit/48kHz or 96kHz), multitrack stems, and high-resolution cover artwork are isolated in dedicated Google Cloud Storage buckets. Files are encrypted at rest with Customer-Managed Encryption Keys (CMEK) via Google Cloud KMS. Download and stream access is restricted exclusively through cryptographically signed URLs with strict time-to-live limits (TTL ≤ 15 minutes).
Security Controls: Ephemeral HMAC-SHA256 signed tokens, origin validation, CORS lockdown, and anti-hotlinking headers.
Tier 3: Distributed Content-Addressed Swarm (IPFS Pinning)
CONTENT CIDs
Immutable metadata manifests, licensing schemas, and public previews are pinned across decentralized IPFS clusters. Assets are addressed by cryptographic content identifiers (CIDs) computed via SHA-256 or keccak256 algorithms, ensuring complete tamper-evidence. Private stems and confidential creator documents are never broadcast unencrypted to the IPFS swarm.
Security Controls: Content-addressed immutability, cryptographic CID verification, peer-to-peer pinning redundancy.
Tier 4: Public Consensus Ledger (EVM Smart Contracts)
ON-CHAIN
Smart contract logic, commercial license tokenization, and irreversible ownership claims are permanently recorded on public EVM networks (Ethereum, Arbitrum, Base, Optimism, Polygon). On-chain data is confined to non-invertible hashes, numeric split ratios, and cryptographic wallet addresses—no plaintext personally identifiable information is stored on-chain.
Security Controls: Formally verified bytecode, audited OpenZeppelin reentrancy guards, and cryptographic multisig governance.
Envelope Encryption & Cryptographic Key Lifecycle (FIPS 140-2 / FIPS 140-3 Level 3)
Sovranly IP employs a two-tier envelope encryption architecture. High-entropy Data Encryption Keys (DEKs) encrypt raw data records and binary blobs at rest using AES-256-GCM (Galois/Counter Mode), guaranteeing both cryptographic confidentiality and authenticated integrity against bit-flipping tampering.
DEKs are themselves encrypted using Key Encryption Keys (KEKs) maintained within Google Cloud Key Management Service (Cloud KMS) backed by FIPS 140-2 / FIPS 140-3 Level 3 certified Hardware Security Modules (HSMs). KEKs are configured with mandatory 365-day automated cryptographic rotation schedules. Plaintext cryptographic keys never enter server memory in unencrypted states and are never written to swap space or persistent disks.
Zero Trust Network Security & Least Privilege Access Controls (PoLP)
Under our Zero Trust architecture, no entity—internal microservice, administrator workstation, or third-party client—is trusted implicitly by virtue of network locality:
1. Continuous Token Validation
Every API invocation validates short-lived signed JWTs, verifying caller UID, issuance timestamps, and cryptographic claim boundaries.
2. Mutual TLS (mTLS) Mesh
All internal service-to-service communication is encrypted using ephemeral mTLS certificates with strict SPIFFE/SPIRE workload identities.
3. Role-Based Access (RBAC)
Strict Attribute & Role-Based Access Controls enforce least privilege. Employees have zero access to production user keys or master audio vaults.
Backup Cycles, PITR & Deletion Propagation
- Continuous Point-in-Time Recovery (PITR): Firestore maintains a rolling 7-day PITR retention window enabling instantaneous state reconstruction during infrastructure anomalies.
- Encrypted Cold Snapshots: Daily differential snapshots are stored in air-gapped, cross-regional storage buckets encrypted with independent KMS keys, retained for a maximum of 30 days before automated cyclic overwriting.
- Tombstoned Deletion Cascades: When a data subject executes an erasure request, tombstone identifiers ensure that restored rollback backups purge previously deleted records before resuming write traffic.
Media Sanitization & Decommissioning Standards
In compliance with NIST SP 800-88 Revision 1 ('Guidelines for Media Sanitization') and DoD 5220.22-M standards, underlying storage hardware in Google Cloud facilities undergoes rigorous multi-pass cryptographic erasure prior to re-allocation, and physical magnetic or solid-state media slated for decommissioning is physically shredded or degaussed. Centralized software caches and temporary upload buffers are purged immediately upon session termination.
Storage Security Measures & Technical TOMs Specification Matrix
| Security Dimension | Standard / Compliance Baseline | Implementation Architecture | Key Rotation / Expiry | Verification & Audit Method |
|---|---|---|---|---|
| Encryption at Rest | FIPS 140-2 / 140-3 Level 3 | AES-256-GCM Envelope Encryption (DEK/KEK in Cloud KMS HSM) | 365-Day Auto-Rotation | Cloud Audit Logs & SOC 2 Type II |
| Encryption in Transit | TLS 1.3 / RFC 8446 | ECDHE-ECDSA-AES256-GCM-SHA384 / ChaCha20-Poly1305 + HSTS Preload | 90-Day Ephemeral Certs | Qualys SSL Labs A+ Verification |
| Access Authorization | Zero Trust / NIST SP 800-207 | Short-Lived Signed JWTs, Firestore Security Rules, PoLP RBAC | 1-Hour Token Expiry | Automated Security Assertion Rules |
| Media Master Delivery | CMEK Object Vaulting | Cloud Storage Buckets with Time-Limited Cryptographic Signed URLs | ≤ 15-Minute URL TTL | HMAC-SHA256 Signature Checks |
| State Reconstruction | ISO 22301 Business Continuity | Rolling 7-day Firestore PITR + Air-Gapped Cross-Region Cold Backups | Daily Snapshots (30d purge) | Quarterly Disaster Recovery Drills |
| Hardware Erasure | NIST SP 800-88 Rev. 1 | Multi-Pass Cryptographic Wipe + Physical Shredding on Decommission | Immediate on Hardware EOL | Google Cloud Data Center Certificates |
[11] Data Retention, Archival & Deletion Schedules
Explicit retention windows for each classification of stored information.
| Data Category | Retention Horizon | Deletion & Archival Protocol |
|---|---|---|
| Account Profile & Auth Tokens | Duration of active account tenure. | Permanently purged within 30 days of receiving a verified account deletion request. |
| Fiscal & Subscription Records | 7 years following transaction date. | Required by statutory corporate tax, audit, and anti-fraud regulations. |
| Server Access & Security Logs | 90 days rolling window. | Automatically overwritten and purged via automated log rotation scripts. |
| Customer Support Inquiries | 2 years following ticket resolution. | Archived to reference past copyright disputes or ownership resolutions. |
| On-Chain Blockchain Data | Indefinite / Permanent. | Inherent to decentralized cryptographic consensus mechanisms. |
[12] Data Deletion, Export & Google Access Revocation Guide
Direct controls and step-by-step instructions for disconnecting Google OAuth, exporting assets, and erasing off-chain data.
SELF-SERVE & VERIFIED CONTROLS
OAUTH ACCESS REVOCATION
Revoke Google Account Access
You maintain unilateral control to disconnect Sovranly IP from your Google Account at any second via Google's security dashboard:
- Navigate to Google Third-party apps & services.
- Scroll to or search for Sovranly IP in your connected apps list.
- Click on Sovranly IP and select 'Delete all connections you have with Sovranly IP' or 'Remove Access'.
- Confirm the prompt. Google immediately revokes active OAuth refresh tokens.
Zero Trust Invalidation: Our backend continuously checks token validity. Once Google revokes access, your active session on Sovranly IP is immediately invalidated and no further profile requests can succeed.
GDPR ART. 17 • CCPA ERASURE
Permanent Off-Chain Erasure
Demand the irreversible deletion of your personal data and creative catalog records from all Sovranly IP servers:
- What is Purged: Your name, Google email, avatar, Firestore profile document, unanchored drafts, payment customer linkages, telemetry records, and audio stem caches.
- On-Chain Decoupling: Smart contract splits and cryptographic hashes confirmed on public EVM blockchains cannot be rolled back, but all off-chain pointers to your identity are permanently erased.
- Execution Window: Completed within 30 calendar days of cryptographic verification at zero cost.
Email create@sovranlyip.com with subject line 'Account Erasure Request' from your registered email address.
GDPR ART. 20 PORTABILITY
Data Portability & Catalog Export
Export all intellectual property assets, license contracts, and royalty history in open standard formats:
- Delivered Formats: Structured JSON catalog archive, cryptographic SHA-256 / keccak256 checksum manifest, and CSV royalty logs.
- Interoperability: Formatted for seamless migration to external digital rights management tools, accounting suites, or sovereign backup drives.
- Verification: Dispatched securely via encrypted download link after challenge verification.
Email create@sovranlyip.com with subject line 'Data Portability Request' to receive your export package.
[13] Your Statutory Rights & Recourse (GDPR Arts. 15-22, CCPA/CPRA & Global Frameworks)
Comprehensive statutory protections, multi-channel verification protocols, technical fulfillment mechanics, and supervisory authority recourse.
STATUTORY RECOURSE
Sovranly IP guarantees sovereign data self-determination. Regardless of whether you reside in the European Economic Area (GDPR), the United Kingdom (UK GDPR / DPA 2018), California (CCPA/CPRA), Brazil (LGPD), Canada (PIPEDA), or Switzerland (FADP), we provide a unified, accessible suite of statutory rights without administrative fees or discriminatory consequences:
Right of Access & Right to Know (GDPR Art. 15 / CCPA § 1798.110)
Demand complete confirmation whether your data is being processed, full access to stored profile records, purposes of processing, categories of personal data collected, specific sources, third-party recipients, and statutory retention horizons.
Right to Rectification & Correction (GDPR Art. 16 / CCPA § 1798.106)
Demand the immediate correction of inaccurate creator attributes, updated ISNI/PRO registrations, corrected royalty split percentages, or completion of incomplete catalog records without undue delay.
Right to Erasure / 'Right to be Forgotten' (GDPR Art. 17 / CCPA § 1798.105)
Demand permanent, irreversible erasure of all off-chain profile data, uploaded audio masters, stems, contact details, and database records from Google Cloud Firestore and Storage buckets within 30 days of verification.
Right to Restrict Processing (GDPR Art. 18)
Require suspension of active catalog dissemination, commercial licensing, or automated processing during accuracy verification, ownership dispute arbitration, or pending formal legal challenges.
Right to Data Portability (GDPR Art. 20 / CCPA § 1798.130)
Obtain your entire creator catalog, ISRC/ISWC manifests, split sheet agreements, and payment transaction logs in a structured, commonly used, machine-readable JSON and CSV format for frictionless migration to external systems.
Right to Object to Processing (GDPR Art. 21)
Object on grounds relating to your particular situation against processing based on legitimate interests. Possess an absolute, unconditional right to immediately halt any direct marketing communications.
Rights Regarding Automated Decisions & Non-Profiling (GDPR Art. 22)
Guaranteed protection from decisions based solely on automated processing or AI profiling that produce legal effects or significantly affect your licensing eligibility. All dispute resolutions feature human administrative oversight.
Right to Opt-Out of Sale or Sharing (CCPA § 1798.120)
Exercise your statutory right to prohibit the sale or sharing of your personal data. Sovranly IP enforces a zero-sale, zero-cross-context-tracking posture across all accounts by default.
Right to Non-Discrimination & Equal Service (CCPA § 1798.125)
Never experience denial of platform services, altered pricing, degraded audio stream quality, or slower smart contract interactions as a result of exercising any California or international privacy rights.
Step-by-Step Practical Rights Exercise & Cryptographic Verification Protocol
To safeguard creator catalogs against impersonation, unauthorized account takeover, or fraudulent data exfiltration, Sovranly IP executes a rigorous, multi-factor verification protocol:
Step 1: Request Initiation
Transmit your request to create@sovranlyip.com with the subject line "Subject Access Request" or "Account Erasure Request".
Step 2: OAuth Challenge
We send an encrypted verification nonce directly to the registered Google OAuth primary email address associated with your creator account.
Step 3: Web3 Signature
For requests involving on-chain wallet records, sign an EIP-712 structured cryptographic challenge via your linked Web3 wallet provider.
Step 4: 30-Day Fulfillment
Complete execution within 30 calendar days at zero cost, delivering structured JSON archives or cryptographic deletion certificates.
Statutory Rights Technical Fulfillment Matrix
| Statutory Right | Applicable Laws | Technical Fulfillment Action | Verification Challenge | Statutory Fulfillment Window |
|---|---|---|---|---|
| Right of Access / Know | GDPR Art. 15, CCPA § 1798.110, LGPD Art. 18(II) | Automated export of all Firestore profile documents and metadata schemas | OAuth Email + JWT Nonce | Within 30 Days |
| Right to Rectification | GDPR Art. 16, CCPA § 1798.106, LGPD Art. 18(III) | Direct database patch to creator profile, ISNI/PRO attributes, and split splits | In-App Authenticated Session | Immediate to 10 Days |
| Right to Erasure / Delete | GDPR Art. 17, CCPA § 1798.105, LGPD Art. 18(VI) | Cascading purge of Cloud Storage binaries, Firestore records, and tombstone propagation | OAuth Nonce + EIP-712 Signature | Within 30 Days |
| Right to Data Portability | GDPR Art. 20, CCPA § 1798.130, LGPD Art. 18(V) | Delivery of encrypted JSON archive containing track catalogs, split sheets, and receipts | OAuth Email Nonce | Within 30 Days |
| Right to Restrict / Object | GDPR Arts. 18 & 21, LGPD Art. 18(IX) | State lock placed on public marketplace listings and immediate suppression from alerts | OAuth Email Challenge | Within 48 Hours |
| Opt-Out of Sale / Sharing | CCPA § 1798.120, CPRA 11 CCR § 7025 (GPC) | Global Privacy Control (GPC) automatic header detection and cookie suppression | Automated Browser Signal | Instantaneous |
Right to Lodge a Formal Regulatory Complaint (GDPR Art. 77 & Global Recourse)
Pursuant to GDPR Article 77 and equivalent global data protection frameworks, if you consider our processing of your personal data to infringe statutory privacy regulations, you possess the unalienable right to lodge a formal complaint with a competent Supervisory Authority in your country or region:
| Supervisory Authority | Jurisdiction | Statutory Competence | Official Portal & Recourse |
|---|---|---|---|
| Data Protection Commission (DPC) | Ireland / EU Lead Authority | General Data Protection Regulation (GDPR) oversight across EU cloud infrastructures. | dataprotection.ie |
| Information Commissioner's Office (ICO) | United Kingdom | UK GDPR and Data Protection Act 2018 enforcement. | ico.org.uk |
| CNIL (Commission Nationale) | France | French Data Protection Act & GDPR compliance enforcement. | cnil.fr |
| BfDI (Federal Commissioner) | Germany | Federal Data Protection Act (BDSG) & European GDPR oversight. | bfdi.bund.de |
| California Privacy Protection Agency (CPPA) | California, United States | California Consumer Privacy Act (CCPA) and California Privacy Rights Act (CPRA). | cppa.ca.gov |
| Federal Data Protection & Information Commissioner (FDPIC) | Switzerland | Swiss Federal Act on Data Protection (revFADP). | edoeb.admin.ch |
| Office of the Privacy Commissioner of Canada (OPC) | Canada | Personal Information Protection and Electronic Documents Act (PIPEDA). | priv.gc.ca |
| Autoridade Nacional de Proteção de Dados (ANPD) | Brazil | Lei Geral de Proteção de Dados Pessoais (LGPD). | gov.br/anpd |
[14] Zero Trust Cryptographic Security & Breach Protocols (GDPR Arts. 32-34)
Technical mechanisms protecting data integrity and mandatory 72-hour incident response obligations.
ZERO TRUST CRYPTOGRAPHY
End-to-End Cryptographic Encryption (Art. 32(1)(a))
All network traffic in transit is encrypted utilizing modern Transport Layer Security (TLS 1.3) with ephemeral Diffie-Hellman key exchanges (ECDHE). Data at rest in Cloud Firestore and Cloud Storage is encrypted with military-grade AES-256-GCM algorithms backed by FIPS 140-2 Level 3 KMS hardware security modules.
Continuous Token Authorization (Zero Trust)
In accordance with Zero Trust principles, no internal network perimeter or service mesh is trusted implicitly. Every incoming API request cryptographically verifies short-lived JSON Web Tokens (JWTs) and validates caller ownership before executing state transformations.
Non-Custodial Architecture & Client-Side Signing
We do not hold, store, or escrow private keys or seed phrases. Web3 transactions, licensing agreements, and smart contract deployments require explicit client-side signing via external Web3 providers (MetaMask, Coinbase Wallet, WalletConnect), ensuring platform servers cannot sign unauthorized transactions.
Automated Vulnerability Scanning & Static Analysis
Smart contracts undergo static analysis, formal verification routines, and fuzz testing against reentrancy, integer overflows, and front-running vectors. Containerized cloud run instances are continuously audited via automated vulnerability scanners.
Statutory Personal Data Breach Incident Response (GDPR Arts. 33 & 34)
In the event of a confirmed security incident resulting in the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to personal data, Sovranly IP executes the following statutory breach containment and notification protocol:
[GDPR ART. 33] SUPERVISORY AUTHORITY NOTIFICATION
Notification without undue delay, and where feasible, not later than 72 hours after becoming aware of the breach to competent lead authorities (e.g., Data Protection Commission), detailing nature of incident, categories and approximate number of data subjects affected, contact details of the DPO, likely consequences, and remediation measures taken.
[GDPR ART. 34] DIRECT DATA SUBJECT COMMUNICATION
When a personal data breach is likely to result in a high risk to the rights and freedoms of natural persons, Sovranly IP communicates the incident directly to affected creators via registered email and public platform bulletin within 48 hours, detailing clear mitigation steps and security advisory notices.
[15] International Transfers & Cross-Border Safeguards (SCCs & DPF)
Cross-border transfer mechanisms, European Commission Standard Contractual Clauses, and Data Privacy Framework compliance.
CROSS-BORDER TRANSFERS
Sovranly IP is headquartered and operated from primary secure computing facilities in the United States of America, supplemented by global edge caching distribution networks. If you access or interact with the platform from the European Economic Area (EEA), the United Kingdom, Switzerland, or other international jurisdictions with extraterritorial data protection frameworks, your personal information is transferred to and processed within the United States.
[EU SCCs] STANDARD CONTRACTUAL CLAUSES
For transfers of personal data originating in the EEA to third countries lacking adequacy decisions under GDPR Article 45, Sovranly IP relies on the European Commission's Standard Contractual Clauses (Implementing Decision (EU) 2021/914), incorporating Module 1 (Controller-to-Controller) and Module 2 (Controller-to-Processor) data processing agreements with all cloud infrastructure subprocessors.
[DPF COMPLIANCE] DATA PRIVACY FRAMEWORK
Sovranly IP adheres to the principles of the EU-U.S. Data Privacy Framework (EU-U.S. DPF), the UK Extension to the EU-U.S. DPF, and the Swiss-U.S. Data Privacy Framework as set forth by the U.S. Department of Commerce regarding the collection, processing, and retention of personal information from member countries.
[SCHREMS II / TIAs] SUPPLEMENTARY MEASURES
In accordance with the CJEU Schrems II ruling (Case C-311/18) and EDPB Recommendations 01/2020, Sovranly IP conducts comprehensive Transfer Impact Assessments (TIAs) and enforces strict supplementary technical measures: full cryptographic payload encryption at rest (AES-256-GCM), TLS 1.3 in transit, and customer-managed KMS key ownership preventing unmonitored foreign surveillance access.
[16] Children’s Online Privacy Protections (COPPA & GDPR Art. 8)
Sovranly IP is an enterprise intellectual property and smart contract management platform designed strictly for creators who are at least 18 years of age (or the legal age of majority in their jurisdiction). We do not knowingly solicit, collect, or process personal data from individuals under 18 under the Children’s Online Privacy Protection Act (COPPA, 15 U.S.C. 6501–6506) or GDPR Article 8. If we discover that personal information of a minor has been inadvertently recorded, we will take immediate measures to permanently eradicate such records from our databases. If you believe a minor has registered an account, please notify us immediately at create@sovranlyip.com.
[17] Storage & Cookie Governance Matrix
Live, transparent ledger of localized parameters, cookies, and tokens.
Dynamic Cryptographic Audit
Active Client State & Local Verification
Your Active Consent Signature
PENDING EXPLICIT SIGNATURE
No custom consent receipt detected. The platform is currently enforcing high-privacy zero-knowledge defaults.
Zero-Trust Directive Verification
Unlike traditional third-party cookie banners that transmit user profiles to cloud ad servers, Sovranly IP computes and validates your consent signature locally in your browser sandbox.
| Key / Cookie Name | Storage Type | Category | Retention | Purpose Description | Current Status |
|---|---|---|---|---|---|
| sovranly_theme | LocalStorage | User Preference | Persistent | Stores your preferred UI color scheme (Light Mode vs. Dark Mode) across sessions. | ACTIVE |
| sovranly_cookie_consent_receipt | LocalStorage | Sovereign Compliance | Persistent | Records your custom compliance signature, timestamp, and consent vectors to prevent re-prompt overlays. | INACTIVE |
| sovranly_essential_consent | Cookie / Local | Core Essential | 1 Year | Maintains zero-trust session security tokens, wallet connection addresses, and routing destinations. | ALWAYS ON |
| sovranly_analytics_consent | Cookie / Local | Diagnostics | 1 Year | Permits localized performance diagnostic tests and Google Analytics 4 telemetry to optimize global platform rendering. | DISABLED |
| sovranly_preferences_consent | Cookie / Local | UI Persistence | 1 Year | Caches sidebar open/closed states, layout density modes, and developer tool selections. | DISABLED |
[18] Data & Privacy Frequently Asked Questions (FAQ)
Authoritative compliance clarifications regarding IP metadata, wallet addresses, and third-party processors.
Expand AllCollapse All
IP METADATA & ASSETSGDPR ART. 5(1)(c)
How does Sovranly IP handle, store, and protect my creative works, media files, and catalog metadata?
Sovranly IP enforces Cryptographic Data Minimization across all catalog operations. When you register or notarize a work (such as an audio track, musical stem, video, cover artwork, or licensing contract), our system treats your raw media with the highest confidentiality:
- Mathematical Hash Generation (SHA-256 / keccak256): Rather than storing unencrypted source masters on centralized public web servers, we generate deterministic cryptographic digests directly. This cryptographic hash proves existence and prior art timestamping without exposing your underlying creative files.
- Decentralized Content Addressing (IPFS): Assets pinned for public distribution or licensing verification are converted into content identifiers (CIDs) on the InterPlanetary File System (IPFS), shielding creators against single-point-of-failure server disruptions.
- Catalog Metadata Security: Associated track attributes (ISRC, ISWC, songwriter credits, publishing splits, and licensing terms) are maintained in Google Cloud Firestore protected by continuous Zero Trust access rules and encrypted at rest with AES-256.
- Anti-Scraping Protection: Your catalog metadata and audio stems are explicitly protected against automated scraping, indexing by AI model crawlers, or unauthorized bulk extraction.
WALLET ADDRESSESGDPR RECITAL 30 • CCPA § 1798.140
Are public blockchain wallet addresses treated as personal data, and how are they protected?
Yes. Under European Union GDPR (Recital 30) and the California Consumer Privacy Act (CCPA/CPRA), public cryptographic wallet addresses (such as Ethereum/EVM addresses 0x...) constitute pseudonymous personal data and online identifiers because they can theoretically be correlated with off-chain activity or transaction histories.
Sovranly IP processes your wallet address under the lawful basis of Contractual Necessity (Art. 6(1)(b) GDPR) to execute requested platform operations:
- Non-Custodial Architecture: Sovranly IP never requests, collects, stores, or transmits your private keys or wallet recovery seed phrases. You hold sole cryptographic authority over your funds and signatures through your personal provider (e.g., MetaMask, Coinbase Wallet, WalletConnect).
- Purpose Limitation: Your wallet address is utilized exclusively to route automated smart contract royalty disbursements, verify asset ownership rights, and confirm cryptographic license signatures.
- Decoupling & Isolation: Internal linkages between your Web3 wallet address and your Google OAuth email identity are protected by signed JSON Web Tokens (JWTs) and can be disconnected or deleted from our off-chain systems upon request.
BLOCKCHAIN IMMUTABILITYGDPR ART. 17 ERASURE
How does Sovranly reconcile the GDPR 'Right to Erasure' with the permanent immutability of blockchains?
Decentralized blockchain networks (Ethereum, Arbitrum, Base, Optimism, Polygon) are structurally immutable—once a block is confirmed by distributed consensus, no central organization, government, or platform can rewrite, amend, or erase historical blocks.
Sovranly IP maintains rigorous compliance with GDPR Article 17 ('Right to be Forgotten') and CCPA deletion mandates through our Dual-Layer Boundary Model:
Off-Chain Records (Fully Erasable)
Your name, Google OAuth profile, email address, customer billing pointers, telemetry logs, and catalog associations hosted in our cloud databases are permanently and irreversibly purged within 30 calendar days of receiving a verified deletion request.
On-Chain Ledger (Stateless Hashes)
Because on-chain transactions cannot be deleted, we prevent personal data leakage by hashing all asset metadata off-chain. Transactions on-chain consist only of pseudonymous contract executions and wallet-to-wallet transfer events, with no plain-text PII recorded.
THIRD-PARTY SUBPROCESSORSGDPR ART. 28 • CCPA SERVICE PROVIDERS
Which third-party vendors process my data, and what contractual compliance safeguards are enforced?
Sovranly IP contracts exclusively with enterprise-grade subprocessors that meet or exceed GDPR Article 28 data processing standards and CCPA service provider requirements. Each partner operates under legally binding Data Processing Agreements (DPAs) with strict purpose limitations:
- Google Cloud Platform & Firebase: Provides secure edge hosting, Firestore databases, and Google OAuth. Certified under ISO/IEC 27001, SOC 2 Type II, and adhering to European Commission Standard Contractual Clauses (SCCs) for cross-border data protection.
- Payment Processors: Processes fiat subscription payments and licensing invoices as certified PCI-DSS Level 1 Service Providers. Sovranly IP never receives, handles, or stores sensitive credit card credentials.
- Google Analytics 4 (G-ZGGTSS0QFN): Collects anonymized platform interaction metrics with IP anonymization enabled. You can disable telemetry at any time via the Sovereign Storage & Cookie Governance Matrix.
- Decentralized RPC Nodes & IPFS Pinning Services: Facilitates blockchain broadcasts and decentralized file accessibility without transmitting user identity profiles.
ZERO DATA MONETIZATIONVERIFIED BOTS WHITELISTED
Does Sovranly sell creator data, or block search engines and Google verification crawlers?
Strict Non-Monetization Policy: Sovranly IP does not sell, rent, license, or barter your personal information, catalog listings, audio stems, artwork, or contact data to data brokers, ad-tech aggregators, or third-party AI labs.
In accordance with CCPA/CPRA regulations granting California consumers the right to opt out of the sale or sharing of personal information, Sovranly IP maintains a zero-sale posture across the entire platform by default.
Search Engine & Google Verification Bot Whitelisting: While private asset repositories are protected by cryptographic token authentication, all public pages, legal notices, terms, and metadata are 100% open and crawlable. Verified search engine crawlers, platform verification bots, and Google review crawlers (such as Googlebot and Google-InspectionTool) are explicitly whitelisted and permanently exempted from any bot challenges, rate limiting, or WAF verification checks. We never serve interstitial challenge pages, captchas, or login walls to verified inspection bots.
EXERCISING YOUR RIGHTS30-DAY FULFILLMENT WINDOW
How can I submit a formal Subject Access Request (SAR), export my catalog, or delete my account?
You can exercise any of your statutory GDPR or CCPA/CPRA rights (Access, Correction, Erasure, Data Portability, or Processing Restriction) with no administrative fees:
- Email Submission: Send an email to create@sovranlyip.com with the subject line
Subject Access RequestorAccount Erasure Request. - Identity Verification: To protect creator catalogs from social engineering attacks, we verify your identity by sending a confirmation challenge to your registered Google OAuth email or requesting a cryptographic signature verification from your linked Web3 wallet.
- Fulfillment Horizon: Verified requests are resolved within 30 calendar days. In cases of data export requests, we provide a structured, machine-readable JSON archive of your catalog metadata, licensing terms, and account transaction histories.
[19] Contact Information & Data Protection Officer
If you have any questions, concerns, complaints, or requests regarding this Privacy Policy, your personal data, or our Zero Trust security protocols, please reach out directly to our dedicated Data Protection & Compliance Office:
Sovranly IP — Data Protection & Legal Compliance Office
Primary Contact: create@sovranlyip.com
Platform URL: https://www.sovranlyip.com
Applicable Jurisdiction: United States of America
Standard Response Horizon: Within 30 calendar days
If you are located in the European Union or United Kingdom and believe your privacy rights have been infringed, you also have the right to lodge a formal complaint with your national Supervisory Authority (e.g., the Information Commissioner's Office in the UK, CNIL in France, or BfDI in Germany).