Privacy Policy

1. Who we are and what this policy covers

Rovemark, Inc. provides sovereign AI infrastructure, software and services. This Privacy Policy covers our websites, hosted platform, APIs and applications, including Logica Deck, when Rovemark determines how personal information is used. Product-specific explanations in this policy apply only when you use the corresponding feature.

Our address is 2810 N Church St STE 91903, Wilmington, DE 19802, United States. For privacy, data-rights and support requests, contact [email protected]. General business inquiries can be sent to [email protected].

2. Rovemark and your workspace operator

For website visits, direct customer relationships, billing, service security and support, Rovemark acts as the organization responsible for the processing described here. When we process workspace content on behalf of a customer, that customer determines its purposes and permissions; our processing follows its instructions and the applicable agreement.

For a self-hosted or customer-operated LogicaOS installation, the organization or person operating it controls its users, workspace content, storage, backups and configured providers. Installing a Rovemark app does not by itself give Rovemark access to all of that installation’s content. Ask your workspace administrator about its configuration and additional notices. A service agreement or data-processing agreement may provide additional safeguards.

3. Information we handle

• Account and relationship information: name, email, profile image, organization, role, invitations, authentication and session identifiers, preferences, and messages you send to sales or support.
• Workspace content: prompts, conversations, agent instructions, memories, missions, tasks, schedules, connected-calendar events, files, images, documents, code, terminal commands and output, and results you submit or access. Content can contain personal information supplied by you or another authorized participant.
• Integration information: authorization tokens, selected scopes, connected-account identifiers and information retrieved or sent through the services you connect. Only connect accounts and provide content you are authorized to use.
• Billing information: plan, credits, purchases, invoices, billing contact, transaction identifiers and payment status. Payment processors handle payment credentials according to the checkout method; Rovemark uses the transaction information needed to administer the purchase.
• Technical information: IP address, device and browser characteristics, app version, request and connection times, security and audit events, service usage, errors and operational diagnostics. These are distinct from optional marketing-site metrics.
• Public and third-party sources: public pages and records requested through research, collection or AI-visibility tools, information returned by configured providers, and content shared by workspace administrators or collaborators. A public source may still contain personal information.
• Website forms: contact and business details you choose to provide, such as name, email, phone, company, role, country, city, team size and the request itself. Do not include passwords or sensitive information unrelated to your request.

4. Why we use information and the applicable basis

• To create and administer accounts, authenticate access, provide requested features, run authorized agents and integrations, maintain workspace continuity, provide support and deliver purchases: performance of a contract or steps you request before entering one.
• To secure services, investigate misuse, maintain reliability, diagnose faults and manage business relationships: legitimate interests in operating safe and effective services, balanced against the rights of the people affected.
• To maintain required financial records, respond to valid legal requests and meet other applicable obligations: compliance with law.
• For optional website metrics, permissions or other processing that requires your agreement: consent. You can withdraw it through the relevant controls or by contacting us; withdrawal does not change processing that was lawful before withdrawal.
• For customer-controlled workspace processing: the customer determines the applicable purpose and legal basis. Availability of a feature does not itself authorize processing someone else’s information.

5. AI, memory and automated actions

AI features may send the input and context needed for your request to a model or tool provider selected for the workspace. Saved memory, retrieval and operation history support the workspace’s services; they are different from training a general-purpose model. This policy does not authorize Rovemark to use private workspace content to train general-purpose AI models.

External model providers apply their own service terms, retention settings and data-use controls. Local and cloud processing depend on the actual deployment and provider configuration; the term “sovereign” is not a promise that every possible integration runs only on your device. Ask your administrator which services receive your information.

Agents and routines can make recommendations or take actions within their configured permissions. Users and workspace operators must review consequential outputs and configure appropriate approvals. We do not use optional website metrics to make decisions with legal or similarly significant effects about individuals. If you believe an automated action has affected your rights, contact us and your workspace administrator.

6. Who may receive information

• Your workspace administrator, authorized collaborators and the appliance or server you choose to connect to, according to workspace permissions.
• Infrastructure, hosting, storage, delivery, security, support and payment providers needed to operate the services. Depending on the feature, these can include Stripe for platform billing, other payment services identified at checkout, and a configured messaging service for internal follow-up on a contact request.
• External AI, browser, repository, calendar, messaging and other integration providers involved in an action you or your workspace authorize. Their processing is subject to their terms and the applicable configuration.
• Google Analytics for optional website metrics after consent; Expo and Apple or Google notification services for enabled mobile push; and device-platform speech services when you choose system dictation.
• Authorities or other parties when legally required, to protect rights and safety, or in a corporate transaction subject to applicable safeguards and notice. We do not provide unrestricted workspace access merely because a third party requests it.

7. Cookies and optional website metrics

Essential storage supports functions such as language, theme, login and security. Optional metrics are separately controlled through “Metrics preferences” in the footer. Refusing them does not prevent you from using the public website.

With permission, our website uses a random browser identifier valid for 90 days to associate a visit with signup or subscription. The service stores a one-way version for up to 400 days. These events do not include your name, email or workspace operation content. Withdrawal stops this optional measurement and requests deletion of the associated visit identifier.

