Privacy Policy

1. Scope

This policy applies to inciver.com, Project-B access through the browser or application, Inciver account services, workspaces and projects, connected integrations, and related services operated by Inciver. A feature or connected provider may present an additional notice when its data handling requires more specific information.

2. Information users provide

Information a user provides may include a name, email address, account information, business ideas, workspace or project data, business metadata, website or store content, marketing content and drafts, support information, uploaded documents, preferences and settings, and communications with Inciver. The categories involved depend on the features the user chooses to use; not every user provides every category.

3. Account and session information

Inciver processes and may store information required to create and maintain accounts, authenticate sessions, secure access, and manage account state. This may include account identifiers, authentication and recovery information, session identifiers, account and plan status, workspace allowance, login or session events, and related security information.

4. Google authentication and authorization

Google authentication and authorization occur through Google’s OAuth services. Project-B does not receive the user’s Google account password. It receives only account information and authorization or data access permitted by the OAuth scopes the user approves. Users may disconnect a Google integration through supported Project-B controls and may revoke authorization from their Google Account connections.

6. Gmail data

When a user connects an authorized Gmail account for supported Customer Support functionality, Project-B may process relevant messages and related metadata allowed by the approved scopes. This processing supports customer-support workflows, maintains customer conversation context where needed, and prepares or manages supported responses or actions requested by the user. Inciver does not receive the user’s Gmail password through OAuth, and Project-B does not claim access beyond the scopes the user authorizes.

7. Facebook and Instagram / Meta

Facebook and Instagram integrations use Meta authorization flows. Project-B does not receive a user’s Facebook or Instagram password through OAuth. Inciver may process authorized account, Page, or business identifiers; permission state; connection metadata; authorization tokens; content or publishing data; and related information required for marketing features the user explicitly enables. This information is used to provide the connected marketing functionality the user requests. Users can disconnect the integration in supported Project-B controls and revoke the app’s access through their Meta or Facebook settings.

8. Authorization tokens and connected-service credentials

Inciver may securely process and retain session or authorization credentials, such as access or refresh tokens, where required to maintain a connected service. Provider passwords are not received through OAuth. Tokens are not exposed publicly and authorization data is used only to provide authorized functionality. Production provider secrets are handled through backend infrastructure rather than embedded as production secrets in the desktop client.

9. AI-powered processing

Project-B includes AI-powered functionality. Content necessary to complete a task requested by the user may be processed by Inciver systems and relevant AI or service providers. Depending on the task, this may include a business idea, workspace context, instructions, research inputs, document excerpts, and other content needed to produce the requested result. Inciver limits this processing to operating and supporting the requested functionality and does not promise that an external provider retains no data unless that commitment applies to the service arrangement in use.

10. Project and workspace information

Inciver may retain information necessary to operate Project-B, including workspace and project records, feasibility results, research outputs, generated outputs and user actions, website or store data, marketing drafts, operations data, settings and context, and connected-service state. This allows the product to preserve user-requested project history and keep work connected across supported features.

11. Documents and PDF processing

When users upload documents or PDFs for supported functionality, Project-B processes the content necessary to provide the requested analysis, summarization, or related task. The amount and duration of processing depend on the requested feature and operational requirements. Inciver does not promise immediate deletion of every copy after processing.

12. Marketing scheduling and publishing

When users connect supported channels and explicitly configure or approve publishing, Inciver may process authorized connected-account information and the user’s content to schedule or publish the requested material. This processing is limited to supported, user-directed marketing workflows and does not imply access to unrelated social content.

13. Payment information

Payment processing is not currently active on the public website. When it becomes available, payment-card processing will be handled by an authorized payment provider. Inciver does not need to directly store complete payment-card numbers or card security codes to operate subscription billing. Inciver may receive and retain limited billing or transaction metadata needed to manage a subscription, such as plan or subscription state, payment status, amount, currency, provider identifiers, relevant timestamps, and cancellation or renewal state.

14. Device, security, and service-log information

