Privacy Policy
Effective August 29, 2026 · Desk V1
DigiSocial Desk (the “Service”) is operated by DigiMass AI, LLC (“DigiMass,” “we,” “us”). This policy describes the data handling available in the current Desk V1 workflow. It does not promise features that are not enabled in this version.
1. Who We Are
DigiMass AI, LLC is a U.S.-based business. For privacy questions or requests, contact privacy@digimass.cloud.
2. Data We Handle in Desk V1
Account and workspace data
We use your authentication identifier and email address to provide sign-in. The Service also stores the selected workspace for your session and workspace role metadata needed to apply access controls.
Workflow data
Authorized workspace users may create or view briefs, package-review records, draft posts, sandbox dispatch intents, schedule-template guidance, and limited Brand registry metadata. The exact fields available depend on the workspace role and the relevant workflow.
Connected social accounts
An authorized workspace owner or operator may connect supported Meta and LinkedIn destinations through OAuth. We store redacted account metadata, the permissions granted, connection status, expiry information, and provider access tokens encrypted at rest. Tokens and provider identifiers are not returned through browser account catalogs.
Read-only metadata
Where historical records exist, Desk V1 can show limited redacted metadata for verified media assets, private voice sessions, connected or recorded provider accounts, and historical analytics. It does not expose storage URLs, credential material, provider identifiers, raw provider responses, transcripts, or private creative-policy configuration through these catalog surfaces.
Optional text generation
If an authorized user explicitly uses the copy-generation feature and the configured service is available, the prompt and requested draft context are sent to the configured text-generation provider to return draft variants. Generated text remains a draft for human review. Desk V1 does not use voice recordings as a transcription input.
Optional subscription image generation
If an authorized user requests an Article Hunt image, the headline and visual concept are sent to the locally installed Codex image generator authenticated through DigiMass’s ChatGPT subscription. The resulting image is validated, stored in the workspace media store, and marked AI-assisted. DigiSocial does not expose the local Codex authentication material or silently use an API key for this lane.
What is not enabled
Desk V1 does not yet offer provider delivery, live publishing, provider metrics refresh, voice upload/recording, audio playback, transcript viewing, social-message inbox access, LinkedIn Company Page connection, or self-service account export/deletion controls. Connecting a provider account does not authorize a post or contact the provider beyond the connection and identity-discovery flow.
3. Why We Use This Data
| Category | Current purpose |
|---|---|
| Authentication and workspace metadata | Sign-in, workspace selection, role-based access, and support. |
| Workflow content | Human-controlled drafting, creative review, and sandbox preparation. |
| Connected-account data | Discover and record destinations an authorized workspace operator explicitly connects. |
| Redacted historical metadata | Workspace visibility into recorded assets, sessions, accounts, and metrics. |
| Optional text-generation input | Return draft copy when an authorized user explicitly requests generation. |
| Optional image-generation input and output | Create, validate, store, review, and later attach an Article Hunt visual when explicitly requested. |
4. Service Providers
Desk V1 relies on configured infrastructure and authentication services needed to operate the Service. When an authorized user explicitly requests text generation or a subscription-backed Article Hunt image, the configured provider processes that request. This page does not claim advertising, analytics, or data-sharing practices beyond the current Desk V1 workflow.
During an account connection, the selected provider receives the OAuth request and returns the approved identity and token data. Desk V1 does not transmit draft or scheduled content to social platforms because provider delivery is not enabled.
5. Retention and Requests
We retain information only as needed to operate the current Service and respond to legal, security, or support obligations. Desk V1 does not yet provide self-service export, account deletion, AI-preference, or provider-disconnect controls. To request access, correction, deletion, restriction, or portability, email privacy@digimass.cloud. Requests are reviewed through the applicable support and legal process; this page does not state a fixed retention or response period that the product has not implemented.
6. Security
Desk V1 uses authenticated sessions, signed and time-limited OAuth state, selected-workspace access checks, database row-level controls, encrypted provider tokens, and narrowly scoped server/database contracts to limit access to workspace data. Sensitive browser surfaces return redacted metadata rather than raw storage, credential, or provider-response fields. Provider delivery remains deliberately disabled in this version.
7. Cookies
Desk V1 uses session cookies for sign-in, a selected-workspace cookie to preserve your current workspace context, and short-lived HTTP-only OAuth state cookies during an account connection.
8. Changes
We may update this policy as the product changes. The effective date above identifies the current Desk V1 version.
9. Contact
For privacy questions, requests, or complaints, email privacy@digimass.cloud.