Privacy Policy

1. Who is responsible

Ruqora is operated by Salah Eddine Saadouni (“Ruqora”, “we”, “us” or “our”), an individual operator based in Poland, in the European Economic Area (EEA). Salah Eddine Saadouni is the controller of the personal information described in this policy. Ruqora is not an incorporated company and has not appointed a data protection officer.

For privacy questions and requests, email the privacy contact below. External websites, social communities, authentication providers and blockchain services have their own privacy practices; this policy covers Ruqora’s own use of information, including information it receives from them.

privacy@ruqora.trade

2. Information you provide

Ruqora processes the information you choose to submit through the features available to you:

• Waitlist: your name and email address, optional crypto or memecoin experience and research goals, survey answers and feedback, early-testing preferences, and your separate choice about marketing updates. A one-time code is emailed to verify the address.
• Private beta access: your invitation and approval status, and the email address you use to request an activation email. Activation creates or links an account with our authentication provider, Supabase, which stores your email address, a password if you set one (stored by Supabase in hashed form) and sign-in records. Ruqora records your access role (for example beta).
• Discord sign-in, if you choose it: your Discord account identifier, username, avatar and the email address Discord shares.
• Workspace records: watchlists and the tokens in them, public wallet addresses you save and the labels you give them, and application settings.
• Research activity: token searches, token addresses and the pages you open, which your browser requests from Ruqora’s data service. Where the Agent is enabled for your account, your messages and recent conversation context (see “Agent and AI processing”).
• Correspondence: what you send when you email Ruqora for support, report a problem or exercise a privacy right.

3. Information collected automatically

Every request to Ruqora passes through Cloudflare, which hosts the website and protects it. Cloudflare and Ruqora’s servers process your IP address, browser and device information, the requested address, timestamps and response details to deliver pages, secure the service and diagnose problems. Rate-limiting records for sign-up, verification and activation use hashed identifiers derived from your network address or email address. Ruqora’s product API logs a request identifier, route, status and timing for each request; it does not log your IP address, account identifier or wallet addresses.

Ruqora does not use advertising trackers, tracking pixels or a browser analytics script. When the application is open, your browser also loads some content directly from other services, which then receive your IP address and browser information: fonts from Google Fonts, token images from the image hosts that token projects use (for example DexScreener’s image service or IPFS gateways), and your Discord avatar from Discord. The Cookie Policy describes cookies and browser storage.

Cookie Policy

4. Public blockchain information and wallet research

Ruqora’s research engine collects public information from the Solana blockchain and from market-data and indexing services: token creation and trading activity, wallet addresses, balances, transfers and timestamps. From this it derives research results such as creator and holder wallets, wallets that act together, tracked “smart money” wallets, token lifecycle states and risk classifications such as RUGGED or RUGGING. Some findings may be published by Ruqora, for example on its official social channels.

A wallet address is pseudonymous, but it can relate to an identifiable person, especially when combined with other information. This processing is based on Ruqora’s legitimate interest, and that of its users, in understanding public crypto markets and recognizing risk. Ruqora does not try to identify the people behind wallet addresses. A risk classification describes on-chain evidence about a token or wallet activity under defined criteria; it is not a finding that a particular person acted unlawfully or intended harm, and it can be wrong.

If you believe a wallet linked to you is processed or described inaccurately, or you want to object to this processing, contact the privacy address. Ruqora cannot change or remove records on a public blockchain, and other services can show the same public information.

privacy@ruqora.trade

5. Why information is used and the legal basis

Under EEA data protection law (the GDPR), each use of personal information needs a legal basis:

• Managing the waitlist, verifying your email, handling invitations, activating your account, signing you in, and providing the workspace and research features you use: performance of our agreement with you, or steps you request before entering it.
• Answering support requests and privacy requests: performance of our agreement, and our legal obligations for data-rights requests.
• Security, abuse prevention, rate limiting, diagnostics and keeping records of access decisions: our legitimate interest in protecting the service and its users.
• Reviewing feedback and survey answers to improve Ruqora: our legitimate interest in improving the product.
• Public blockchain research and published research findings: our legitimate interest, and that of users, in market transparency and risk awareness.
• Optional marketing updates: your consent, given separately from registration. It is not preselected.
• Keeping or disclosing information when the law requires it, and establishing or defending legal claims: legal obligation or legitimate interest.

6. Marketing updates and consent

Ruqora sends marketing updates only if you opted in. Verification codes, activation emails and messages needed to run your access are service messages, not marketing. You can withdraw marketing consent at any time through the waitlist preview account controls or by emailing the privacy contact. Withdrawal does not affect processing before it, and it does not delete your waitlist record.

Preview account controlsprivacy@ruqora.trade

7. Agent and AI processing

The Agent is an AI research assistant. It is currently available only to accounts the operator enables, not to every beta account. When you use it, your message, the relevant token address and limited recent conversation context are sent to Ruqora’s research service. Your sign-in token is checked with Supabase to authorize access. For model-generated answers, Ruqora’s server sends your question, recent context and selected token or on-chain evidence through OpenRouter to the model provider OpenRouter routes the request to. Public wallet addresses may appear in that evidence or in what you write.

Ruqora does not deliberately send your account identifier, sign-in token or IP address to OpenRouter. OpenRouter receives Ruqora’s server connection, application headers, request settings and the submitted content, so personal information you include in a message can reach the model provider. OpenRouter and the providers it routes to have their own logging, retention, security and model-training practices, which vary by provider and settings. Ruqora does not promise that requests are kept for zero time or excluded from model improvement.

