DOC #075 03_DEVELOPER_IMPLEMENTATION

SUBKUZ WEBSITE, APPLICATION, PRIVACY, COMMERCIAL AND SECURITY RECONCILIATION SPECIFICATION

Subkuz Global Governance Framework | Issued by Subkuz Media Networks Private Limited (CIN: U72900JH2020PTC014521)

Document #075 | Verified Master Version

One Public Record Across Web, Applications, Vendors, Advertising, Data Rights and Security Operations

1. Objective

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.

2. Required technology and data inventory

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

3. Controller and provider consistency

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.

4. Consent and cookie controls

  • Necessary technologies are limited to genuine security, delivery, session, preference and requested-service needs.
  • Optional analytics, advertising or personalisation are inactive until the required valid choice.
  • Reject Optional is as accessible as Accept Optional.
  • No optional category is preselected.
  • The choice persists and can be changed through a visible Cookie Settings control.
  • Third-party embeds remain blocked or privacy-protected until the relevant choice where required.
  • Consent records identify version, categories, time and withdrawal without collecting unnecessary identity data.
  • The live cookie inventory is generated from the actual implementation and manually verified.

5. Application permissions

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

6. App-store reconciliation

  • Developer or publisher identity matches the authorised public record.
  • Privacy labels match actual collection, purpose, linkage and tracking.
  • Support and privacy URLs resolve to current pages.
  • Account deletion route is available where accounts can be created.
  • Screenshots and descriptions do not promise inactive features, languages or city coverage.
  • Version notes do not create false claims of security or privacy certification.
  • Application data permissions notice reflects the current released version.

7. Forms and analytics separation

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.

8. Commercial systems

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.

9. Security baseline

  • Individual administrator accounts and multi-factor authentication.
  • Least privilege for editorial, commercial, form, analytics and infrastructure roles.
  • Rapid removal of departed or unnecessary accounts.
  • Supported software, documented patching and removal of unused extensions.
  • Encrypted transport and secure secret storage.
  • Backups separated from the primary environment and restoration tested.
  • Security logs protected from ordinary editing and reviewed for critical events.
  • Rate limiting, bot protection and form-abuse controls that do not block accessibility.
  • Content-security, framing, transport and referrer controls assessed against the live application.
  • Incident response covering readers, sources, applicants, complainants, clients and editorial continuity.

10. Vulnerability disclosure and security.txt

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.

11. Incident response

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

12. Accessibility and performance

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.

13. Reconciliation sign-off

  • Website and app data flows match public notices.
  • Vendor and SDK inventory is complete for the released versions.
  • Cookie and application choices work as described.
  • Account deletion and privacy routes operate end to end.
  • Commercial scripts and paid pages comply with consent and search rules.
  • Security contact, security.txt, backups and incident routing are tested.
  • Application-store disclosures and official support links are current.
  • No obsolete controller, address, email or policy remains in a cached template or application screen.
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