Privacy

Privacy

Measuring visits

This page covers Pharo. Orama measures visits to this site and to its dashboard, and the reads and questions that agents make of a published business, with Umami, open-source web analytics. Orama runs Umami itself, on its own server, so the measurements are not sent to another company; this page names it so you can read how it works.

• Umami records which page was seen and which event happened, with the browser, operating system, device type, screen size, language, the country, region and city worked out from the IP address, and the campaign link. It sets no cookie and stores no IP address.
• To count a visitor once a day it keeps a hash of the visitor's IP address and user agent mixed with a salt that changes every day. Yesterday's hash cannot be matched to today's, and nothing in it identifies a person.
• When a link carries a campaign label (utm_campaign), it is kept in your browser tab until you close it, so a sign-up can be counted under the campaign that brought you. It is not kept anywhere else.
• Agents are counted the same way. When an agent reads a published business, asks it a question or calls a tool, Orama sends Umami the kind of read, the answer's outcome word and the business's public address, with the agent's user agent and IP address for the same daily hash. The question and the answer are never sent.
• Nothing identifies a visitor, so Orama asks for no consent for this measurement. Questions put to a business are a separate matter, covered by the subprocessors page.

What the browser sends

Each event carries at most four labels: whether the visitor is a person or an agent, which part of Orama it happened on, the campaign label, and (for a published business) its public address. Never a name, an e-mail address or the text of a question.

• page_view: A page is shown (Umami's own page view, sent with the properties; the dashboard sends one per navigation).
• landing_link_clicked: A visitor activates a measured link on the landing page; destination and placement are fixed labels, not its URL.
• signup_started: The sign-up page is shown.
• signup_completed: The first page after a finished sign-up is shown (once per browser tab session).
• source_added: The owner's website, Markdown file or pasted text was accepted.
• go_live: The owner confirmed Go live.
• release_live: The dashboard saw the release serving publicly after Go live (once per browser).
• first_question: The owner's first test question was put to the preview (once per workspace).
• returned_7d: The owner opens the dashboard 7 or more days after this browser first did (once per browser).

Umami's own answers about the data it collects, cookies and GDPR are at umami.is/docs/faq.