DataVisitors is hosted. There is nothing to install, migrate, or operate: the application you sign in to renders every screen, and the analytics service at api.datavisitors.com receives every event.
Where the data lives
The analytics service is the only writer of analytics data. It keeps configuration — projects, keys, goals, shields, share links — apart from events, each in a store built for that job.
The browser tracker and every SDK post to https://api.datavisitors.com/api/event. The Query API answers at https://api.datavisitors.com/api/v1/query, and an assistant asks the same questions at https://api.datavisitors.com/mcp.
What is stored
An event carries the page path without its query string, the referrer reduced to its host, the campaign fields, a coarse country, the device class, the browser class, the operating system, the locale, the consent state, the SDK name, the custom properties, and — when the tracker collected them — the scroll depth, the engaged time and the click position. A raw IP address is never retained.
A visitor and a session are first-party random identifiers. A person's traits are the facts your own system sent with identify. The consent regime of the project decides whether a visitor's device holds an identifier at all; see Browser tracker for the regimes and the consent modes.
Retention
Retention follows the plan: 90 days on Free, 365 days on Starter, 730 days on Growth, 1,095 days on Business. The period is stamped on every event at ingest, so a change of plan applies to the events that arrive after it.
Collection does not stop past the monthly allowance. Every event is still accepted, counted and kept for the plan's retention. What a plan buys is the ability to read those events: past the allowance the analytics screens are replaced by a page that says so until the plan grows. Nothing is dropped and nothing needs re-sending.
Exports
Raw exports are requested from the project's Settings page, under Data & privacy, and served from inside the application. The file is prepared in the background; it stays downloadable for seven days. See CSV export for the columns and the row cap.
Erasure
A person's erasure is requested from the project's Settings page, under Data & privacy, or from the person's own profile on the People page. The service's worker answers it: it deletes the person's events and traits and keeps a hashed tombstone, never the key or a value.
Public pages
Public share pages show aggregates only. They never show a session, a visitor identifier, a profile, a workspace ID, or a project ID.