One Public Record Across Web, Applications, Vendors, Advertising, Data Rights and Security Operations
The website, mobile applications, application-store listings, consent interface, vendor configuration, advertising systems and public policies must describe the same real operation. A privacy policy cannot state that optional tracking is consent-based while an application activates it before choice. A deletion page cannot promise account deletion if the application has no working route. A public security policy cannot be treated as implemented until the contact, access control, logs and incident process operate.
| Inventory domain | Required record |
|---|---|
| Web platform | Hosting, CDN, content management, theme, extensions, search, forms, cache, media storage and backups |
| Applications | Bundle identifiers, versions, stores, SDKs, permissions, login, notifications, analytics, crash reporting and advertising |
| Data purposes | Reading, account, location relevance, personalisation, notifications, analytics, security, advertising, contributor, grievance and commercial processing |
| Providers | Legal entity, service, role, processing location, contract, access, retention and subprocessor information |
| Cookies and local storage | Name, provider, category, purpose, duration, consent state and domain |
| Advertising | Networks, contextual or personalised mode, audience data, conversion measurement, frequency control and paid-content systems |
| Retention | Operational, legal, source, grievance, applicant, commercial, security and backup periods |
| Rights routes | Access, correction, deletion, objection, withdrawal, account closure and appeal |
| Security | Asset owner, authentication, encryption, logs, patching, vulnerability, incident, backup and restoration controls |
The entity identified in the Corporate Legal Notice, Privacy Policy, application-store privacy disclosure, account interface, form notices and vendor contracts must remain consistent with the actual role. Subkuz Media Networks Pvt Ltd ( SMN ) is described according to the locked corporate and technology relationship and does not receive editorial authority merely because it owns, licenses, develops, hosts or supports technology. A provider acting on instructions is not described as the independent publisher. Any provider processing for its own purpose is separately assessed and disclosed.
| Permission or capability | Launch rule |
|---|---|
| Precise location | Request only when a user chooses a function that genuinely requires precision; general local news should ordinarily work with city selection or less precise data |
| Approximate location | Explain purpose and allow manual edition selection |
| Notifications | Separate opt-in and granular preference where available |
| Photos, camera or microphone | Request in context for a user-initiated submission or capture function |
| Contacts | Do not request for ordinary news reading |
| Background activity | Use only where necessary and disclosed |
| Tracking across apps or sites | Follow platform and applicable consent rules; do not describe as necessary merely because an ad provider prefers it |
| Account data | Collect only fields needed for the service and rights process |
Grievance, privacy, source, applicant, copyright and security forms must not expose message content, names, email addresses, uploaded file names or case references to advertising pixels, session replay, heat maps or broad analytics. The confirmation URL must not contain personal or case data. Form events may record a privacy-safe success or failure signal only where it is necessary and lawfully configured.
Advertising and paid-publication systems store client identity, ultimate beneficiary, claims evidence, contracts, approval, disclosure, links and payment records separately from independent newsroom source and grievance data. An advertiser cannot upload a page directly to production. Every commercial item passes classification, disclosure, claims, rights, landing-page, data-use and search-integrity review. Ad scripts are tested for consent, performance, accessibility, security and unexpected redirects.
The public Security Vulnerability and Responsible Disclosure page and form must be live before security.txt is published. security.txt is served over HTTPS at /.well-known/security.txt with a current Contact, Expires, Preferred-Languages, Canonical and Policy field. The expiry is reviewed before it lapses. The contact is monitored by a primary and backup owner. A public encryption key is added only after a maintained key and verification process exist.
| Stage | Required action |
|---|---|
| Detect | Preserve alert, timestamp, affected asset and reporter information |
| Contain | Restrict access, disable affected integration, rotate secrets and protect evidence |
| Assess | Determine data, source, editorial, commercial, availability and legal impact |
| Notify | Inform authorised internal owners and external parties where law or safety requires |
| Recover | Restore from a verified state and validate the affected public routes |
| Learn | Record cause, correction, policy or configuration change and public notice where material |
Consent, account, deletion, grievance, correction, privacy, accessibility and security journeys are tested by keyboard and screen reader. Third-party scripts must not block core content, trap focus, create uncontrolled motion or cause severe layout shift. Performance budgets are applied to homepage, article, city, policy and form templates. A revenue script is not exempt from accessibility, security or performance review.
| DOCUMENT CONTROL | DETAILS |
|---|---|
| Issued by | Subkuz Media Networks Private Limited |
| Corporate Identification Number | CIN U72900JH2020PTC014521 |
| Document classification | Developer implementation instrument |
| Effective date | 6 August 2026 |
| Last reviewed | 7 August 2026 |
| Previous legal name during statutory disclosure period | Subkuz Media Networks Private Limited |