Randomly privacy policy: what stays local and what is measured.
Randomly is browser-first: ordinary Entries and Winners stay in the current browser, while Cloudflare delivers the site and receives a deliberately narrow set of aggregate measurements. This notice separates what happens today from the additional controls required before any Google advertising can run.
Privacy summary
Randomly has no account system, student profile, email capture, or cloud Setup library. The site does not ask for a name, age, school, location, or payment details. Do not use an Entry as a place to store sensitive information. A facilitator controls the labels they enter, the local Setups they save, and every Shared Setup link they send.
Cloudflare receives network information needed to deliver and protect the site. Cloudflare Web Analytics and Randomly’s same-origin product events are active in production, but they are configured to avoid Entry text, Winner labels, exact Setup URLs, query strings, fragments, user identifiers, and exact screen sizes. Google AdSense remains governed by the fail-closed inventory and approval contract described below.
Entries, Winners, and saved Setups
Entries and Winners are processed by browser code on the device being used. Choosing a Winner does not upload the Entry list to a Randomly account because this release has no account or cloud-sync service.
If you deliberately save a Setup, Randomly stores its name, Tool, Template identity, Entry labels, enabled or disabled state, and repeat setting in this site’s localStorage. Up to 12 recent Setups can be stored. They remain on that browser until you delete them through the Tool or clear this site’s browser storage. Browser sync, backup, extensions, shared devices, and device-management tools are outside Randomly’s control.
What a Shared Setup link contains
A Shared Setup encodes the Tool configuration in the URLfragment after #. Browsers do not include that fragment in the ordinary HTTP page request, and Randomly removes paths, queries, fragments, and raw referrers from its product-event payloads.
The fragment is readable, not encrypted. Anyone or any device service that receives the complete link may read its labels. A copied link may also appear in messages, screenshots, browser history or sync, or third-party extensions. Use short neutral labels, share deliberately, and never place contact details, medical information, confidential notes, or other sensitive records in a Shared Setup.
Cloudflare hosting and measurements used today
Cloudflare hosts, delivers, and protects Randomly. Ordinary network requests necessarily expose information such as the requested host and path, IP address, browser headers, timing, and security signals to Cloudflare under its terms. Randomly does not copy those raw request values into its product-event dataset.
Cloudflare Web Analytics measures page views and real-user performance. Cloudflare describes the service as collecting timing metrics rather than tracking individuals across customer properties. It does not log query strings. Cloudflare currently says unsampled beacon data is retained for seven days, then aggregated for longer-term storage, and the dashboard exposes the previous six months. These are Cloudflare’s current service terms, not retention periods controlled by Randomly.
Randomly also sends allow-listed events to a same-origin/api/events endpoint backed by Workers Analytics Engine. The event may contain the Tool and surface, Template identity, broad Entry-count and viewport buckets, reduced-motion status, a coarse source category, and an event-specific bucket such as Selection time or remaining Entry count. The endpoint rejects unknown fields. It does not accept free text, Entry or Winner labels, Setup names, full URLs, raw referrers, IP addresses, device identifiers, or exact screen dimensions as event fields. Cloudflare currently retains accepted Analytics Engine data for three months.
Product-event measurement stops inside Presentation Mode. An entry event can record that Presentation Mode began, and an exit event can record its broad duration bucket; Selections and other activity inside the projected session are not sent. Blocking analytics does not block or change a Tool result.
Cookies and advertising status today
Randomly does not currently load a Google ad tag or request a Google ad on any public route. It therefore does not set or read Google advertising cookies through AdSense today. Cloudflare Web Analytics is used for aggregate page and performance measurement and Cloudflare states that it does not use visitors’ personal data for that service. Saved Setups use browser localStorage; they are functional data chosen by the facilitator, not advertising profiles.
Google advertising is disabled on public inventory in this build. This status is generated from the same fail-closed inventory and approval contract used by the site, rather than inferred from the Privacy page itself.
Controls required before future AdSense advertising
Before any public route can request Google AdSense, Randomly requires an approved account and site, authorized ads.txt, a real publisher and slot identity, exact route approval, audience and age treatment, category controls, privacy review, consent readiness, and dated owner approval. Legal pages, Shared Setup URLs, Presentation Mode, and active Selection, result, and history states remain outside advertising. Classroom Templates are suppressed in the current manifest and require a separate audience, child-safety, policy, and owner decision before that treatment could change.
Google requires publishers to disclose that advertising can involve cookies, web beacons, IP addresses, or other identifiers. If AdSense is activated, Google and selected ad technology partners may receive the page URL and IP address, use cookies or similar technologies for ad delivery, measurement, fraud prevention, and—where permitted and chosen—personalization. Read how Google uses information from partner sites and manage Google personalization through Google Ads Settings.
For visitors in the EEA, UK, or Switzerland, activation requires a Google-certified consent management platform integrated with the IAB Transparency and Consent Framework. Randomly’s ad runtime does not call Google’s tag when Purpose 1 consent is required but absent. The final CMP, vendor list, purposes, retention disclosures, withdrawal link, and regional behavior must be published and tested against the exact production configuration before advertising is approved.
Children and classroom use
Randomly is written for an adult teacher, host, or facilitator to set up and operate. A student does not need an account and is not asked to submit a name, email address, age, school, or profile. Facilitators should use neutral labels where possible, avoid sensitive student information, and follow their institution’s rules.
Classroom Templates and Presentation Mode do not request ads in the current product. Randomly does not use classroom activity to build an advertising profile. Any future change to classroom treatment would require a separate child/teen, consent, audience, category, privacy, and owner review; Presentation Mode remains ad-free. Report a concern without including a student name, Entry list, or Shared Setup link.
Purposes, providers, and international processing
Browser storage restores a Setup on the same device. Cloudflare delivers and protects pages, measures page performance, and stores the allow-listed aggregate product events. These services help keep the Tools reliable and show whether core actions work across broad device and referral categories.
Cloudflare may process information in countries other than yours under its contracts, privacy notice, and transfer mechanisms. Google is not an active advertising recipient in the current build. If that changes, Google and the final CMP/vendor list will be identified in this notice and consent interface before activation. Randomly does not sell Entry lists or create student profiles.
Your choices, requests, and contact
You can use a Tool without saving a Setup, delete saved Setups inside the Tool, clear this site’s localStorage, avoid sharing a Setup link, block optional measurement, or stop using the site. A Tool remains usable if measurement is blocked. Because ordinary Entries and saved Setups remain on the device, Randomly normally cannot find or delete them remotely.
For a privacy, access, deletion, correction, objection, child-status, or provider question, email hello@tryrandomly.com or use the Contact page. Requests are assessed according to the information Randomly actually controls and any applicable obligation. Do not include student names, Entry lists, or Shared Setup contents. You can also read the Terms of Use, About Randomly, and randomness explanation.
Source checks and changes to this notice
The operational descriptions above were checked on 31 August 2026 against Randomly’s production network behavior and source code, Cloudflare Web Analytics collection documentation, Cloudflare Web Analytics retention documentation, Workers Analytics Engine limits, Google Publisher Policies, and Google’s TCF integration guidance. Vendor services and rules can change, so these claims must be checked again before analytics or advertising configuration changes.
Randomly may update this notice when the Tools, providers, inventory, or legal requirements change. The effective and last-updated date below will change with a material revision. This plain-English notice describes current product behavior; it is not a promise of legal compliance in every jurisdiction and does not replace owner/legal review.
Effective and last updated: 31 August 2026. Randomly is an independently operated project. Privacy contact: hello@tryrandomly.com.