App privacy notice

Scope and operator

Einwort, LLC operates the Einwort business app and invited pilot workspaces. This notice covers those services. The separate website privacy notice covers the informational website and updates list.

Information and purposes

We process sign-in identity, business membership and access records, business and brand information, uploaded media, drafts, schedules, reviews, approvals, channel connection and delivery status, and operational records needed to provide and secure the workspace. Content is used to organize your library and prepare drafts for your review. A manual download or customer-reported posting status is not independent proof of platform publication.

Providers and connections

Google Identity and Firebase Authentication support sign-in, including your Firebase account identifier, email address, verified-email status and sign-in provider. Current business membership determines access separately from sign-in. Google Cloud, Firestore and Cloud Storage support isolated business records, media and service operation.

Managed-library draft processing supports local models on Einwort-operated workers. Separate optional workflows use OpenAI when enabled and authorized for your workspace, sending the content needed for the requested processing. The processing path depends on the enabled feature and workspace configuration; processing may take place on an Einwort-operated worker or an enabled service provider. Resend handles enabled account invitations and review or manual-delivery notifications. Paddle supports subscription transactions as merchant of record; only an explicit purchase through an available checkout creates a paid subscription. Enabled features and recipients depend on your approved configuration. The applicable provider terms govern optional AI processing.

Facebook and Instagram connections use the authorized Page or professional-account identity, granted permissions, server-held connection credentials, selected media, captions, approvals, publication status and available insights needed for the enabled features. Approved content and necessary requests are sent to Meta for those operations. An account connection does not by itself approve a post or enable publication. Disconnect and platform revocation requests follow the applicable connection procedure; they do not automatically remove posts already published.

A TikTok connection uses the authorized account identifier, granted permissions, access and refresh credentials and their expiry information, and posting and status records to support approved channel operations. Credentials are held in a server-side Google Secret Manager vault rather than supplied to the review page. Einwort does not ask for your social-platform password. Permissions and availability are limited by the connected platform. Disconnecting Einwort records and revoking permission at the platform are separate operations.

Access and requests

Business access requires authenticated identity and current membership. Support access is limited to an authorized purpose. Use our contact form for access, correction, export, disconnect or account closure. We must verify your authority for the affected business before acting. Closing Einwort does not delete your Google or social-platform account or automatically remove posts already published there.

Closure requests follow a staged process: verification, stopped processing, the recovery window, cancellation or deletion. Cancellation alone does not resume work or revive revoked connections. Contact us to make or cancel a request; we verify authority and the affected records before acting.

Closure and backups

After an accepted closure request, we provide a 30-day recovery and cancellation window. Backup retention runs on the separate creation or deletion clocks below. We do not promise indefinite retention or a recovery guarantee.

The following retention schedule applies to the app and invited pilot workspaces.

Retention schedule
Information or copy	Retention
Active customer content	While the account is active, unless deleted sooner.
Accepted account closure	30-day recovery and export window, followed by active-data removal within 7 additional days.
Cloud database backups and deleted-file recovery	7 days on their respective creation or deletion clocks.
Local and NAS backups	30 days maximum from original creation, including snapshots, versions and deleted-file recovery.
Temporary restored databases and recovery copies	7 days, with a documented extension up to 30 days total.
Completed processing caches	Remove within 7 days after successful completion.
Resolved support attachments and correspondence	30 days for attachments and 90 days for correspondence. Account deletion may shorten these periods.
Ordinary operational logs	30 days.
Minimal approval and publication receipts	12 months from the event, using identifiers, timestamps, decisions and hashes instead of customer media.
Google-required audit records	400 days under the platform-required retention.
Minimal deletion and revocation records	400 days, or longer only when needed to prevent an explicitly retained backup from restoring deleted data.

The normal cleanup targets are active customer content removed by day 37 and remaining ordinary backup content expired by day 67 after an accepted closure request. Specifically retained records and documented legal or incident holds are exceptions. We do not report deletion complete until the applicable copies have been verified.

Copying or restoring a backup does not restart its age. Restored data stays isolated until deletion and revocation records are applied; a restore must not restart closed accounts or queued publication. Legal or incident holds identify the exact records, purpose and responsible person and are reviewed every 30 days. Unresolved-operation evidence remains held for explicit reconciliation.