DOC #026 01_PUBLIC_WEBSITE_DOCUMENTS

SUBKUZ APPLICATION DATA AND PERMISSIONS NOTICE

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

Document #026 | Verified Master Version

Public Information for Android, iOS, Mobile Permissions, Software Components and Account Controls

POLICY INFORMATION POLICY INFORMATION
Issued by Subkuz Media Networks Private Limited
Corporate Identification Number CIN U72900JH2020PTC014521
Effective date 6 August 2026
Last reviewed 7 August 2026
Previous legal name during statutory disclosure period Subkuz Media Networks Private Limited

1. Purpose and scope

This Notice explains the personal data, device information, permissions and software components that may be involved when a person installs or uses an authorised Subkuz mobile application. It supplements the Privacy and Data Protection Policy, Cookie and Similar Technologies Notice and the platform disclosure shown on the relevant application-store page. The application build, in-app explanations, privacy manifest, permissions, third-party software and store declarations must remain materially consistent.

A permission or data category is not used merely because it is described in this Notice. The current Application Data Register identifies the permissions and data flows present in the active Android and iOS builds. A permission must not be added to a release until the feature, purpose, public notice, legal basis, security review and platform disclosure are complete.

2. Responsible entities and technology roles

Subkuz Media Networks Private Limited is the principal publisher and controller or Data Fiduciary for application services it operates directly. Subkuz Media Networks Pvt Ltd ( SMN ) may own, license, develop, host, maintain or support the application and associated infrastructure and ordinarily acts as a technology provider or processor when it handles personal data on documented Subkuz instructions. A local Subkuz entity may become responsible for a regional application or service only after its legal role and contact information are published in the Controller and Contact Directory.

Application-store operators, device manufacturers, telecommunications providers and third-party services may process information independently under their own terms. Their independent processing is not attributed automatically to Subkuz merely because the application is distributed through a platform.

3. General reading without an account

A person can ordinarily read general publicly available journalism in the application without creating an account or providing a name, telephone number, email address or precise location. Limited technical data may be processed to deliver content, maintain security, identify the correct application version, remember a selected language or city, diagnose faults and protect the service from abuse. This may include an internet protocol address, operating-system version, application version, device characteristics, request time, approximate network region, security events and crash or performance information where enabled lawfully.

General reading must not require access to contacts, call logs, text messages, calendar, microphone, camera, photo library or precise location. Such access may be requested only for a current optional feature that the person chooses to use and only to the extent necessary for that feature.

4. Current-build and store-disclosure standard

Google Play and the Apple App Store require developers to describe application data practices, including data handled through third-party software. Subkuz is responsible for ensuring that its declarations are complete and accurate. The absence of a category from a store label must not be used to conceal data transmitted by a library, software-development kit or server request, and a category must not be declared merely because a template assumes that all applications collect it.

For every public release, Subkuz reconciles the application code, requested permissions, third-party components, privacy manifest, network traffic, account functions, deletion route, this Notice and the current store declarations. A testing build and production build may differ, but the disclosure shown to users matches the build made available to them.

5. Essential application and device information

The application may process limited information necessary to install, open, update, secure and deliver the service. Depending upon the active build, this may include application version, operating-system version, device model category, language, selected edition, network status, notification status, security values, session information, request logs and technical errors. The data is used for content delivery, compatibility, security, fraud prevention, fault diagnosis and continuity rather than for unrelated behavioural profiling.

Device identifiers are not used as a substitute for an undisclosed civil identity. An identifier may be used where necessary for security, fraud prevention, a requested notification, consent management or another defined application function. Any use of an advertising identifier requires an approved purpose, platform compliance, an accurate store declaration and the applicable consent or opt-out.

6. Accounts and authentication

Where the application offers account creation, Subkuz may process a name or account identifier, email address, telephone number, authentication credential, selected city, country, postcode, language, communication choices, account status and security records. Information is limited to the service requested. The application does not obtain unrelated device contacts, messages or photographs merely because an account is created.

Authentication may be provided directly or through an approved third-party login service. Before a third-party sign-in is used, the application must explain the information exchanged and the responsible provider. Account security may require verification, multi-factor authentication, device confirmation or another proportionate safeguard.

7. Location

Subkuz is designed to deliver hyperlocal journalism through a manually selected city, country, postcode, edition or approximate network-derived region. Precise global-positioning coordinates are not required for general reading. Where a current optional feature genuinely requires device location, the application must explain the purpose immediately before the operating-system prompt, request only the level of accuracy and duration necessary, and provide a reasonable manual alternative where the feature can operate without precise location.

Location is not used to infer religion, caste, political allegiance, health, immigration status or another sensitive characteristic merely because a person was present in a particular area. Denying or withdrawing location permission must not prevent general journalism from being read.

8. Notifications

The application may request permission to send notifications for breaking news, selected editions, account security, service information or another user-selected purpose. A notification token may be processed to deliver the message. Optional editorial and promotional alerts are controlled separately from essential security or account notices where the platform and service permit.

