1. Scope

This policy applies to the Social space for statuses, profiles, conversations, community features, and connected business accounts.

2. Data we may process

The data involved depends on the features you use and the information you choose to provide.

• profile identity, active business account, and visibility settings
• statuses, comments, reactions, followers, reports, and conversations you send
• attachments you choose to upload, subject to the applicable limits and security checks
• the minimum technical data needed to deliver notifications and protect conversations

3. Sources and collection

Data may come from you, another member's action connected to your account, an authorized party in a service process, or your browser and device when a feature is used. We seek to explain the need when data is requested and do not request unrelated data without a reasonable purpose.

• You may provide data through forms, settings, Chat, uploads, email, support, or a service workflow.
• Technical data such as sessions, devices, times, and security signals may be created automatically to operate the service.
• Data from another party is processed only when connected to a function, access decision, report, or lawful obligation.

4. Why data is used

Data is used only for legitimate purposes connected to the service.

• display statuses to the audience you choose
• deliver conversations, notifications, and community features
• protect the integrity of Social, including moderation and report handling
• prevent spam, abuse, and unauthorized access

5. Visibility and sensitive data

Some visibility choices can be managed in product settings.

• A status is visible only under the public, followers, business-team, or private audience you select when publishing it.
• Chat messages and attachments are treated as private within the conversation; access may still be limited by membership, invitation status, and the visibility period.

6. Social data sources and activity

Social data comes from your profile, statuses, comments, reactions, follows, reports, Chat, group invitations, audience settings, device, and interactions. Some data is created by other members, such as when they mention your account, invite you, or interact with your status.

We use that information to show spaces and notifications connected to your account, enforce privacy, prevent abuse, and provide the functions you request.

• Public profile data is displayed according to account status and the applicable visibility choice.
• Interaction data may support unread counts, conversation ordering, and requests you make.
• Security data such as sessions, device signals, IP, and rate-limit signals is used narrowly to prevent attacks and abuse.

7. Status visibility and business context

A status may have a public, followers, business-team, or private audience. The server determines access using status state, follow relationship, business membership, and active context; a browser UI or visible URL does not change that decision. We may retain what is needed to apply visibility changes consistently.

When a status is made for a business account, the business identity, acting member, and relationship to the business may be stored so history, notifications, and audits are not confused with a personal account.

8. Messages, attachments, and reports

Chat content and attachments are processed to deliver messages, show history a user may see, synchronize receipts, unread state, replies, edits, deletions, and security features. Access is limited by session, membership, invitation status, visibility periods, history boundaries, and per-account deletion.

When a message is reported, the minimum snapshot needed for review may be stored with reporter identity, the reported user, time, and security metadata. A moderation snapshot is not sent to the public timeline and is not public data.

• File name, size, type, scan status, and attachment metadata may be processed without making private storage public.
• Message content is not used for conversation-based advertising.
• Deleting a message or conversation from your view does not always remove records needed for safety, audit, disputes, or legal obligations.

9. Notifications and devices

If you enable email, web, or Push notifications, we store the subscription or channel preference needed to deliver them to the correct session. Browser permission can be revoked on a device; that does not automatically erase activity records or conversation content.

We may retain technical data about browser, connection time, delivery failures, and session state to prevent cross-account delivery and remove invalid subscriptions. Capability endpoints and tokens are not put in ordinary logs.

10. Retention, controls, and privacy requests

Retention differs for public content, Chat history, attachments, moderation reports, audits, and security data. We delete, anonymize, or restrict data when its purpose ends unless there is a valid reason to keep it. Backups and incident snapshots may follow separate cycles.

You can use settings to change status audience, who may start a Chat, notifications, or account context. Access, correction, restriction, and deletion requests may require identity verification and exceptions for other members' data or records that must be retained.

11. Sharing

We do not sell personal data as a commodity. Data may be shared on a limited basis with:

• accounts or space members who are given access by your settings
• authorized moderators when a report or abuse investigation requires review
• infrastructure providers needed to deliver messages and store private media

12. Retention and security

Data is retained only as long as needed to operate the service, protect users, resolve disputes, or meet applicable obligations. It is then deleted, anonymized, or restricted as appropriate.

We use technical and organizational controls proportionate to risk. No digital transmission or storage can be guaranteed 100% secure, so users must also protect their accounts and devices.

13. Your requests

Subject to applicable law, you may request access, correction, restriction, or deletion of certain data. Some information may need to be retained for security, audit, service, or legal reasons. We will explain a decision where reasonably possible.

14. Cookies and similar technology

Cookies or similar technologies may be used for sessions, language preferences, security, and product operation. Disabling necessary cookies may prevent parts of the service from working.

15. Updates

This policy may be updated when the product, processing practices, or legal requirements change. The latest version is identified by the update date above; material changes may receive an additional notice through an appropriate channel.