WorkflowRight privacy policy

Last updated: 9 October 2026

This policy describes WorkflowRight's current web platform and Android companion. It is an engineering description of implemented practices, not a certification of compliance with every jurisdiction.

Accounts and organization membership

Clerk authenticates users. WorkflowRight associates the Clerk identity with a stable internal user identifier and synchronizes display name, verified email addresses and profile-update time. Organization administrators manage membership, roles and permissions. One account can belong to several organizations; their applications and records are kept separately.

Business process information

Organizations configure applications, records, workflow forms, tasks and process instances. The information entered depends on those configurations and may include personal or business information. WorkflowRight processes this content to run the configured services. Organization administrators determine the business purpose and access rules; WorkflowRight does not know every purpose of arbitrary organization-defined content.

Subscriptions

Google Play handles Android checkout and subscriptions, and RevenueCat processes store purchase information. WorkflowRight verifies subscription information with RevenueCat and stores the product, subscription state, access period and organization binding. WorkflowRight does not receive full payment-card details through this integration. Subscriptions belong to organizations. Purchaser identifiers and binding history are retained to prevent inappropriate subscription transfers.

Devices and notifications

The Android app stores session information in SecureStore. Optional notification registration creates a random device identifier and, when permission is granted, sends a push token to WorkflowRight. If push delivery is enabled by the operator, Expo and Google's notification infrastructure deliver notifications. Task notifications use generic text and a task link; this statement does not assert that production push delivery is enabled. Signing out attempts to revoke that device registration. Requesting account deletion revokes account device tokens on the server.

Files and attachments

The platform can store organization attachments in Vercel Blob and associated metadata in PostgreSQL. Access follows organization permissions. The current Android task interface may display record references; it does not provide a general file-upload picker. Organization content and attachments are not automatically erased when an individual account is deleted.

Diagnostics and security

Operational logs and audit history help investigate failures, protect accounts and maintain workflow integrity. Billing diagnostics store limited processing evidence rather than full webhook payloads or purchase tokens. Hosting and service providers may separately process connection and device metadata. We use authentication, authorization and tenant access controls; no system can be guaranteed completely secure.

Service providers

• Vercel hosts the web application and operational services; Vercel Blob stores platform attachments.
• Neon hosts the PostgreSQL application database.
• Clerk provides identity and authentication.
• Resend sends configured service emails, including invitations.
• RevenueCat and Google Play support Android purchases and subscription verification.
• Expo supports the mobile application and, when enabled, push delivery alongside Google infrastructure.

These providers have their own policies and processing practices. This policy does not claim fixed provider retention periods or that their SDKs collect no additional telemetry.

Retention and deletion

Retention is not governed by a single automatic deletion period today. Organization data, workflow history and security/audit information can remain after membership ends or an account is anonymized. Completed personal-account processing removes the local name/email profile and device registrations and deletes the Clerk identity. A stable pseudonymous user reference, the old authentication identifier as a blocked tombstone, and billing bindings remain for history and anti-transfer protection. Retained references are still data, not a claim of complete irreversible anonymization. Backups, service-provider records and organization-owned content require separate retention review by the operator and organization.

Your choices

Contact us about privacy. The public form collects your email address, request category and message, and optionally your organization name. We store these details in our database for operator review and send an operational notification through Resend to the operator's Google-hosted mailbox. These details are unverified and are not automatically linked to a user or organization. A keyed fingerprint suppresses duplicate requests; keyed email/network identifiers enforce short-lived request limits. Raw IP addresses are not saved in the intake tables. Hosting providers may separately retain connection logs.

Request records and email copies are retained to handle enquiries and document their resolution. There is no automatic request-content deletion period currently; retention and removal are reviewed by the operator, including provider/mailbox copies and backups. We do not promise a fixed response time. Public submission is not authorization to access or delete an account, and we may need to verify your identity.

You can manage account information through the available sign-in account controls, ask organization administrators about membership and organization data, and control notification permission on your device. Leaving an organization, deleting a personal account and deleting an organization are distinct operations. Administrators can use existing exports where appropriate; export is not a prerequisite to requesting deletion.

See account deletion instructions for restrictions, cancellation of pending requests and information retained. Deleting an account does not cancel Google Play billing; manage subscriptions in Google Play separately.

Operator and contact

Operator: FullStackDev KZ | WorkflowRight.

For privacy and account enquiries, use the WorkflowRight privacy request form. Requests may require identity verification before processing.