Privacy, without euphemisms.

This policy covers the Newsova iOS application, account API, optional private chat and foreground calling services, and the Newsova website.

Privacy questions can be sent to hello@newsova.site. The legal entity acting as data controller and its postal address must be inserted and verified before this document is published.

You do not need a Newsova account to read news. Edition, language, category, saved-story, and read-state preferences are stored on the device.

The app requests RSS or Atom feeds and, when needed, publisher article pages and images directly. Publishers and their infrastructure may receive ordinary network data such as an IP address, request time, and user-agent information under their own policies. Full articles open from the original publisher inside an in-app browser.

If you choose private chat, Newsova processes account contact details, user and session identifiers, username, password hash, relationship and block state, generic push-device binding, call history, and abuse-report state. Passwords and PINs are not stored in plaintext; the device-local PIN is separate from the account password.

Messages and attachments use Matrix end-to-end encryption. Encryption protects content in transit and on the Matrix service, but participants can still capture, export, or retain content on their devices. Newsova does not promise deletion of copies it cannot control.

Foreground audio and video calls use LiveKit and WebRTC and require camera or microphone access only after the user starts or answers a call. Apple Push Notification service delivers generic private-activity notifications; private payloads must not contain sender, message, attachment, or room details.

Newsova also relies on Apple platform services, publisher infrastructure, Matrix/Synapse, LiveKit, email-delivery infrastructure, and hosting providers. The production subprocessor list, locations, and transfer safeguards require legal and deployment verification before publication.

Blocking and reporting are separate. A report normally contains a category and the reporter’s own short explanation. Newsova does not silently decrypt conversation content for moderation.

A selected message may be attached only after the reporter turns on evidence sharing and confirms a second disclosure prompt. Approved evidence is encrypted before database storage and kept in a restricted quarantine. Attachment evidence is not enabled until scanning and bounded retrieval are operational.

The implementation can delete a Newsova account, sessions, push bindings, relationship state, and controlled server records. Delivered Matrix content and external screenshots, exports, or backups may remain outside Newsova’s control and must be explained in the final deletion notice.

Moderation engineering defaults are 90 days for a case and 30 days for explicitly selected evidence, but these are not approved legal retention periods. Final retention tables, legal bases, regional privacy rights, request-verification steps, complaint authority details, and response timelines must be approved before launch.

Newsova uses bounded network requests, encrypted transport, secure device storage, generic notifications, access controls, and audit records designed not to contain message bodies or secret identifiers. No security measure can eliminate every risk.

Material changes will be dated and presented through the app or website as required. The publication checklist identifies the controller, legal basis, retention schedule, subprocessors, regions, and effective date.