A person may disable notifications through the application or device settings. Notification interaction is not used to create an unrestricted profile of the person. Limited delivery and engagement information may be used to ensure that the requested alert functions correctly and, where optional measurement requires consent, only after the required choice.

9. Camera, photographs, video and files

Camera, photograph, video or file access may be requested only when a person chooses to submit a news tip, upload evidence, change an authorised profile image, scan a document or use another current feature that requires the material. The application uses a system file picker or limited-access method wherever that method can achieve the purpose without granting broad library access. General reading does not require media access.

Material submitted to a newsroom remains subject to verification, source protection, copyright, privacy and editorial review. Granting device access does not create an entitlement to publication and does not authorise Subkuz to browse unrelated files.

10. Microphone and audio

Microphone access may be requested only for a current user-initiated function such as recording or submitting audio, participating in an authorised interview or using another feature that cannot operate without sound input. The application must display the operating-system indicator and respect withdrawal. General reading and ordinary account use do not require microphone access.

Audio is processed for the stated feature and is not used for continuous background listening, advertising profiling or unrelated voice identification. Biometric voice analysis requires a separate lawful purpose and enhanced review.

11. Contacts, communications and other sensitive permissions

General Subkuz use does not require access to a device address book, call log, text messages, calendar, health records, nearby devices or other sensitive system data. Any feature requiring such access is introduced only after a necessity assessment, platform approval where required, prominent in-app disclosure, appropriate consent, privacy review and an update to the Application Data Register. A person is not asked to provide access merely to improve growth, invitations or advertising convenience.

12. Diagnostics, crash reporting and security

The application may process crash, error, performance, network and security information to maintain reliability and protect the service. Diagnostic information is minimised and does not include article content, private messages, source material or full account details unless the information is indispensable to investigate a specific fault and is protected appropriately.

A third-party diagnostic component is not treated as harmless merely because it is widely used. Its data collection, retention, recipients, international processing and platform disclosure must be assessed before deployment. Optional product analytics remains separate from security and crash processing.

13. Third-party software and privacy manifests

An application may include third-party software-development kits for functions such as notifications, security, authentication, payments, media playback, accessibility, diagnostics or consent management. Subkuz remains responsible for the data transmitted by code included in its application. Each component must have an identified purpose, current version, security assessment, contract, data description and removal or replacement plan.

Where the platform requires a privacy manifest, signature or declaration of required-reason application programming interfaces, the current release must include the required information. A vendor statement is evidence for review but does not replace Subkuz verification of the actual application behaviour.

14. Advertising and measurement in applications

If the application displays advertising, Subkuz favours contextual and hyperlocal delivery based upon the current content, selected language, manually selected city, country, approximate region and other lawful non-sensitive signals. Advertising identifiers, cross-application tracking and optional campaign measurement are not used unless an approved service purpose, accurate store disclosure and the applicable consent or opt-out have been implemented.

Subkuz does not provide advertisers with a list identifying individual readers merely because they viewed a particular article. Children are not behaviourally profiled for advertising or political persuasion.

15. Account deletion and data requests

Where an application allows account creation, it must also provide a clear in-application route to request account deletion and an accessible web route that remains available after the application has been removed from the device. The request page must identify the application or developer, explain any necessary steps and distinguish account deletion from deletion of published journalism, legal records, fraud-prevention information and data that must be retained lawfully.

Privacy rights, correction, consent withdrawal, account closure and other requests may be submitted through the Subkuz Privacy Rights and Data Request Page. Deleting the application from a device does not itself delete an account or server records unless the application expressly provides that result.

16. Children and age-appropriate safeguards

The application is not an open social platform for children to publish content. Account and interactive features may carry age restrictions or require parental or guardian authorisation according to the jurisdiction and feature. Subkuz does not knowingly use children's application data for behavioural advertising, political targeting or hidden psychological profiling. A child-related feature requires age-appropriate information, data minimisation and appropriate safeguarding.

17. Managing permissions and withdrawing choices

A person may manage permissions through device settings and may manage optional cookies or software technologies through the applicable in-app privacy controls. Withdrawing a permission stops future access controlled by the operating system, but information already supplied may be retained where a lawful journalistic, contractual, security or legal purpose continues. The application must not repeatedly pressure a person to restore a permission that is not necessary for the requested feature.

Where a permission is essential only to a specific feature, the rest of the application remains available whenever reasonably possible.

18. Security, updates and contact

Subkuz applies security safeguards appropriate to the data and application risk, including secure transmission, access control, credential protection, software updates, vulnerability management and incident response. No application can be guaranteed free from every defect or attack, but a known material vulnerability or privacy inconsistency must be addressed without avoidable delay.

This Notice is updated when a material permission, data category, software component, account function or platform requirement changes. Questions and privacy requests may be submitted to [email protected]. India-related publisher and privacy grievances may also be submitted to [email protected].