News Share · LaunchAlike Studio
Privacy Policy
How News Share handles personal information, who receives it, and the choices and deletion routes available to you.
On this page
1. Scope and responsible operator
This Privacy Policy applies to the News Share Android app and News Share support and account-deletion requests. The responsible operator is BK Sekulane (Brighton Sekulane), based in South Africa, using the LaunchAlike Studio app brand. Contact bk.sekulane.dev@gmail.com for privacy requests.
News Share shares links and discussion; linked publishers, sign-in providers, advertising providers, and your email service also have their own privacy notices. This policy explains the app's processing and does not replace those providers' notices or the website operator's notice for general website hosting and visits.
Visiting a public support or deletion page can generate ordinary hosting access and security records, such as the requested page, IP address, browser information, and time. This is separate from the deletion form's entries, which stay in your tab until you choose to send the prepared email. Website hosting and email providers process those respective records for delivery, security, and handling your request.
2. Accounts, sign-in, and public aliases
Firebase Authentication processes your account identifier, chosen sign-in provider, authentication credentials or tokens, and related technical security information. Depending on the method you choose, this can include an email address, password authentication data, phone number, and information returned by Google sign-in such as an email address, provider name, or profile image. Authentication is handled by Firebase and the chosen provider; support does not need your password or verification codes.
If you use phone sign-in, your phone number is sent to and stored by Google for authentication and spam and abuse prevention across Google services, including Firebase. Choose another offered sign-in method if you do not want to use phone verification. SMS and mobile-network charges may apply.
We store a public profile with your chosen display name, unique username, account ID, account type, profile status, and relevant timestamps, including the accepted Terms version. A display name need not be your legal name. Your sign-in email or phone number is not deliberately published as your public profile. An anonymous or guest account still has a persistent technical account ID and can be associated with its activity; it is not anonymous to the service.
3. Content, groups, and interaction data
We process article links and previews, titles, summaries, image URLs, categories, comments, likes, author or actor IDs and aliases, and timestamps. Group data includes names, descriptions, selected icons and colours, public or private status, owner and member IDs, invitation codes, membership and join requests, and moderation actions. We also process notification categories, scope access, read state, and the notification events needed for the service.
Reports can include the reporting account, reported content or account identifiers, reasons, relevant content excerpts, and review information. Support correspondence includes the information you choose to send and the details needed to respond or verify a request. Do not submit passwords, verification codes, government identity documents, or unrelated sensitive information unless a lawful, necessary verification process has first been explained.
4. Who can see your content
Public posts, public group information, aliases, and associated public activity can be visible to other users and processed by our public-search service. Public posting is not confidential. Private-group posts are restricted through app access controls to authorised group participants and service operators and providers that need access to operate or protect the service. Private-group posts are not intended for the public Algolia news index.
Group owners can view and act on membership and join requests and moderate group content. Private groups are not end-to-end encrypted. Members can capture or redistribute information, and removal from a group cannot recall copies they already received. Blocking primarily filters content in your own app experience; it is not a guarantee of two-way invisibility or deletion of public material.
Deleting content cannot remove copies or screenshots independently kept by others, material quoted in someone else's post, or the original publisher's article. Contact us if another user's content improperly exposes your personal information.
5. On-device storage, article visits, and offline copies
The app uses local databases, preferences, and caches for saved reading entries, available offline article copies, shared-item history, local like state, blocked-account selections, session and profile caches, notification state, consent choices, and temporary ad-pause settings. Read Later and Catch Up are primarily device-local and are not promised to synchronise across devices.
Preparing link previews, retrieving images, saving offline copies, or opening an article can contact the original site and other services used by that site. They can receive the requested URL, IP address, browser or device information, and applicable cookies. Background preview and offline-article requests do not copy your WebView cookies, although a publisher can set cookies during those requests. The in-app browser uses Android WebView; live publisher pages may run their own scripts and storage under their own policies. The app's generated offline reading view does not run publisher scripts. External browsers and apps manage their own data.
Saved copies can be incomplete or unavailable, including when a publisher blocks automated requests or requires browser verification. News Share does not bypass those checks to prepare previews or offline copies; a saved entry may contain only the available title and summary. An offline copy can reload the live publisher page when connectivity returns, making a new network request. Optional downloaded files and browser caches may remain on the device until removed through the relevant device or app controls. App-managed Android backup is disabled; this does not control a device manufacturer's independent backup tools or copies you create.
6. Notifications and device identifiers
Firebase Cloud Messaging processes app-installation identifiers, messaging registration tokens, and topic subscriptions to deliver notifications. News Share uses topics rather than maintaining its own per-user token directory in Firestore. The messaging provider still processes device and token information; topic-based delivery does not mean no personal data is processed.
Category subscriptions and account or group state determine which notifications are relevant. Private-group push messages are designed to be generic, with protected details retrieved through the app's access controls. Notification delivery and displayed lock-screen information also depend on Android, your device settings, and connectivity. You can change categories in the app and turn notification permission off in Android settings.
7. Advertising, analytics, and crash reporting
The app uses Google AdMob and the Google User Messaging Platform for advertising and applicable consent and privacy-choice messages. Depending on consent, device settings, ad format, and provider behaviour, advertising services can process IP addresses and approximate location inferred from them, advertising and app-set identifiers, device and app information, ad impressions and interactions, and performance or fraud-prevention information. News Share does not request precise GPS location permission.
Firebase Analytics is included for app usage and advertising measurement, including ad impression-revenue events such as placement, ad-source information, value, and currency. Firebase Crashlytics is included for crash reports, diagnostic traces, app or device details, and installation-related identifiers. These SDKs can collect automatically in the current app configuration; ad-consent controls and rewarded ad pauses are not a general analytics or crash-reporting opt-out.
When required and available, advertising privacy choices are offered through the consent flow and Settings. Android advertising-ID and privacy settings provide additional controls. Declining personalised advertising does not necessarily prevent limited advertising, essential fraud prevention, or all provider processing. The available options depend on your region and device.
Completing an eligible optional rewarded ad can pause ads managed by News Share for 45 minutes. That pause does not erase earlier records, withdraw consent, stop analytics or crash reporting, or suppress ads on publisher websites. Do not confuse ad suppression with a privacy request.
8. Purposes and grounds for processing
We use information to authenticate and manage accounts; display profiles and shared content to the intended audience; provide feeds, public search, comments, groups, offline reading and notifications; deliver and measure advertising; investigate reports and abuse; diagnose faults; answer support and rights requests; and meet applicable legal obligations.
Depending on the activity and applicable law, processing is necessary to provide the service you request or perform our agreement, to comply with legal duties, for legitimate operational and security interests balanced against your rights, or on consent where required. We do not treat use of the app as consent for every optional purpose. Where processing is based on consent, you may withdraw that consent through the available controls or by contacting us; withdrawal does not undo lawful earlier processing.
Account identifiers and necessary service records are required for account-based features. Optional notification permission and choices are not required simply to read available app content. If you withhold data needed for a particular sign-in or feature, that feature may not work.
9. Service providers and other disclosures
We use Google Firebase and Google Cloud for authentication, databases, server-side functions, push messaging, analytics, crash reporting, and related hosting and operations. Google AdMob and its applicable advertising partners supply and measure ads. Algolia processes public news records and search requests when public search is enabled. Our support mailbox and your email provider process correspondence you send.
These providers receive the information necessary for their roles. Advertising providers may also process information under their own policies. We do not offer your private sign-in email or phone number as public profile fields or sell those account contact details as a contact list. Advertising-related disclosures may have specific legal classifications, including sharing under some laws; the advertising choices above remain relevant.
We may disclose relevant information to comply with law or valid legal process, protect rights and safety, prevent or investigate abuse, or resolve a dispute, subject to applicable law. If operation of the service is transferred, personal information may transfer with it under appropriate protections and notice where required.
Provider information: Firebase privacy and security, Google Privacy Policy, Google advertising information, and Algolia Privacy Policy.
10. Retention and deletion timing
Active account, profile, content, group, membership, preference, and notification records remain while needed to provide their functions, unless removed through the relevant content, group, or account-deletion process. They do not all have a fixed automatic expiry. Device-local reading entries and copies remain until cleared, removed, or replaced through applicable local controls.
Confirmed in-app account deletion starts server-side processing at that time; completion depends on the amount of associated data and service availability. A request made outside the app is processed after it reaches support and ownership is reasonably verified, without undue delay and within applicable legal time limits. Contact support for progress or if a request appears incomplete; an error or an unsent draft is not confirmation of deletion.
Limited reports about an account, abuse or security evidence, necessary support correspondence, and legal or dispute records may be retained after deletion only while needed for the relevant investigation, legal obligation, claim, or request handling. They are not retained to continue ordinary public participation by a deleted account. The applicable period depends on that specific purpose and any legal requirement rather than a single period for all records; you may ask us about an applicable exception.
Provider diagnostic, security, advertising and analytics records, technical caches, and any provider-managed backups follow the relevant service's retention and deletion processes, not an instantaneous device-wide erase. For example, Firebase documents that Authentication deletion can take up to 180 days to remove associated authentication data from live and backup systems, while Crashlytics keeps crash data and related identifiers for 90 days before starting removal. These provider periods do not mean an account remains available for normal sign-in after successful deletion. Analytics retention depends on the configured property and data type. Aggregated information that no longer identifies you may be kept for statistics. See the provider notices above for details.
11. Delete an account or request data removal
In the app: open Settings, select Delete account, type DELETE, and confirm. This is different from signing out, clearing cache, or uninstalling. The server process removes the Firebase Authentication account, public profile and username reservation, your posts and associated post interactions, your comments and recorded likes, memberships and join requests, category subscriptions and account-specific notification state or events, and reports you submitted. It also deletes groups you own and their associated group posts and records, including other members' posts in those groups. Relevant public-search removals follow the index synchronisation process.
Outside the app: visit https://launchalike.co.za/apps/newsshare/account-deletion. Enter a contact email and, if known, your account ID or username. The form prepares an email to bk.sekulane.dev@gmail.com; you must open your email app and send it, or send the prepared text yourself. The page does not upload or save the form entries or submit the deletion request automatically. Your email provider processes the email you send. No app installation or sign-in is required to contact us.
You may instead email support directly with the subject News Share Account Deletion. We may ask for proportionate, non-secret information to verify that the account is yours before removing it. Do not send a password, sign-in link, or verification code. Verification can be difficult for an anonymous account if its device credentials are lost. If verification is not possible, we will explain what information or alternative process is needed rather than delete someone else's account.
Successful in-app deletion also clears the app's current-device profile cache, saved reading entries and saved copies in that local database, shared history, local like and block records, notification badges, WebView cookies and website storage. It does not promise to erase every downloaded file, all browser or image caches, data on another device, independent screenshots, third-party publisher data, or provider records subject to the retention section. Remove remaining local files or app data using the relevant device controls.
Deleting a News Share account does not delete your Google account or other provider accounts, withdraw information from an original publisher, or automatically remove another person's independent copy. Reports about you and limited legal or security records may remain for the purposes in the retention section. Analytics and advertising records are not necessarily indexed by your News Share account ID and are not all automatically removed by the account-deletion callable. Contact support for a broader personal-data request; where records can be identified and applicable law requires it, we will arrange relevant provider deletion or explain the lawful limitation.
To request access, correction, or removal of particular personal data without closing the entire account, contact support and identify the data and requested action. We will explain any feature impact or lawful retention exception. Completed account deletion is irreversible; keep any material you are lawfully entitled to retain before confirming.
12. Security and international processing
We use account authentication, access-control rules, server-side validation, and restricted administration to protect information. Connections to our backend use encrypted transport. These measures reduce risk but do not guarantee that any service, device, or private group is completely secure. Third-party websites may have different security practices.
Our providers operate internationally, and information may be processed or stored outside South Africa or your country. Transfers are subject to applicable law and the providers' relevant contractual and technical safeguards. We do not promise exclusively South African storage. Contact us for information about the safeguards applicable to a particular request. Where a security incident requires notice under applicable law, we will follow those obligations.
13. Your controls and privacy rights
You can edit your public alias, remove content using available controls, leave groups, choose notification categories, disable Android notification permission, manage available advertising privacy choices, use Android advertising-ID controls, clear local app data, sign out, and request account or data deletion. Some actions affect only the current device, and clearing local data does not by itself delete your online account.
Depending on applicable law, including South Africa's Protection of Personal Information Act (POPIA), you may request confirmation or access to personal information, correction, deletion, objection to or restriction of certain processing, withdrawal of consent, and other applicable rights. Email support with your request. We may verify your identity proportionately, explain any lawful refusal or limits, and respond within the applicable legal period. We will not ask you to email passwords or verification codes.
You may complain to a competent data-protection authority. In South Africa, information and complaint routes are available from the Information Regulator. Contacting us first can help resolve a concern but does not remove your right to approach a regulator.
14. Children and sensitive information
News Share is intended for teens aged 13 and over and adults, not children under 13. Users must also meet any higher applicable legal and store age requirements and have parent or guardian authorisation where required and legally permitted. We do not seek personal information from children under the applicable minimum age or unnecessary sensitive personal details. Teen users' information is processed for the activities described in this policy, subject to applicable protections for minors. A store content rating is not age verification or a guarantee that every user-submitted link is suitable for every teen.
Do not post children's private details, sensitive identity or health information, or non-consensual personal data. If you believe a child has provided information unlawfully, or content exposes a child's safety or privacy, report it in the app or contact support so that we can investigate and take appropriate action.
15. Updates and contact
This policy was last updated on 22 October 2026. The app displays its bundled document revision, and current website text is available at https://launchalike.co.za/apps/newsshare/privacy-policy. Older installed app versions may retain earlier bundled text. We will publish revisions and give additional notice or obtain consent where legally required for material processing changes. A policy update does not itself authorise incompatible new processing.
Privacy and account requests: BK Sekulane (Brighton Sekulane), LaunchAlike Studio, South Africa. Email bk.sekulane.dev@gmail.com. Account-deletion request page: News Share account deletion.