Design documents and generation
Design documents and assets are stored locally. Design conversation history is stored separately in a local database; exporting an LDF design does not export that private chat history.
Design AI generation uses the hosted backend and server-selected model providers. Selected prompts, design source and context requested for generation can be processed remotely. Code's BYOK settings do not select Design's generation models. Local editing is separate from remote generation. See Design setup and exports for the workflow.
Three different data paths
- Local work: workspace files → local indexes, chat/history and checkpoints. They remain local authorities; the website cannot read that history.
- Direct BYOK: selected request context + your provider credential → the provider configured in the desktop app. That provider can process the request under its API terms. Account/configuration requests may still use Licuse services.
- Hosted AI: selected context → Licuse backend → OpenRouter/model provider, with any invoked search/fetch services. Responses return to the app. Account-linked usage and operational metadata are recorded separately.
Services involved
| Service | Role and data | Location / information |
|---|---|---|
| Supabase | Authentication, profile/plan, credits, hosted usage and request accounting; sandbox billing tables. | Northern Virginia, USA, for the configured project. Service operations and subprocessors may involve other locations. Privacy · DPA |
| Vercel | Website, server routes, delivery, network/security metadata and function diagnostics. | Website functions configured to iad1 (Washington, D.C. area, USA); global delivery network. Privacy |
| Fly.io | Hosted backend request processing, AI request context in transit/processing and operational diagnostics. | Amsterdam, Netherlands, for the reported live backend. This is not a promise about all provider logs or downstream services. Privacy |
| OpenRouter and routed model/search providers | Hosted prompts, selected context, attachments, output and invoked search queries/URLs. | Depends on the selected model, endpoint and tool. No blanket EU-only or zero-retention guarantee. Privacy |
| Your BYOK provider | OpenRouter, OpenAI or Anthropic receives direct API requests and the key for that provider. | Your provider account, model and API policy determine processing. OpenAI · Anthropic |
| Google sign-in / optional Google Analytics | Sign-in information if you choose Google; website analytics identifiers/events only if configured and consented. | These are separate purposes. Analytics does not run on account pages. Privacy |
| Polar | Checkout and customer portal, payer details, fraud checks, payment/subscription information; separate reseller/controller obligations. | Sandbox checkout is labelled and keeps test records separate from live purchases. Payment processing can be international. Privacy |
| GitHub | Handles sign-in information if you choose GitHub. Also hosts release installers, checksums and notes; download/update requests reveal normal network metadata to GitHub. | External release service. Privacy |
Training, retention and your provider
The current Licuse code does not include a pipeline that trains a Licuse model on your private workspace. Hosted routing requests data-collection restrictions where configured, but provider policies, endpoint capabilities and optional tools differ. We do not describe every provider or model as “zero data retention”.
Direct BYOK requests follow the selected provider’s controls; Licuse cannot change all settings in your independent provider account. Review the model/endpoint’s retention, abuse-monitoring and training terms before sending confidential data. A model’s brand name alone does not determine its processing location or retention behaviour.
Local deletion and historical records
Remove chats, notes, workspace history or provider connections using the relevant IDE settings. Back up what you need first. A local database, export, OS keychain entry or system backup may require separate removal. The web account cannot remotely inspect or wipe those copies.
Earlier versions may have stored server chat records. Current local storage and retirement of the legacy export route do not establish that historical data was erased. Include historical chats in a cloud deletion/access request if relevant.
For account data, contact hello@licuse.com. We review the relevant account stores and explain legal or recovery-related exceptions. See retention and rights.
Read this before sharing sensitive material
Use only data you are authorized to process. Review selected context, attachments and terminal output for secrets. Search tools may transmit a query or URL to another service; a signed private URL can itself be sensitive. Extensions, MCP connections or integrations you install can add recipients beyond those listed here.
These regional descriptions identify current/prepared deployment choices, not a comprehensive data-residency commitment. A specific residency, confidentiality or regulated-data requirement needs a verified arrangement before use. Email us for clarification.
A person you can reach.
Licuse is operated by Berat Doğan Araç, an individual based in Konya, Türkiye. Licuse is a brand, not a separate incorporated company.
hello@licuse.com ↗