Fyncta Privacy Policy

Public URL: https://fyncta.com/privacy-policy Last updated: 2026-05-21

1. Introduction and Scope

This Privacy Policy explains how Fyncta collects, uses, shares, and protects personal data in connection with Fyncta Cloud, approved Fyncta Web Apps, Fyncta Mobile Apps, and Fyncta AI Vault Private Server.

This Policy applies when you create an account, use consumer-facing Fyncta services, install or use Fyncta AI Vault Private Server, interact with approved Fyncta Web Apps or Fyncta Mobile Apps, contact support, or otherwise engage with the end-user side of the Fyncta platform.

2. How Fyncta Works: Cloud Control Plane and Local AI Vault Processing

Fyncta uses a split architecture.

Fyncta Cloud provides account, authentication, session continuity, billing, telemetry, pairing, relay-session coordination, governance, support, and related control-plane services.

Where a Fyncta experience is designed to use Fyncta AI Vault Private Server, protected app-scoped AI inference, local storage, local memory, tools, skills, and task execution are intended to occur within the user's selected AI Vault Private Server rather than in the ordinary web or mobile interface layer.

Fyncta Web Apps and Fyncta Mobile Apps are generally interface surfaces for approved app contexts.

This means some personal data may be processed locally on your device through AI Vault, while other personal data may be processed by Fyncta Cloud to provide sign-in, account management, billing, security, telemetry, pairing, relay, support, and other control-plane functions.

3. Categories of Personal Data We Collect

Depending on the service and feature, we may collect:

account and identity data
contact data
authentication and security data
device, browser, and application data
billing and payment-related data
support and communications data
activity, telemetry, and diagnostic data
pairing, relay, and session metadata
content or inputs you choose to provide through supported features

The categories collected in a particular case depend on which Fyncta services you use, whether AI Vault is involved, whether you enable remote access features, and whether you contact support or request help with a specific workflow.

4. Data We Collect Directly From You

We may collect data you provide when you:

create or manage an account
sign in or verify identity
subscribe, purchase, or manage billing settings
contact support
configure product settings
submit prompts, records, files, or other content through supported services

If you contact support or request troubleshooting help, you may also provide screenshots, logs, example prompts, diagnostic details, or other materials that help us understand the issue.

5. Data We Collect Automatically

We may collect technical and usage information automatically, such as:

IP address and general location information
device identifiers and operating-system information
browser or app version information
sign-in, session, and security event data
telemetry about feature use, failures, latency, or operational health

We may also collect cookie, local storage, session, or similar browser-level information where needed to support continuity, security, configuration, or measurement.

Fyncta Cloud may process account registration details, authentication events, subscription state, billing records, payment-provider references, refund handling records, support history, and related administrative information.

Fyncta does not directly collect or store full end-user payment card details as part of the ordinary billing flow. End-user card payments are handled by third-party payment providers such as Stripe and Paddle.

Where billing is handled by third-party providers, Fyncta may receive transaction metadata, subscription status, billing identifiers, and refund-related records needed to manage the service relationship.

Billing and payment providers may also use billing country, region, or other jurisdictionally relevant location information to determine and apply applicable sales, value-added, goods-and-services, or similar taxes during checkout.

Fyncta Web Apps may collect or transmit interface-layer data needed to render the product experience, maintain session continuity, submit user actions, and support approved product behavior.

Where an app is designed to use AI Vault, the web app is intended to act as the client interface surface rather than the primary protected execution plane for app-scoped AI work.

In those flows, prompts, commands, or records you trigger through the web app may be sent to your selected AI Vault for processing, while Fyncta Cloud may separately process control-plane information about the session, identity, billing, telemetry, support, or remote access state.

Fyncta Mobile Apps may collect or transmit interface-layer data needed for sign-in, device registration, proof registration, discovery, pairing, relay-session bootstrap, support, and chat-style or dynamic UI presentation.

The mobile product direction may use one common chat shell across Android and iOS to interact with app-scoped agents for supported Fyncta experiences.

Dynamic UI rendering or structured responses are presentation-layer behavior and do not by themselves determine trust, routing, or policy.

Where remote AI Vault access is supported, the mobile app may function as a remote control surface for app-scoped AI Vault execution rather than as the primary execution environment itself.

Where used, Fyncta AI Vault Private Server is intended to be the local runtime and local data boundary for protected app-scoped inference, memory, tools, records, and task execution.

Each AI Vault installation is designed to be owner-bound and private to one Fyncta end user at a time. It is not intended to operate as a shared AI Vault store for unrelated Fyncta end users or to hold another Fyncta end user's protected AI Vault workspace data as part of the ordinary product model.

Depending on the feature, data such as prompts, responses, local records, local vectors, task state, or local memory may be processed or stored within that local environment.

This does not mean all data stays local. Fyncta Cloud may still process control-plane, security, billing, and support data related to the same user or workflow.