Agent conversations are saved in your browser’s storage; the current research service does not save conversation messages in a Ruqora database. It records operational data such as request status, timing and model usage. Do not submit private keys, recovery phrases, passwords, confidential material or unnecessary personal information. AI answers can be wrong, including about people and wallet relationships.

OpenRouter privacy policyOpenRouter provider data practices

8. Service providers and other recipients

Ruqora does not sell personal information or share it for advertising. Information is processed by the service providers needed to run the features you use:

• Cloudflare: website hosting, content delivery, security and network protection, the waitlist database and secure connections to Ruqora’s servers.
• Supabase: account authentication, sign-in sessions and the account and workspace database.
• Brevo: delivery of verification codes and activation emails. Brevo receives your email address and the message, including any code or sign-in link.
• Discord: optional sign-in, if you choose it.
• Hosting providers of the virtual private servers that run Ruqora’s research engine, product API and Agent service.
• Blockchain and market-data services: Ruqora’s servers query blockchain nodes, indexing and market-data services for token and wallet data. When you view the portfolio for a saved wallet, Ruqora’s server sends that public address to a public Solana network endpoint to read its balances; your account details are not sent.
• OpenRouter and the model providers it routes to, only for Agent requests.
• Google Fonts, token image hosts and Discord’s image service, which your browser contacts directly as described above.

9. Legal disclosures and international transfers

Information may be disclosed where required by law or a valid legal process, or where necessary to investigate abuse, protect people and systems, or establish and defend legal claims. If the service is restructured or transferred, relevant records may be transferred subject to applicable privacy requirements.

Ruqora operates from Poland. Several providers above are based in, or process information in, the United States or other countries outside the EEA, where data protection rules can differ. Such transfers must rely on an adequacy decision (such as the EU–US Data Privacy Framework for certified recipients) or appropriate safeguards such as standard contractual clauses. Contact the privacy address for information about the mechanism that applies to a particular provider.

10. How long information is kept

Ruqora keeps information while it is needed for the purpose it was collected for, then deletes it unless it must be kept for a legal obligation, security investigation or legal claim. Ruqora has not yet set fixed retention periods for most records, so the honest current position is:

• Waitlist entries, marketing choices, preview progress and feedback, account and access records, watchlists, saved wallets and settings are kept until you ask for deletion, remove them yourself where a control exists, or Ruqora closes the related feature or service. They have no automatic expiry.
• Email verification codes are valid for 10 minutes; verification and code-sending records become eligible for cleanup after 24 hours. Rate-limiting records are cleaned up by age. These cleanups run intermittently, so removal is not guaranteed at an exact time.
• The waitlist preview session cookie lasts up to 30 days; signing out ends it. Supabase sign-in sessions last until you sign out or they expire. Ending a session does not delete your account or records.
• Server logs on Ruqora’s servers are rotated or overwritten as they age or reach size limits. Some web-server access logs are kept for about 14 days; application logs do not yet have a fixed period. Providers keep their own logs and backups under their policies.
• Agent conversations in your browser stay until you delete them or clear the browser’s storage.
• Public blockchain research data is kept as long as it is useful for research and risk history. Records on the blockchain itself are permanent and outside Ruqora’s control.

11. Your rights

Under the GDPR you have the right to access your personal information, have it corrected, have it deleted, restrict its processing, receive information you provided in a portable format where processing is based on our agreement or your consent, and object to processing based on legitimate interests, including the blockchain research described above. You can withdraw consent at any time. These rights have conditions and exceptions under the law.

To exercise a right, email the privacy contact. Ruqora may ask for information needed to confirm that the request is yours, and responds within one month, extendable where the law allows. There is no self-service account deletion in the application yet: deletion requests are handled manually across the waitlist, the account and workspace records. Copies in provider logs and backups are removed as those cycles run. If you joined the waitlist, the preview account page also lets you update your details and marketing choice and submit a deletion request; submitting it records the request and does not by itself erase records.

You can complain to a data protection supervisory authority, in particular in the EEA country where you live, work or where an alleged infringement occurred. In Poland this is the President of the Personal Data Protection Office (UODO).

privacy@ruqora.tradePreview account controlsUODO (Polish supervisory authority)

12. Automated classifications

Ruqora automatically classifies tokens and on-chain activity, for example HOT, WATCH or RUGGED. These classifications are research information about tokens and wallet activity. Ruqora does not make decisions about you that produce legal effects or similarly significant effects based solely on automated processing. Access to the private beta is decided by the operator.

13. Security

Ruqora uses encrypted connections, access controls, role checks for owner-only features, rate limits, hashed session and verification tokens, and authentication provided by Supabase. These measures reduce risk but cannot guarantee that a service, device or account will never be compromised. Keep your password and devices secure, and never share verification codes, private keys or recovery phrases. Ruqora will never ask for them.

14. Age requirement

Ruqora is intended for adults aged 18 or over and is not directed at children. If you believe a child has provided personal information, contact the privacy address so it can be reviewed and removed.

15. Changes and contact

This policy changes when Ruqora’s features, providers or legal requirements change. The date at the top shows the current version. Where the law requires notice or consent for a change, Ruqora will provide it.

For privacy questions, data-rights requests or complaints, email the privacy contact. Share only what is needed to handle your request, and do not post account details in public channels.

privacy@ruqora.tradeTerms of UseCookie Policy