Privacy & cookies

Last updated: 11 October 2026.

Who is responsible

Controller name

Vincenzo Emanuele Carusotto

Country

Italia

Privacy email

rozdb.privacy@gmail.com

Accounts and price alerts

Signing in with Discord provides RO Market DB with your Discord identifier, username and display name. We record your latest sign-in time to operate your account. Price tracking stores the item configurations you choose, alert status and notification delivery information, including Discord messaging identifiers. These service records are separate from usage statistics.

You can stop tracking from the item page or your tracked-items list. Logging out ends the local session; it does not delete the account or its service records. Use the privacy contact above to request access, correction, erasure or an explanation of retained records.

Account records remain while the account is used or until an erasure request is resolved; no inactivity deletion is currently automated. Daily maintenance removes explicitly disabled alert configurations and their delivery records after 30 days, following a fresh recovery-verified backup. Active and delivery-blocked alerts are excluded. Historical paused records use their last update as a conservative starting date; new disablings have an explicit timestamp. Erasure requests are reviewed manually, including cancellation of notifications and removal or anonymisation of contributor links where compatible with preserving public market observations. Any legally necessary exception is explained to the requester.

Public market observations

RO Market DB displays item configurations, prices, observation dates and source information. Public market source material can contain seller names or other identifiers. Where an observation is linked to a contributor account, that association is a service record and is not added to usage statistics. Contact the controller about personal information appearing in an observation or source.

Aggregate usage statistics

We count successful page requests across the site, as well as explicit searches, item-link openings, selected catalog controls, “I like this” clicks and successful tracking enables. Page views also have aggregate UTC hour buckets, collected only from the hourly release onward; no earlier hourly traffic is reconstructed. Counters contain the UTC day, optional hour bucket, event type, a catalog item identifier when applicable, a permitted page group or category and a count. Search statistics contain only a canonical item identifier when recognised and a result-count band; they do not contain the words you searched for.

These counters do not store IP addresses, Discord identifiers, browser hashes, full URLs or individual navigation histories. Repeated actions count separately; the figures do not represent unique people. Page views are counted on the server without analytics cookies or JavaScript, including repeat visits and reloads. Known bots, prefetches, background requests and the admin panel are excluded; automated-client exclusions are approximate. Explicit browser-action counters require JavaScript; hover and polling do not increment them.

Aggregate counters cover the current UTC day and the preceding 89 UTC calendar days. Daily maintenance deletes older buckets after verifying recovery of a fresh backup. A failed recovery check or busy production lock postpones deletion until the next successful run; older buckets remain excluded from displayed statistics while waiting. Search and filter counters may be missing when a request or JavaScript fails.

Cookies and local storage

For RO Market DB's own traffic statistics and site optimisation, we estimate daily unique browsers using a common day flag, not a unique visitor identifier. __Host-rozdb_daily_count contains a version, UTC date, pending/counted state and a deterministic signature; its value is identical for every browser in the same state on that day. It is HttpOnly, Secure and SameSite Lax, restricted to this host, and expires at the next midnight UTC without sliding renewal. A visible public page first requests the pending flag; the server increments one aggregate daily total only when a JavaScript acknowledgement returns that flag, then marks it counted. No per-browser record, IP, user agent, page, query, account or advertising association is stored for this estimate. Technical security logs remain separate as described below.

This narrowly scoped first-party aggregate statistic is treated as an analytics cookie assimilated to technical cookies under the Garante's cookie guidance; it does not rely on advertising consent. It is not a record of individual browsing. Blocking cookies or JavaScript, leaving before acknowledgement and browser exclusions can cause undercounts. Cookie deletion, private browsing, devices, concurrent requests and replay can cause overcounts; known-bot exclusions are approximate. It is an estimate, not a complete count of people or distinct browsers. Expiry does not subtract from anonymous daily totals, which follow the aggregate retention policy above.

Daily estimate preferences on this page lets you exclude this browser for 180 days or resume the daily aggregate estimate. A valid saved exclusion or legacy refusal is respected. The previous optional implementation did not persist refusals, so past deleted choices cannot be recovered. __Host-rozdb_daily_count_off stores only a shared excluded flag, common expiry date and signature, without a visitor identifier. Already aggregated contributions cannot be identified and removed individually. Access to the site is unaffected.

_rozdb_items_session is used for session security and Discord sign-in, with an expiry of seven days. It is HttpOnly and SameSite Lax, and is Secure on the HTTPS production service. Security requests can create this session cookie before sign-in. Usage counters do not use it as an analytics identifier.

The retired rozdb_activity and rozdb_browser_visit cookies are deleted when a browser next contacts RO Market DB. Optional random-identifier browser collection, its consent interface and its online/day counters have been removed. Daily maintenance removes any remaining live permission and visit records from the retired systems after a recovery-verified backup. These records are not collected again or used by current statistics. Copies can remain in retained recovery backups under the backup policy below. The installed web app can cache static assets on your device; this storage is not sent as an analytics identity.

The private admin dashboard shows page views, hourly page views and daily history as aggregates. No tracking consent is requested for these counters, which do not use an analytics identifier on your device. The daily browser estimate uses the shared day flag described above. The catalog, accounts and alerts remain available after exclusion. No individual navigation history is recorded.

Technical logs, providers and support payments