Google Analytics is loaded only after permission. The implementation excludes URL query parameters from the page location sent and does not intentionally send workspace content. Google receives technical information associated with its analytics requests. Its own privacy policy and browser controls also apply. Permission for website metrics does not enable mobile-app diagnostics.

8. Logica Deck and mobile permissions

Logica Deck (Android package com.logicaos.deck.mobile) connects a phone to an existing authorized Deck or LogicaOS installation. It handles device and appliance identifiers, pairing credentials and cryptographic material, session state, workspace information and actions needed for the features you use. It does not provide standalone commercial-account registration.

• Camera access is used when you choose QR pairing. Selected photos, documents or other attachments are used for the action you request; selecting a file can transmit its contents to your connected workspace and its configured services.
• System dictation turns speech into text you can review before sending. Depending on device settings, the operating-system provider may process speech locally or through its services. The mobile app does not persist a separate dictation audio recording.
• When enabled and provisioned, push uses device notification tokens and the notification content generated by your Deck through Expo and the platform’s notification infrastructure. Manage permission and lock-screen previews in device settings.
• Optional biometric or device-code protection uses the operating system. The app receives the authentication result, not your fingerprint, face template or device passcode.
• Drafts, offline information and preferences can remain on the device. Widgets use a limited local summary; displaying additional names or details is optional. Removing a pairing clears its associated app-managed session, workspace state and widget summary. Copies exported elsewhere remain at their destination.
• Optional stability sharing is off by default for the selected appliance. Reports contain limited versions, affected areas, numeric codes, durations and times. The report schema excludes conversation text, commands, project names, URLs, tokens and raw error stacks. Reports go to the selected appliance; shared diagnostic records there expire after seven days.
• Relay infrastructure may process IP addresses, connection times and technical identifiers to route and protect connections. The app uses encrypted pairing and transport. The mobile app does not include third-party advertising SDKs or use workspace content to deliver third-party advertising.

9. How long we retain information

Retention depends on the type of information, the service, the deployment and legal obligations. We keep account and relationship records while needed to provide and administer the service; billing records for applicable accounting and tax obligations; support correspondence while needed to handle the request and follow-up; and security records while needed to investigate abuse, protect services or resolve disputes.

Workspace content follows the customer’s instructions, contract and configured retention and backup settings. A subscription cancellation does not itself delete workspace history or constitute a data-deletion request. Local app data follows app controls and the device’s storage lifecycle. Website attribution and mobile stability periods are specified in the sections above.

When information is no longer needed, it should be deleted or anonymized according to the applicable process. Backup copies may remain until their normal replacement cycle; records retained for a legal obligation or dispute are restricted to that purpose. We will explain relevant retention exceptions when handling a deletion request.

10. Your rights, account deletion and choices

Depending on applicable law, you may request confirmation and access, correction, deletion, a portable copy, restriction of processing, or objection to certain uses. You may withdraw consent and object to direct marketing. You may also have rights relating to significant automated decisions. We do not sell personal information or share it for cross-context behavioral advertising.

Email [email protected] with the subject “Privacy request” or “Account deletion”. Identify the account or workspace and your request, without sending passwords, API keys or identity documents unless securely requested. We may verify your identity and authority and will respond within the period required by applicable law. An authorized representative may act where the law permits. We will explain any refusal, limitation or necessary retention.

For customer-controlled data, contact your workspace administrator; we can help route the request. Revoking a mobile pairing stops that device’s access but does not delete the workspace account, organization records or copies held by independent integrations. For Rovemark-controlled accounts and data, you can request deletion through the contact above; account deactivation alone is not data deletion.

You may complain to the competent supervisory authority, including the ANPD in Brazil or your local European or UK data-protection authority where applicable, and request review of our response. We will not penalize you for exercising applicable privacy rights.

11. International processing

Rovemark is based in the United States. The infrastructure, people, customer installations and providers involved in delivering a feature can be located in other countries. A self-hosted installation’s location does not determine the location of every external tool it invokes.

Where applicable law restricts an international transfer, the responsible parties must use an appropriate legal mechanism, such as an adequacy decision or approved contractual safeguards, with additional measures where required. Contact [email protected] for information about the processing locations and safeguards applicable to your service.

12. Security and sensitive information

We use technical and organizational safeguards appropriate to the service, including access controls, permission boundaries and encrypted communications where implemented. No system can guarantee absolute security. Protect your devices and credentials, review integration scopes and report suspected unauthorized access to [email protected].

Do not submit highly sensitive information unless the product, workspace configuration, agreement and applicable law allow its processing. Customer administrators are responsible for their own deployment controls and authorized users. External destinations and exported files have their own security and retention practices.

13. Children

Our services are intended for professional and organizational use and are not directed to children. If you believe a child has supplied personal information without appropriate authorization, contact us so we can investigate and take the measures required by law.

14. Updates and contact

The date on this page identifies this version. We may update the policy as services, data practices or legal requirements change and will provide additional notice or obtain consent when required. A policy change does not itself authorize a new use that requires consent.

Privacy, deletion and support: [email protected]. General inquiries: [email protected]. Postal address: Rovemark, Inc., 2810 N Church St STE 91903, Wilmington, DE 19802, United States.