Privacy Policy

Controller: CyanBridge (Fernando Saiyan)

Email: contato@fersaiyan.com

Support: contato@fersaiyan.com

CyanBridge includes a mobile companion for supported smart-glasses workflows and CyanBridge Model Studio, a local-first desktop application for personal datasets, model training, local inference, and optional cloud compute. This domain does not sell hardware. For any privacy-related inquiries, you may contact us at the email above.

We may collect the following categories of data:

• Account Information: email address, display name, and authentication credentials when you register for an account.
• Closed-Test Information: the Google Account email you voluntarily provide when requesting access to an Android closed test.
• Local Desktop Data: when you use Model Studio, raw personal exports, source parsing, privacy filters, dataset previews, local training, and local inference stay on your machine by default. We do not automatically collect or upload those files.
• Optional Cloud Job Data: if you explicitly start a cloud fine-tuning or hosted-inference job, the selected prepared training package, job configuration, and job metadata may be sent to the services needed to run that job. The upload scope is shown before launch.
• Usage Data: API model selection, number of requests, tokens consumed, job status, and timestamps. This data is used for quota enforcement, billing, support, and service improvement.
• Payment Data: transaction records (payment method type, amount, currency, timestamp). We do not store full credit card numbers, CVV codes, or other sensitive payment instrument data. Payment processing is handled by Asaas and Stripe.
• Communication Content: prompts, messages, voice recordings, and images you submit to AI models through managed inference. These are forwarded to the selected AI model provider and are not stored on our servers beyond transient processing for delivery, except where a service explicitly discloses otherwise.
• Device Information: Android device model, OS version, connected app version, smart-glasses integration state, and similar technical data for troubleshooting and analytics.
• Technical Data: IP address, browser/user-agent information, and session identifiers collected for security and operational purposes.

We use your data for the following purposes:

• Providing and operating the mobile companion, managed inference, and optional cloud-compute services.
• Managing user accounts, authentication, and access control.
• Managing Google Play closed-test access and communicating test-related updates.
• Enforcing usage quotas and processing subscription payments.
• Preparing, launching, monitoring, and settling cloud jobs that you explicitly authorize.
• Forwarding prompts and content to third-party AI model providers as requested by you.
• Improving the service, diagnosing technical issues, and preventing abuse.
• Complying with legal obligations and enforcing our Terms of Use.

The CyanBridge mobile companion and CyanBridge Model Studio source code are publicly available. You are free to inspect, audit, and verify how your data is handled at every layer of the applications:

• Mobile companion: includes device-bridge, transport, and data-handling code used for supported smart-glasses workflows.
• Model Studio: includes the local timeline tooling, dataset workflow, training, local serving, and managed coding-session code used by the desktop app.
• Managed web services: include the billing, cloud-job, and relay code that supports optional paid services.

We believe transparency builds trust. However, open-source availability does not imply any warranty or additional liability regarding the security or privacy of the system (see Section 9 below).

We share your data only where necessary to provide the service:

• AI model providers: receive prompts, messages, voice recordings, and images when you use managed inference. Their handling of that data is governed by their own privacy policies.
• Cloud compute providers: receive an encrypted, prepared training package and job configuration only when you explicitly launch a cloud fine-tuning or hosted-inference job. Raw source exports are not uploaded automatically.
• Asaas / Stripe: process subscription payments. They receive transaction data as necessary to execute recurring billing.
• Legal authorities: when required by applicable law, court order, or governmental regulation.

We do not sell your personal data to third parties. All third-party processors are contractually bound to process data only for the purposes described in this policy.

We implement reasonable technical and organizational security measures:

• Local-first processing for raw exports and personal dataset preparation by default.
• Encryption in transit (TLS 1.3) for all communications.
• Encryption at rest for stored data.
• Encryption of cloud training packages before they leave the Studio environment.
• Role-based access controls on server infrastructure.
• Regular security reviews and dependency audits.
• We do not store full credit card numbers, CVV codes, or passwords in plaintext.

We retain your data only as long as necessary:

• Account data: for the duration of your account plus 5 years after closure (statutory limitation period).
• Usage logs and quota records: for the current billing period plus 12 months for accounting purposes.
• Payment records: 5 years to comply with tax and fiscal obligations.
• Closed-test signup emails: until the closed test ends, plus up to 90 days for access reconciliation and support.
• AI prompts and responses: not retained on our servers beyond the time necessary to forward them to the AI provider and deliver the response back to you.
• Local exports and datasets: remain on your device unless you explicitly select a cloud job. We do not receive them automatically.
• Cloud job packages and artifacts: are kept only for the active job and the disclosed artifact-retention period. You can delete available cloud-job artifacts from Studio when that option is provided.

After the retention period, data is securely deleted or anonymized. Backups are rotated every 90 days, after which deleted data is overwritten.

Depending on your jurisdiction, you may have the following rights:

• Access: request a copy of the data we hold about you.
• Rectification: request correction of inaccurate or incomplete data.
• Erasure: request deletion of your data, subject to legal retention requirements.
• Portability: request transfer of your data to another service provider.
• Objection: object to processing based on legitimate interests.
• Withdraw consent: where processing is based on consent, you may withdraw it at any time.

To exercise your rights, contact us at contato@fersaiyan.com. We will respond within 30 days.

No Guarantee of Absolute Security. While we design CyanBridge with privacy as a core principle and take reasonable measures to protect your data, no system is completely secure. We cannot and do not guarantee that unauthorized access, data breaches, or other security incidents will never occur.

No Liability for Data Incidents. To the fullest extent permitted by applicable law, CyanBridge, its developers, and contributors shall not be held liable for any loss, corruption, or unauthorized disclosure of your data arising from security breaches, software vulnerabilities, or any other cause beyond our reasonable control. This includes, but is not limited to, data transmitted to or from third-party AI model providers via OpenRouter.

Open Source Does Not Imply Warranty. The fact that the CyanBridge source code is publicly available for inspection does not create any warranty, guarantee, or additional duty of care beyond what is explicitly stated in this policy and the Terms of Use.

Third-Party Services. Prompts and content you submit to AI models are forwarded to third-party providers (e.g., OpenRouter, and ultimately the AI model hosts). We have no control over how those third parties handle your data after it reaches them. You should review their privacy policies before using the service.

Use at Your Own Risk. By using CyanBridge, you acknowledge and accept these risks. You are responsible for evaluating whether the service meets your privacy and security requirements.

We may update this Privacy Policy from time to time. Material changes will be notified via email (if you have an account) or through a prominent notice on the website.

Continued use of the service after changes take effect constitutes acceptance of the updated policy.