a social media

Privacy Policy

How a handles identities, network traffic, local data, external services, and private safety reports.

Last updated October 21, 2026Version 1.2

1. Scope

This Privacy Policy applies to a social media ("a") and its public website. a is a client for decentralized social networks operated by Logic Omnipresence. It does not operate the underlying networks or a centralized social service.

Your device normally communicates directly with the independent network services you choose. Those third parties have their own policies and may receive network information independently of Logic Omnipresence.

2. Data that stays on your device

a stores the following data locally when a feature requires it:

  • social identities and the active identity selection;
  • private signing credentials protected by the iOS Keychain;
  • network-provider choices and connection preferences;
  • cached public content, profiles, reactions, and link previews;
  • decrypted direct-message content and conversation state;
  • My Verse watchers, muted users, hidden events, and display choices.

Logic does not receive this local data merely because you use the app. Do not send a private identity credential or decrypted direct message to support or include it in a report.

3. Direct network traffic

When you use network-backed features, your device communicates with the providers you enabled. Depending on the supported protocol, a provider may receive your public identity, content identifiers, subscription filters, signed public content, encrypted message envelopes, IP address, and other ordinary network metadata. Provider storage, retention, access, and moderation are controlled by that provider, not Logic.

Public network content is designed for distribution and may be copied by providers, clients, archives, and other users. Removing local data or publishing a deletion request cannot guarantee deletion of every copy.

4. Identity credentials and private messages

Private identity credentials are generated or imported on your device and stored through iOS Keychain controls. a does not provide an account-recovery service and cannot recover a lost credential.

a uses the private-messaging mechanisms of each supported protocol. Message content is encrypted before transmission and decrypted on your device. Network providers still process encrypted envelopes and associated delivery metadata. Recipients may retain or share messages after receiving them.

Official safety notices use Logic's authenticated HTTP inbox. The app checks it while active and stores received notices locally. Logic and its Cloudflare infrastructure store recipient public keys, encrypted envelopes, and the underlying moderation decision, notice text and delivery records. The principal safety account signs notices on its device; private identity credentials are never sent to the service. This inbox is specific to a and is separate from the independent Nostr relays you select.

When you publish profile metadata or relay lists in a, the app also sends the same signed public event to Logic's identity-recovery service. Logic and its Cloudflare infrastructure retain the current profile event (including the username, description, and avatar URL you supplied) and the current NIP-65 and NIP-17 relay-list events for your public key. This lets a restore on another device discover those public settings without your private key. The service verifies event signatures, stores no private credential, and is not a general mirror of your posts or relay traffic. These events can be retrieved by public key and may also remain available from independent relays after Logic's copy is changed or deleted.

5. External media, links, and verification

Opening media, a link preview, a website, or an identity-verification domain sends a request from your device to that external host. The host may receive your IP address, request headers, and related network metadata. Regular attachments use your media-safety preference. Content marked sensitive through a supported protocol is not downloaded or revealed in the App Store build.

6. Private safety reports to Logic

When you choose Report to a, Logic receives your public Nostr key, the target content identifier or public identity, the selected reason, optional context you write, the signed report, available signed evidence and relay hints, a report receipt, and timestamps needed to review and resolve the report. Email reports include the sender email address and the information included in the message, but do not require a Logic account. Appeals include the appellant's public key and explanation. Private keys are never transmitted.

Cloudflare provides the website, report endpoint, and report storage and processes ordinary network information, including IP addresses, to deliver and protect those services. Logic does not store reporter IP addresses in the report table and does not use report traffic for analytics or advertising.

Open reports are retained while they are reviewed. Resolved reports have a 90-day retention target. Evidence supporting an active restriction, appeals, and moderation audit records may be retained while needed to enforce and review the decision, meet legal obligations, or resolve an active dispute.

7. Network reports and private reports are different

A supported protocol may allow a signed report to be published to selected network providers. That report may be distributed and retained by third parties. Public reports submitted in a are also submitted to Logic's safety team, and the app shows whether that delivery succeeded. The separate Report to a action delivers a signed report privately without publishing it to relays.

8. Website data

The public website is static. It does not use analytics, advertising, tracking pixels, or non-essential cookies. Standard Cloudflare security and delivery logs may still be processed under Cloudflare's role as infrastructure provider.

9. Retention and deletion

Cached data remains on your device until the app evicts it or you clear it. Identity-scoped local data remains until you remove that identity data. Keychain behavior may differ from ordinary app storage, including across an app reinstall, as described by iOS.

Network-hosted data follows each provider's policy. a can publish a best-effort deletion request when a supported protocol permits it, but neither a nor Logic can require every provider or recipient to delete a copy.

10. Your privacy choices

  • Choose, disable, or remove independent network providers.
  • Keep regular attachments in Ask First mode.
  • Block or unblock a public identity for the active identity.
  • Clear disposable cached content without removing saved keys.
  • Remove a key from the device or delete its related local identity data.
  • Request best-effort network deletion where the protocol permits it.
  • Ask Logic to delete the current identity-recovery copy associated with your public key.

For a privacy request concerning data held by Logic, contact global@logicomnipresence.com. Include a report receipt when the request concerns a safety report. Never include a private identity credential.

11. Security

a uses the iOS Keychain and system owner authentication for protected key operations. Private credentials are not synchronized by a Logic service. No system can eliminate all risk: protect your device, keep independent backups where appropriate, verify destinations, and treat anyone requesting your private credential as untrusted.

Report a security issue privately to global@logicomnipresence.com. Do not publish an unpatched vulnerability or include unrelated personal data.

12. Age and children

The first App Store release is intended only for people aged 18 or older. a is not directed to children, and Logic does not knowingly operate accounts for children through this product.

13. Changes and contact

We will update this page when the shipped data flow changes. Material changes will receive a new date and version. Questions may be sent to global@logicomnipresence.com.