Fyncta does not describe every category of locally processed AI Vault data as being routinely uploaded to Fyncta Cloud. If cloud transfer occurs for a particular feature, support interaction, remote-access flow, sync feature, or diagnostic workflow, that transfer should be limited to what is needed for that function as described in the applicable product flow or notice.

10. Local Processing Versus Cloud Processing

Fyncta aims to distinguish between:

data processed locally in AI Vault for protected app-scoped execution
data processed by Fyncta Cloud for account, security, billing, telemetry, governance, support, and control-plane functions
data processed by service providers that help operate the platform

Where remote relay-backed access is supported, relay infrastructure is intended to function primarily as transport and session coordination rather than as the default long-term storage or primary execution layer for protected app-scoped content.

In other words, the existence of a cloud session, mobile shell, web app surface, or relay path does not mean protected app-scoped AI work is ordinarily performed in the general Fyncta cloud environment.

11. Remote Access, Pairing, Relay, and Session Metadata

Fyncta may process pairing records, relay-session issuance data, session identifiers, device identity or proof metadata, security events, authorization context, and related records needed to support remote access features securely.

Depending on the implementation, relay infrastructure may transiently handle traffic needed to establish or maintain remote sessions.

Relay or pairing support does not mean Fyncta necessarily stores the full substance of all prompts, outputs, records, or task data in the relay layer.

12. How We Use Personal Data

We may use personal data to:

provide, maintain, and secure the services
authenticate users and maintain sessions
process subscriptions, billing, refunds, and related administration
support pairing, relay, and remote access workflows
monitor reliability, performance, abuse, fraud, and policy compliance
provide support and respond to requests
improve features and user experience
comply with legal obligations and enforce our terms and policies

We may also use personal data to investigate security incidents, troubleshoot failures, maintain auditability, and preserve evidence needed for abuse-prevention, dispute handling, or legal compliance.

13. Legal Bases for Processing

Where required by applicable law, our legal bases may include:

performance of a contract
legitimate interests
compliance with legal obligations
consent, where consent is required

These legal bases may apply differently depending on the service, jurisdiction, and the specific processing activity involved.

We may share personal data:

when required by law, legal process, or lawful governmental request
to protect rights, safety, security, or platform integrity
in connection with a merger, acquisition, financing, or business transfer

We do not sell personal data in the ordinary sense of exchanging it for money, unless we specifically state otherwise in a region-specific disclosure.

15. Partners, Service Providers, Payment Providers, and Other Recipients

Some Fyncta experiences may involve approved partners or partner-operated app contexts.

Where a partner controls separate downstream processing beyond the standard Fyncta platform flow, additional partner-specific notices or supplemental disclosures may apply.

16. International Transfers

Fyncta and its service providers may process data in countries other than your own.

Where applicable law requires a transfer mechanism for international data transfers, Fyncta.com will rely on the transfer mechanism recognized by the applicable law for the specific transfer in question.

17. Data Retention

Fyncta retains personal data for as long as reasonably necessary for the purposes described in this Policy, including to provide the services, maintain security, meet legal obligations, resolve disputes, and enforce agreements.

Retention periods may vary by data type, product flow, and jurisdiction.

For example, billing and tax-related records may be retained longer than routine troubleshooting records, and security or audit records may be retained longer where needed to protect the platform or comply with law.

18. Security and Safeguards

Fyncta uses administrative, technical, and organizational measures designed to protect personal data.

No method of transmission, storage, or processing is completely secure, and Fyncta cannot guarantee absolute security.

19. Cookies, SDKs, Telemetry, and Similar Technologies

Fyncta may use cookies, software development kits, local storage, session mechanisms, diagnostic logging, and similar technologies to operate the services, remember settings, maintain continuity, measure usage, and improve reliability.

This section should be expanded with any consent, cookie-category, or regional disclosure detail required before publication.

20. Your Privacy Rights and Choices

Depending on your jurisdiction, you may have rights to access, correct, delete, export, restrict, object to, or withdraw consent regarding certain personal data.

Fyncta may need to verify your identity before fulfilling some requests.

Some requests may be limited where Fyncta must retain data for security, billing, legal, fraud-prevention, recordkeeping, or contract-performance reasons.

21. Region-Specific Disclosures

If a jurisdiction requires additional privacy disclosures, consumer rights details, consent language, or opt-out mechanisms beyond this Policy, Fyncta.com may provide those details through a supplemental notice, product interface, or region-specific disclosure.

22. Children's Privacy

Fyncta's consumer-facing services are not directed to children under 18 and are not intended to be used by children under 18 without authorization from a parent, guardian, or other legally authorized adult where such authorization is required by law.

If Fyncta.com becomes aware that it has collected personal data from a child in a manner that requires deletion or additional action under applicable law, Fyncta.com will take reasonable steps to address the situation.

23. Changes to This Privacy Policy

Fyncta may update this Policy from time to time.

If required, Fyncta will provide notice through the services, by email, or by other reasonable means.

24. Contact Information

Fyncta.com is the operator for this Privacy Policy.

For end-user privacy requests, account questions, or privacy-related support, use the end-user panel contact surface at https://fyncta.com/panel/end-user.