# DataVisitors > See where people came from, what they did, and what converted — on websites, apps, and servers. No cookies on visitors. Named people stay off until you switch them on. Public pages show totals. Software analytics. Know what happens in your software — without following anyone home. ## Pages - [Software analytics for websites, apps, and servers](https://datavisitors.com): See where people came from, what they did, and what converted — on websites, apps, and servers. No cookies on visitors. Named people stay off until you switch them on. - [How it works](https://datavisitors.com/how-it-works): Create a project, connect a site, app, or server, and read the dashboard the same minute. Goals, funnels, boards and people follow as you switch them on. - [Features](https://datavisitors.com/features): Dashboards, sources and technology; funnels, retention, segments, journeys and attribution; sessions, profiles and a live map; shields, privacy regimes, exports, public links and an audit trail. - [Pricing](https://datavisitors.com/pricing): Four plans from Free: events per month, retention, projects and seats, and the features each one switches on. The limits on this page are the limits the service enforces. - [Questions and answers](https://datavisitors.com/faq): How counting works without cookies, what a privacy regime changes, what happens past a plan's ceiling, what a public link shows, and how a visitor is erased. - [Security](https://datavisitors.com/security): The practices DataVisitors ships: aggregates-only public pages, secrets shown once and stored hashed, a read-only analytics store, two-factor authentication and an audit trail on both sides. - [Privacy approach](https://datavisitors.com/privacy-approach): What the tracker and the pipeline do with a visit: no cookie, a stateless start, a salt that expires every day, three privacy regimes, and export and erasure on every plan. - [Demo](https://datavisitors.com/demo): Click through the dashboard with no account: switch between labelled sample projects, change the range, and read pages, sources and locations. - [Contact](https://datavisitors.com/contact): Ask about measuring your product, a plan, privacy, or a security concern. ## Documentation - [Introduction](https://datavisitors.com/docs/introduction): What DataVisitors measures, how a workspace, a project and its keys fit together, and what the product deliberately does not do. - [Quick start](https://datavisitors.com/docs/quick-start): From an accepted invitation to your first recorded page view, in about five minutes. - [Core concepts](https://datavisitors.com/docs/core-concepts): Visitors, sessions, events, goals and time zones — the words the rest of the manual uses, and exactly what each one counts. - [Counting correctly](https://datavisitors.com/docs/counting-correctly): The six integration mistakes that make a dashboard lie, how each one looks in your data, and the rule that prevents it. - [Browser tracker](https://datavisitors.com/docs/browser-tracker): One script tag records page views, SPA navigation, outbound links, downloads and engagement — without reading a full URL or building a fingerprint. - [Custom events](https://datavisitors.com/docs/custom-events): Name the moments a page view cannot capture, attach the properties you want to break them down by, and identify a person when you have the right to. - [HTTP API](https://datavisitors.com/docs/http-api): The ingest endpoint every SDK speaks — one batch, one project, a per-event answer and never a silent drop. - [SDKs](https://datavisitors.com/docs/sdks): The native, server and framework SDKs, and the raw protocol every one of them speaks. - [CSV import](https://datavisitors.com/docs/imports): Bring aggregate page history from a CSV export or from Google Analytics 4, and what an import can never recover. - [Dashboards](https://datavisitors.com/docs/dashboard): Every card on the project Dashboard, the workspace Overview, and the boards you build yourself. - [Product analytics](https://datavisitors.com/docs/product): Funnels, retention, segments, journeys, attribution, and the properties your events carry. - [People](https://datavisitors.com/docs/people): Sessions one by one, the people behind them, and the switch that keeps both off until you decide. - [Share links](https://datavisitors.com/docs/sharing): Read-only links to the dashboard, a board, the full reports or the people map — what each one shows, how to protect it, and how to revoke it. - [CSV export](https://datavisitors.com/docs/exports): Take a copy of a project's events out of DataVisitors as CSV — what the file holds, how long the link lives, and what it deliberately leaves out. - [Query API](https://datavisitors.com/docs/api): Aggregate analytics over HTTP with a read key, the traits door, and the same questions through MCP. - [Projects and keys](https://datavisitors.com/docs/projects-and-keys): A project holds one site's data. Keys are how code reaches it, and each key does exactly one kind of thing. - [Allowed origins](https://datavisitors.com/docs/allowed-origins): An install key sits in page source where anyone can copy it. Three separate rules decide where a copy is still useful — and they behave differently. - [Goals](https://datavisitors.com/docs/goals): Count the visitors who reach one event or one page target. - [Alerts and webhooks](https://datavisitors.com/docs/alerts-and-webhooks): Be told when a number moves — by mail, or by a signed request to your own endpoint, with the delivery attempts on the screen. - [Shields](https://datavisitors.com/docs/shields): The ingest rules that refuse an event before it is stored, and the three rules every project gets. - [Account security](https://datavisitors.com/docs/account-security): A second factor on your own account, recovery codes, and requiring both of everyone in the workspace. - [Cookieless by default](https://datavisitors.com/docs/cookieless): What the tracker stores on a visitor's device, when it is allowed to, how a visitor is counted when it is not, and what a consent banner changes. - [Data removal](https://datavisitors.com/docs/data-removal): Erasing a person you identified yourself — who can ask, what the worker deletes, and what the finished receipt does and does not hold. - [Data and hosting](https://datavisitors.com/docs/data-and-hosting): Where your analytics data lives, how long it stays, and how it leaves. - [Error codes](https://datavisitors.com/docs/error-codes): Every refusal the ingest can answer with — the per-event codes inside a 202, the statuses that refuse a whole request, and which of them are worth retrying. - [Limits](https://datavisitors.com/docs/limits): The ceilings the ingest and the project settings enforce, the two rate budgets, and what your plan decides instead. ## Optional - [Full site content](https://datavisitors.com/llms-full.txt): Every page above, as Markdown, in one document.