DOC #072 03_DEVELOPER_IMPLEMENTATION

SUBKUZ FORMS, ROUTING, ACKNOWLEDGEMENT AND CASE MANAGEMENT SPECIFICATION

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

Document #072 | Verified Master Version

Operational Standard for Fourteen Public Submission Interfaces

1. Purpose and mandatory operating condition

The fourteen public forms convert policy commitments into working public processes. A form must not be published until its destination, primary owner, backup owner, acknowledgement, reference number, evidence storage, access control, response timer and closure record have been tested. A visible form that loses submissions or sends them to an unmonitored mailbox is a material governance defect.

2. Reference-number standard

Every accepted submission receives an immutable reference in the form PREFIX-YYYYMMDD-RANDOM, using the prefix in the routing table and a four-character uppercase alphanumeric random component generated by the server. Example: COR-20260807-7K2Q. The reference is generated only after secure storage succeeds. It is displayed on screen and sent through the acknowledgement channel. References must not reveal sequential complaint volume, personal identity, subject category or outcome.

3. Form routing matrix

Prefix Form Primary route Acknowledgement Key control
PRV Privacy Rights Request Privacy owner Privacy rights acknowledgement Identity verification where proportionate
GRV Grievance Submission India Grievance Officer or responsible complaints function 24-hour statutory acknowledgement where applicable Editorial, privacy, copyright or service classification
APL Editorial Appeal Appeal reviewer Appeal acknowledgement Eligibility and independence check
COR Correction, Clarification or Retraction Corrections desk Correction acknowledgement Exact claim, URL, evidence and urgency
DEL Account Closure and Deletion Privacy and account operations Deletion request acknowledgement Account identity and retention assessment
CPY Copyright Infringement Notice Copyright and legal Copyright notice acknowledgement Rights ownership and authority
LIC Content Licensing and Reuse Licensing and legal Licensing request acknowledgement Material, territory, duration, platform and commercial use
TIP Secure News Tip Secure editorial intake Risk-appropriate receipt only Source safety, public interest and evidence
CON Contributor Application Contributor programme Application receipt Identity, role, expertise, conflicts and privacy
ADV Advertising Enquiry Commercial compliance Commercial enquiry receipt Advertiser, client, product, claims, targeting and destination
PRP PR and Paid Publication Brand Studio and commercial publishing Submission receipt Payer, beneficiary, format, claims, rights and links
ACC Accessibility Issue Accessibility owner Accessibility report receipt Barrier, page, technology and alternative requested
SEC Security Vulnerability Security owner Security report receipt Asset, reproduction, impact and coordinated disclosure
LEG Corporate and Legal Contact Corporate or legal owner Official correspondence receipt Sender authority, subject, jurisdiction and deadline

4. Shared form controls

  • Clear title, purpose, governing policy and responsible entity.
  • Only fields necessary for the stated process. Optional fields are identified as optional.
  • Accessible labels, instructions, errors, focus order and confirmation.
  • Server-side validation in addition to client-side validation.
  • File-type, size, malware and extension controls for attachments.
  • No password, authentication code, private key or payment-card field.
  • Privacy notice explaining purpose, recipients, retention and rights.
  • Consent only where consent is the actual legal basis. Do not use consent to waive editorial, legal or statutory rights.
  • Submission timestamp in UTC and the user-facing local time where relevant.
  • Language, edition and accessibility preference where necessary for routing.
  • A human-readable acknowledgement and a durable server record.

5. Attachment controls

Control Requirement
Allowed formats PDF, DOCX, TXT, CSV, JPG, PNG, MP3, MP4 and another format expressly required by the form
Default maximum 25 MB per file and 100 MB total unless the secure-tip or security route provides a separate approved transfer method
File-name handling Replace unsafe path characters and store under a generated internal identifier
Malware screening Quarantine before delivery to the case owner
Metadata Do not remove evidence metadata automatically from original newsroom or security submissions; create a protected original and a working copy
Public display Never publish an attachment automatically
Rejected files Explain the reason and provide a safe alternative route

6. Urgency classification