Hosting is supplied by OVH S.r.l., Italia. The production VPS is located in Gravelines, France (region os-gra6). OVH Standard automated backups are active, separately from the application database backups. The Standard service uses replicas in the same data centre on separate servers. The OVH data-processing agreement, version 17 October 2025, was confirmed in the account on 29 June 2026.

The hosting infrastructure necessarily receives connection information, including IP addresses and requested addresses. Query parameters are filtered in Rails application logs, but infrastructure access logs require separate configuration and retention controls. Browser-local caches and historical backups are not covered by deletion of live aggregate rows.

Application and shared reverse-proxy container logs rotate at 10 MB per file, with at most three files per container. Retention therefore depends on traffic, rather than a fixed number of days. Proxy logs can include IP addresses, user agents, requested paths and query text. Rails parameter filtering does not remove these proxy records. Access is restricted to service administration; the shared proxy also serves other sites.

The adopted application-backup policy is 30 days for ordinary database dumps and associated bundles. Special recovery copies require review within 90 days; this is a review deadline, not an automatic deletion promise. Daily expiry automatically removes ordinary backup sets older than 30 days after verifying recovery of a fresh database dump and its evidence bundles. Deletion follows the next successful daily run; failed verification or a busy production lock postpones it. Special recovery copies are excluded, including explicitly protected sets. OVH Standard keeps one daily whole-VPS restore point for approximately 24 hours; the seven-day option is Premium and is not active. Erasure from live records does not edit existing backups. After a restore, previously completed erasure requests must be reapplied before normal service resumes; exceptional retention must be documented and restricted to recovery.

OVH S.r.l. (Italy) processes hosted service data under its data-processing agreement; the selected VPS is in Gravelines, France. Its agreement permits necessary remote access and uses applicable adequacy decisions or standard contractual clauses for transfers outside the EEA. Discord operates the external sign-in and messaging service under its own privacy policy. Stripe operates external support checkout and retains transaction data under its own policy, with controller or processor roles depending on the operation. Google provides the dedicated Gmail privacy mailbox; correspondence is handled under Google's consumer-service privacy terms, not a verified Google Workspace processing agreement. These external services can process data internationally under the safeguards described in their policies. Provider access does not mean that RO Market DB sells user information.

Provider information: OVH data-processing agreement, OVH VPS backups, Discord privacy policy and Google privacy policy. Contact the controller for information about applicable transfer safeguards.

The Support RO Market DB link opens Stripe’s external page for a one-time payment (suggested €3, minimum €1). Stripe’s payment terms and privacy policy apply there; RO Market DB does not collect your card details through this website. Payment-provider transaction records are separate from site usage counters. The controller may receive payment information in the Stripe dashboard. The owner-only admin reads confirmed payments for the RO Market DB support link through a restricted read-only Stripe API key. It displays only gross EUR totals and payment counts, before fees, refunds and disputes; this is not the Stripe balance. API responses can contain payer details, processed transiently to calculate the total; names, email addresses and individual payment records are not stored in RO Market DB. Only aggregate results and the successful-read time are cached for up to five minutes, separately from Discord accounts, usage statistics and advertising. Missing or failed reads are shown as unavailable, not zero. No Stripe SDK, embedded checkout, webhook or payment-status callback is installed on RO Market DB.

Legal bases and your rights

Requested account sign-in and price alerts are processed to provide the requested service (GDPR Article 6(1)(b)). Security, operational logs and necessary service administration rely on legitimate interests in protecting and operating RO Market DB (Article 6(1)(f)). Public market observations rely on the legitimate interest in providing verifiable market information, subject to correction, objection and removal of unnecessary personal identifiers. Aggregate counters contain no stored individual identifier; the processing needed to produce them relies on the legitimate interest in understanding site traffic and explicit use and improving the catalog. Page-view counters do not create or read an analytics identifier or individual navigation history. Handling privacy requests and any legally required payment records relies on applicable legal obligations (Article 6(1)(c)); other support-payment administration relies on the requested transaction or legitimate administrative interests.

You may request access, rectification, erasure or restriction, and where applicable object to processing or request portability. If processing relies on consent, you can withdraw it. You can lodge a complaint with your competent supervisory authority, including the Italian Garante per la protezione dei dati personali.

Write to the privacy email above. We normally respond within one month; if a lawful extension is necessary, we explain it within that month. We request only the information needed to verify the request. Discord sign-in data is necessary for accounts and alerts; you can browse the public catalog without signing in. Support payments are optional. RO Market DB does not make automated decisions with legal or similarly significant effects.

The retired activity, interest, like and optional-browser collections are no longer populated. Daily maintenance removes remaining live records after a recovery-verified backup. Retained backup copies are restricted to recovery and expire under the backup policy; they are not reused to identify visitors or reconstruct current statistics. After a restore, this retirement purge must be reapplied before normal service resumes.

Advertising

Advertising is currently disabled on RO Market DB. The site does not load Google advertising scripts, display ads or show an advertising consent message. Google Analytics is not installed. RO Market DB's aggregate statistics and daily browser estimate operate separately from advertising.

Any future activation requires a separate review of the actual advertising and consent behaviour and an updated notice before activation. No advertising identifiers are imported into RO Market DB statistics.

See the Terms of use for the limits of market observations, account features and voluntary support.