ricursor / privacy
Privacy notice
Last updated 2026-10-19 · Current application practices
01Platform administration
Active platform staff with verified two-factor authentication can read bounded account identifiers/display names, workspace/project metadata, connection eligibility, recorded usage and CI finding counts. Workspace owner/admin roles do not grant this access. Platform owners with recent verified authentication can change display names and internal Free/Starter/Pro assignments. Internal assignments are not paid subscriptions. Successful reads and changes record staff identifiers, scope, timestamps, reasons for changes and correlation identifiers in a protected audit trail; change receipts support safe retries. Account deletion removes its current internal assignment, but protected receipts and audit history may remain subject to operator-defined retention. This release does not expose passwords, connection secrets/hashes, memory rules, raw CI logs or code to staff. Audit and staff-assignment retention periods require operator review before launch.
02AI CI-log analysis
When a workspace developer requests CI analysis, submitted logs and selected project/workspace constraints are sent to Lovable AI to explain quality violations and suggest fixes. Raw submissions are not saved by this feature, but findings (including evidence excerpts), suggested fixes and applied-fix records are saved in workspace CI history and visible to workspace members until the project or workspace is deleted. Providers may process operational logs. Only submit authorized content without credentials or unnecessary personal data. Analysis is autonomous after submission, but no code is changed or command executed. Follow-up comparisons show association, not proof that a fix caused improvement.
03AI code reviews
When a maintainer requests a code review, submitted changes and the selected project's saved constraints (including workspace-wide rules) are sent to Lovable AI to identify architectural conflicts. Review submissions and results are not saved by this feature; service providers may process operational logs. Only submit code you are authorized to share, without secrets or unnecessary personal information. Findings are advisory and do not apply changes automatically.
04Who is responsible
Ricursor operates this application. The controller’s legal name, postal address and privacy contact have not yet been published. This notice describes the current application, not a certification of GDPR compliance. Those details and an operational rights-request channel must be completed before a public launch.
05Information we process
Account email and authentication records; profile name, bio, website and optional photo; appearance and live-update preferences; workspace and project memberships; memory rules, reported token usage, file paths, state changes and Console activity. Team invitations contain the invited email and membership role. Only submit project content you are authorized to share; do not include credentials or unnecessary personal data.
06Purpose and lawful basis
Account and workspace information is used to deliver the service you request (performance of a contract, Article 6(1)(b)). Authentication, access controls and recovery support service security (legitimate interests, Article 6(1)(f), subject to a documented assessment). Optional analytics and marketing tracking are not currently used. A controller review must confirm these bases and any legal-obligation retention before launch.
07Service providers and access
Lovable Cloud provides hosting, authentication, database and private avatar storage. Choosing Google or Lovable sign-in shares authentication information with that provider. Workspace members can access workspace content according to their roles; an AI assistant you authorize through MCP can access permitted project context. Hosting providers may process operational request logs. App errors can also report the page address, error details and stack to Lovable when its reporting hooks are available. No sale of personal data is implemented.
08Retention and deletion
Account data is stored while your account is active; workspace content remains until deleted through the service. Account deletion removes your account and private avatar files, and attempts to remove owned personal workspaces. Owners of shared workspaces must resolve ownership first. Contributions in other workspaces may remain. Exact backup, log and invitation retention periods are not yet published; deletion here does not guarantee immediate removal from provider backups.
09Your rights
Subject to applicable conditions, you may request access, rectification, erasure, portability, restriction and objection. Settings lets you edit your profile, download accessible account records and delete your account. That download is not a complete disclosure of all provider-held records. You may complain to your local data protection authority. No dedicated channel for additional rights requests is currently published.
10International transfers and security
Workspace isolation and private avatar storage limit access; authorized workspace content is shared with team members and connected assistants. Hosting region, subprocessors, data-processing terms and safeguards for transfers outside the EEA require controller verification and publication. No claim of EU-only storage or complete security is made.
11Automation and updates
The Playground guard is a simulation. Ricursor processes project context, not a system designed to make legally significant decisions about people. This notice will need updating when real agent processing, optional tracking or new providers are enabled.