Level Meaning Operational action
Critical Immediate threat to life, active security compromise, exposed credentials or time-limited voting misinformation Alert primary and backup immediately; do not promise emergency-service intervention
High Serious reputational harm, child safety, source risk, active legal deadline, material privacy exposure or rapidly spreading false information Priority human review and documented escalation
Standard Ordinary grievance, correction, privacy, licensing, contributor, advertising or contact matter Normal queue and applicable published timeframe
Low or informational General enquiry, suggestion or incomplete non-urgent submission Route without displacing statutory or safety work

7. Acknowledgement content

The acknowledgement confirms receipt, reference number, date and time, form type, responsible function, expected next step, any published acknowledgement target, the need to retain the reference and an instruction not to resend the same matter repeatedly. It does not state that the allegation is true, the requested remedy will be granted, the work will be published, the applicant will be appointed, a licence exists or a security reward will be paid.

8. Model acknowledgement

Subkuz has received your submission. Reference: [case reference]. The responsible function will assess the information under the applicable public policy. This acknowledgement confirms receipt only and does not determine the facts, outcome, publication, appointment, licence, payment or remedy. Please retain the reference and use it in further correspondence. Do not send passwords, authentication codes, private keys or unnecessary sensitive information.

9. Timers and service levels

Process Public target Timer start Pause or extension rule
India statutory grievance Acknowledgement within 24 hours; publisher decision within the applicable 15-day period Successful receipt by the designated route Only as permitted by applicable law; missing essential information is requested promptly
Correction request Prompt acknowledgement and proportionate review Successful receipt Urgency rises where the error can cause immediate harm
Privacy request Within the period required by applicable law Verified or sufficiently identifiable request Valid extension and identity clarification are recorded
Accessibility report Acknowledgement target in the Accessibility Statement Successful receipt Provide an interim accessible alternative where repair needs more time
Security report Acknowledgement and initial triage targets in the Security policy Successful receipt Active exploitation receives immediate escalation
Commercial, contributor and licensing Operational target set internally Successful receipt No public guarantee unless the governing page states one

10. Case states

  • Received
  • Acknowledged
  • Identity or authority check
  • Triage
  • Assigned
  • Evidence requested
  • Under review
  • Response or right of reply pending
  • Decision drafted
  • Approved
  • Remedy in progress
  • Closed
  • Appealed
  • Reopened
  • Rejected as spam or unsafe

11. Access and confidentiality

Cases are accessible only to the people required for routing, review, decision, security, legal compliance and audit. Advertisers and commercial personnel do not receive correction, grievance, source or security case data merely because the matter concerns a client. Confidential source identity is separated from ordinary case content. Security vulnerabilities and whistleblower evidence are stored outside routine customer-relationship or marketing systems where those systems cannot provide the required protection.

12. Misrouting and duplicates

A clearly identifiable submission sent through the wrong Subkuz route is forwarded internally without requiring the person to begin again, where safe and lawful. The original receipt time is preserved. Duplicate submissions are linked to one case and do not receive multiple outcomes. A mass campaign may be consolidated for administration while preserving any individual evidence or rights that require separate treatment.

13. Closure record

  • Reference, form, receipt and acknowledgement timestamps.
  • Responsible owner and reviewers.
  • Issue classification and jurisdiction.
  • Evidence considered and source restrictions.
  • Decision and remedy.
  • Public correction, notice or register entry where applicable.
  • Appeal eligibility and deadline.
  • Retention and deletion category.
  • Any process failure or required preventive action.

14. Form acceptance tests

  • Successful submission with and without optional fields.
  • Required-field and invalid-format errors announced accessibly.
  • Safe attachment accepted and malicious or disallowed attachment rejected.
  • Reference created only after storage succeeds.
  • Acknowledgement received and matches the displayed reference.
  • Primary and backup routes receive the case.
  • No sensitive content appears in analytics, advertising pixels or URL query strings.
  • Noindex is present and the page remains crawlable.
  • Mobile, keyboard and screen-reader completion succeeds.
  • Rate limiting blocks abuse without preventing legitimate repeated evidence submission.
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