CRM
Privacy Policy
Forja Labs LLC, Florida, United States, is responsible for CRM and its authentication. Contact us for support and privacy at support@forjalabs.dev. This policy describes the CRM version in development and the connections you may choose. We do not sell data, show advertising or track you across apps or websites.
Local workspace and optional account
You can organize clients, activities, notes, tasks, events, quotes and focus sessions without registering. Records, PDFs and your chosen profile photo remain on the iPhone. The system photo picker provides only the image you select; CRM does not request full Photos or Contacts access. The local workspace and each account use separate stores. There is no automatic cross-device synchronization or transfer between workspaces. Device backups, if enabled, follow your Apple settings and terms.
If you create an account or sign in, Supabase Auth processes your email, password, account identifier and authentication requests. The app keeps session tokens in Keychain, not your password. Account confirmation and recovery emails use Brevo. See Supabase and Brevo.
Optional recipients and purposes
Your business server receives an account token to verify its owner and the data needed for requested operations. Its operator must have permission to process customer information and maintain appropriate safeguards and provider agreements. Administrative provider credentials are configured on that server.
- WhatsApp Business/Meta processes phone numbers, messages and delivery status you synchronize or send.
- After explicit confirmation, the AI provider identified in the app—OpenAI or Google Gemini—receives your prompt and business instructions through the server. Customer details and up to ten recent messages are added only if you enable that option. The same provider checks content safety. Cancelling prevents sharing.
- Apple and Superwall process identifiers, metadata, products, releases, drafts and reports for your other apps. They do not sell access to CRM.
- Stripe processes your own business payment references and results. Full card details and provider credentials are not entered or stored in CRM; payments do not unlock CRM features.
Provider results and synchronized messages may remain on the iPhone and business server. Local notes and photos are not automatically sent to AI. Provider policies: OpenAI, Google, WhatsApp, Stripe, Apple, Superwall. We use data for requested functions and require providers we engage to protect it consistently with this policy and applicable obligations; external accounts you administer also have their own terms.
Safety and reports
The server checks AI input and output; blocked or unverifiable content is not returned as a valid draft. You may block a contact or provider in CRM. This does not block calls or messages in other apps. A content report contains a reason and reference; text is attached only if you choose. It is registered with your business server for its operator to review, not sent to AI. You may also report content directly to support@forjalabs.dev; avoid unnecessary customer information.
Assistant context and ChatGPT linking
In the general assistant you can authorize a summary of the 13 sections in the open workspace: customers, activity, quotes, notes, tasks, schedule, focus, stored messages, team board, paywalls, experiments, releases and profile. It may include personal and financial information. The summary is bounded to recent records and limited text; you can review it before confirming sharing with the identified provider. Other workspaces, photos, passwords and keys are excluded. Proposed changes are applied only after your review and explicit confirmation in CRM.
Optional ChatGPT linking takes place on OpenAI's official sign-in screen. If enabled, the server retains the OpenAI account identifier and any name and email OpenAI supplies to display the link. CRM does not request or store your ChatGPT password. Linking identity and using a plan for AI responses are separate capabilities; the hosted integration remains subject to OpenAI admission and configuration. You can request unlinking in the app or contact support to exercise your rights.
Retention, choices and deletion
Local records remain until you delete them. Signing out preserves the account store; forgetting a session removes the local login credential. Delete local workspace in Studio removes only that workspace. Reminders are optional and use a generic notification by default; you may enable titles or disable reminders. Declining optional permissions does not block local work.
To delete an account, choose Studio → Delete account and confirm your password. CRM first requests deletion of connected server records, then the authentication account; after both are confirmed it removes that account's local store and credentials. Errors are shown rather than claiming complete deletion. The server may retain a minimal deletion marker to prevent delayed events from recreating records. Its operator must apply applicable deletion duties to backups as well.
Previously received messages, documents and provider transactions are not automatically cancelled or removed; recipients' policies and obligations apply. Reports and server records remain while the account is active or until its operator deletes them. To exercise access, correction, deletion or objection rights regarding data processed by Forja Labs, contact support@forjalabs.dev. If law requires retention, we will explain its scope and applicable period.
Children and contact
CRM is a business tool and is not directed to children under 13. We will publish policy updates with a new date. Support and privacy: support@forjalabs.dev · Forja Labs LLC, Florida, United States. Help and contact.