Operating and protecting the services may involve processing an IP address, browser or device information, timestamps, request metadata, login and session events, security events, and service diagnostics. Inciver uses this information for delivery, reliability, troubleshooting, and security; this policy does not claim that Inciver uses invasive device fingerprinting.

15. Cookies, local storage, session technologies, and analytics

Inciver uses cookies, browser storage, and similar session technologies where needed for authentication, session continuity, security, language or theme preferences, display settings, and necessary site functionality. Inciver also uses Cloudflare Web Analytics to understand website traffic and performance at an aggregate, privacy-oriented category level. Inciver does not describe or use these necessary technologies as advertising cookies and does not use the analytics service to build unrelated advertising profiles.

16. How information is used

Inciver uses information to provide Project-B and related services; authenticate accounts; maintain projects and workspaces; operate connected integrations; complete AI-powered tasks; support user-approved marketing workflows; provide customer-support functionality; manage subscription and billing state; prevent security threats, fraud, and abuse; diagnose and improve reliability; respond to support requests; and comply with applicable legal obligations.

17. When information may be shared

Information may be shared with service providers and processors necessary to operate Inciver, including cloud and infrastructure providers; AI providers where needed for requested AI functionality; connected platforms at the user’s direction; payment processors when enabled; and advisers, authorities, or other parties where a security or legal disclosure is reasonably required. Information may also transfer as part of a proposed or completed merger, financing, acquisition, reorganization, or sale of relevant assets, subject to appropriate handling. Inciver does not sell users’ personal data as part of Project-B’s ordinary business model.

18. Data retention

Inciver retains information only for as long as reasonably necessary to provide account and service functionality, maintain user-requested project history, meet security and operational needs, satisfy applicable legal or accounting obligations, and resolve disputes. Retention differs by category, service state, and context. Deletion from active systems does not necessarily remove information immediately from every protected backup or record that must be retained for a legitimate reason.

19. Data deletion

The normal account-wide deletion mechanism is available inside Project-B: open Settings, choose Delete All Account Data, review the confirmation, and confirm only when ready. Once confirmed, the deletion is permanent and cannot be undone through Project-B. Delete Workspace removes only the selected workspace and is not the same as deleting all account data. The Project-B Data Deletion instructions explain both actions and provide support contact details if account access is unavailable.

Users may separately disconnect integrations and revoke Google or Meta authorization through the applicable provider controls. Deleting Project-B data does not automatically delete information independently controlled by Google, Meta, payment providers, or other third parties, and Inciver does not claim that every protected backup is erased instantly.

20. Security

Inciver uses reasonable administrative and technical safeguards appropriate to the services, which may include access controls, protected backend infrastructure, authorization controls, secret-management practices, and monitoring. No internet service can guarantee absolute security. Users should protect their account credentials and notify Inciver if they suspect unauthorized access.

21. International processing

Inciver and the online infrastructure or service providers used to operate the services may process information in different jurisdictions. Applicable protections can vary by location. This policy does not claim a specific transfer mechanism where one has not been established for the relevant processing.

22. Children

Project-B is intended for people using the service for business or project purposes. It is not intended to knowingly collect children’s personal data in violation of applicable law. If a parent or guardian believes a child has provided personal information inappropriately, they may contact Inciver.

23. User choices and privacy rights

Users can update available account information, sign out, disconnect integrations, revoke Google permissions, revoke Meta permissions, use Settings → Delete All Account Data for the normal account-wide Project-B deletion flow, request access to or correction of account-associated information where applicable, and manage subscription cancellation or resumption when those controls are available. Depending on where a user lives, applicable law may provide additional privacy rights. Inciver may verify a separate privacy request and may retain limited information where a legitimate legal, security, accounting, or dispute-resolution need applies.

24. Changes to this policy

Inciver may update this policy as the website, Project-B, connected services, or operating practices change. Updates will be reflected by revising the “Last updated” date on this page.

25. Contact

For privacy questions or requests, email support@inciver.com. Do not send passwords, OAuth tokens, or payment-card details.