Legal
Privacy Policy
Last updated
This policy explains how personal information is handled when you visit Ruqora, join the waitlist, use the guided preview or access the research application. The information involved depends on the features you use.
1. Scope of this policy
Ruqora is operated by Salah Eddine Saadouni (“Ruqora”, “we”, “us” or “our”), an individual operator based in Poland, in the European Economic Area (EEA), and the controller responsible for the personal information described in this policy. This policy covers the Ruqora website and crypto research application, including early-access registration.
External websites, social communities, authentication providers and blockchain services have their own privacy practices. This policy covers Ruqora’s use of information received from them; it does not govern their independent activities.
2. Information you provide
We process information you choose to submit through the features available to you. This can include:
- Waitlist and preview details: your name and email, optional crypto or memecoin experience, research goals, feedback, early-testing preferences and your choice about marketing updates.
- Account and profile details: identifiers, username, avatar and email made available when you sign in with Discord, together with your access status and account settings.
- Workspace records: watchlists, saved public wallet addresses and labels, alert and automation settings, and associated activity. Paper-trading features can store simulated balances, positions and trades.
- Research requests: searches, token identifiers, Agent messages and the conversation context submitted with a request.
- Correspondence and requests: information you send when asking for help, reporting a problem or exercising a privacy choice.
3. Technical and public information
Requests to the website and its services expose technical information such as IP addresses, browser and device information, request paths and response details to the infrastructure handling them. Authentication and preview services also process verification attempts, session identifiers, preview progress and timestamps to operate access and protect against abuse. Rate-limiting records use hashed identifiers derived from a network address or account-related identifier.
Ruqora retrieves token, market and public blockchain information for research. Public wallet addresses and on-chain activity may identify or relate to a person, especially when combined with an account, a label or other information. Saving an address in your workspace connects it with your account. Ruqora cannot remove records from a public blockchain.
4. How information is used
Information is used to provide and maintain the features you request and to support the operation of the service. These purposes include:
- Registering waitlist interest, managing access and invitations, verifying email ownership and maintaining authenticated sessions.
- Delivering the guided preview, saving its progress, enforcing usage limits and reviewing feedback to improve the experience.
- Saving workspace settings and research records, retrieving market information and generating responses to research requests.
- Sending verification and service messages, answering inquiries and sending marketing updates when you have opted in.
- Preventing unauthorized access and misuse, diagnosing service problems and handling legal obligations and requests.
5. Legal bases for processing
Under EEA data protection law, processing needed to register your interest, provide requested access, authenticate you, save your workspace and answer research or support requests is based on performing our agreement with you or taking steps at your request before entering it. We rely on legitimate interests in preventing abuse, securing the service and maintaining product reliability for related security records, diagnostics and proportionate feedback review, subject to a balance with your rights. Where a law requires us to keep or disclose information, the basis is that legal obligation.
Optional marketing communications rely on your consent. The waitlist marketing choice is separate from registration and is not selected by default. You may withdraw that choice through the preview account controls or by contacting us at the privacy address below. Withdrawal does not affect processing that was lawful before you withdrew consent, or necessary verification and service messages.
6. Agent messages and research services
When you use Agent, your prompt, relevant token identifier and limited recent conversation context are sent to Ruqora’s research service. Your account authentication token is checked with Supabase to authorize access. For responses that use an external model, Ruqora sends the question, recent context and selected token or on-chain evidence through OpenRouter to a model provider. Public wallet addresses may appear in that evidence or in text you submit. The current research flow retrieves token evidence from Ruqora’s data service; it does not send your question to a separate web-search service.
The model request is made by Ruqora’s server. It does not deliberately forward your account identifier, authentication token or browser IP address to OpenRouter. OpenRouter receives the server connection information, Ruqora application headers, request settings and submitted content. Identifying information included in your messages can still reach the model provider. The current Agent research request accepts text, not file uploads; older conversation features can store messages and attachments on the server.
OpenRouter and the providers it routes to have their own logging, retention, security and model-improvement practices. These depend on the provider, service terms and account settings. We do not promise that all requests receive zero retention or are excluded from model improvement. See the provider information linked below.
The application also saves Agent threads in browser storage. Clearing that storage removes the device’s copy, not records held by a service. Ruqora records operational information such as request status, timing and model usage. The current research endpoint does not write conversation messages to its database, but this does not describe all conversation features or infrastructure logs. Avoid submitting private keys, recovery phrases, passwords, confidential material or unnecessary personal information. Generated responses can be wrong, including about people or wallet relationships.
9. How long information is kept
The applicable retention period depends on the information, why it is needed to provide and secure the service, and any record-keeping, legal or dispute-related requirements. Waitlist, marketing-choice, preview-progress, feedback and account records do not currently have a general automatic expiry. They may remain until removed through available controls or a manually handled deletion request. Signing out or letting a credential expire does not erase those records.
Verification challenges and code-send records become eligible for cleanup after 24 hours. Cleanup runs intermittently when the verification service is used, so removal is not guaranteed at that time. Rate-limit records also have an age-based cleanup that runs intermittently. Older server-stored conversations have cleanup based on seven days since their last update, run when that service starts; this is not a guaranteed seven-day deletion deadline or a statement about backup copies.
You can request deletion using the privacy email below. A preview deletion request is recorded for processing; submission does not itself erase associated records. Requests require review and handling, and some information may need to remain for a specific legal obligation, security investigation or dispute. Browser history and preferences have no automatic time-based expiry and remain until removed by the application or your browser controls. Public blockchain records remain outside Ruqora’s control.
10. Security and international processing
Ruqora uses access controls, protected sessions and verification mechanisms to restrict access. Preview session tokens are stored as hashes, and verification challenges are protected rather than stored as readable codes in the preview database. These measures reduce risk but cannot guarantee that a website, device or service will never be compromised. Keep your account and device secure and do not share verification codes.
Ruqora operates from Poland and uses international service providers. OpenRouter describes processing in the United States and other countries; model-provider locations can also differ. Data protection rules may differ from those where you live. Transfers outside the EEA require an applicable legal basis for the transfer, such as an adequacy decision or appropriate safeguards. Contact the privacy address below to ask about the locations and safeguards relevant to your information.
11. Your rights and choices
Under EEA data protection law, you have rights to access your personal information, correct inaccuracies, request deletion, restrict processing and, where applicable, receive a portable copy. You can object to processing based on legitimate interests and withdraw consent for processing based on consent. These rights have conditions and exceptions. You may complain to a supervisory authority, including in the EEA country where you live or work or where an alleged infringement occurred. Other applicable laws may also provide rights.
The verified preview account page lets you update your name, goals and marketing choice and submit a waitlist deletion request. You can also email the privacy contact below for access, correction, deletion and other data-rights requests or privacy complaints. We may need information sufficient to verify your identity and understand the request. Do not send passwords, recovery phrases or private keys, and do not post personal account details in a public community.
Signing out ends the relevant session; clearing browser storage removes local data. Neither action alone closes an account or deletes server-side records. Market classifications and research responses are informational outputs and should not be treated as decisions about your legal rights or eligibility.
12. Children’s information
Ruqora is intended for people who can lawfully use the service and enter the agreement described in the Terms of Use. It is not directed at children. If you believe a child has provided personal information without the required authorization, contact Ruqora so the circumstances and any necessary removal can be reviewed.
13. Policy changes and contact
This policy may change as the service, its practices or applicable requirements change. The date at the top identifies the latest revision. Where the law requires additional notice or consent for a change, that requirement applies.
For privacy questions, data-rights requests or privacy complaints, email the privacy contact below. Share only the information necessary to handle your inquiry; public posts and community channels are not suitable for private account information.