Last updated October 2, 2026
This privacy notice for SatsRail LLC d/b/a Eggtrail ("Eggtrail", "we", "us", or "our") describes how and why we collect, store, use, and/or share ("process") your information when you use our services ("Services"), such as when you:
Questions or concerns? Reading this notice will help you understand your rights and choices. If you do not agree with our policies and practices, please do not use the Services. You can contact us at hello.eggtrail@pm.me
This summary highlights key points; use the table of contents below to jump to details.
In short: We collect personal information that you provide to us.
There are two ways to use Eggtrail and they collect different amounts of information. Almost everybody who uses the Services is in the first group.
1. Playing a trail. Players do not create an account. To join a trail you type a team name, and that is the only personal information you give us. It may appear on that trail's leaderboard, which anyone holding the trail's link can read, so please do not use a full name if you would rather it were not shown. Alongside it we keep what your team did in the trail: which codes you found, when, and your score.
2. Writing or running trails. Organizers — staff at a school, library, museum or other venue — do hold accounts, and those accounts carry:
Sensitive Information: We do not process sensitive information. We do not ask for a date of birth, a photograph, an address, a phone number, or any information about a school or a class.
Payments: Playing is free, and no player is ever asked to pay. An organization that subscribes can pay by card through Stripe, our payment processor: the card form is Stripe's own hosted page, and card numbers never reach or pass through our servers. What we keep is the identifier Stripe assigns to the organization's billing relationship, never the card itself. Organizations can also pay by invoice outside the app, with no card involved.
All personal information you provide must be true, complete, and accurate, and you must notify us of changes.
In short: Our servers keep ordinary web request logs. Analytics is off unless a venue turns it on.
Like any web service, our servers record requests as they are served — including the IP address the request came from, the browser and the page requested. These logs exist for security and for keeping the service running, and they are held for a short period by our hosting provider.
We may also use a web analytics service to count page views. It is configured per deployment and is switched off unless the operator of that deployment enables it.
Advertising:
We run no advertising or retargeting tag on any page of this site.
Not on the marketing pages, and not on the trail board, the cards a player scans, the leaderboard,
the maps or any screen inside an organization's account. There is nothing here that builds an
advertising audience out of the people who read us, and a child scanning a code is never reported to
an advertising network by us. We do not sell personal information, and we do not share it for
cross-context behavioral advertising. This is checkable rather than a promise: open any page of the
site, view its source, and search it for
facebook
or
doubleclick
— there is nothing to find.
Location: We do not record where a player is. A trail may optionally ask a player's browser to confirm they are standing near a code before it counts, to stop a code's link being shared and played from elsewhere. When that setting is on, the browser answers a single yes-or-no question at the moment of a scan; the answer is used to allow or refuse that one action and is then discarded. On a GPS hunt, the hunt's map asks the browser for the player's position while the map is open, to show where they are and which stops are close; that position stays in the browser. Checking a stop sends it to us once, to allow or refuse that action, and it is then discarded. We keep only that the team reached that stop, so it can finish the card without checking again, and that goes when the team's progress is cleared. No coordinates describing a player are written to our records. Coordinates we do store belong to the codes themselves — the spot a venue's own staff chose when they hid one.
In short: To provide, improve, administer, communicate, secure, and comply with law. We may also process your information for other purposes with your consent.
In short: We share information only in specific situations and with specific third parties.
In short: Yes, we may use cookies and similar technologies to collect and store information.
Which cookies, how long each lasts, and how to refuse them are all listed in our Cookie Notice.
In short: A team and everything attached to it is deleted when the organizer archives the trail. Accounts last until you close them.
Teams. When the organizer archives a finished trail, every team that joined without an account is deleted, along with its name, its score and the record of the codes it found. A trail that is set to rank its board daily does the same thing every night. Deleting is triggered by the organizer rather than by a fixed clock, so a venue whose own policy requires a set retention period should tell us the period and we will run their trail to it.
Accounts. An organizer's account lasts until it is closed. Ask us and we will delete it.
Backups. We keep encrypted backups of the database for 30 days so the service can be restored after a failure. Information you have deleted can persist in those backups until they expire, after which it is gone. Server request logs are held for a short period by our hosting provider.
In short: Children play without an account, and a team name is the only personal information we get.
Eggtrail is built to be played by children, including on school trips and at parties, so this section describes the ordinary case rather than an exception. A child does not create an account and is never asked to. They scan a code, type a team name, and play.
For a player who joins this way we hold the team name they chose and what that team did in the trail. We do not collect or store:
Because a team name is free text, a child can type something that identifies them. We cannot tell. Organizers running a trail for children should say so when teams are being named, and can ask us to change or remove any team name.
We do not knowingly collect any other personal information from a child. If you believe a child has given us more than a team name — by typing it into a team name, or by creating an organizer account — contact us at hello.eggtrail@pm.me and we will delete it. A parent, guardian, school or venue may ask us to delete a team at any time, and archiving the trail deletes every one of them at once.
A plain-language version of this section, written for schools and venues assessing the Services, is at Accessibility and data .
In short: We aim to protect your information through organizational and technical safeguards, but no system is 100% secure.
Transmission of personal information is at your own risk; only access the Services within a secure environment.
In short: You may review, change, or terminate your account at any time.
If you are in the EEA/UK and believe we process your personal information unlawfully, you may complain to your local authority: Supervisory Authorities
If you are in Switzerland, see: FDPIC
Withdrawing consent: If we rely on your consent, you may withdraw it at any time by contacting us (see Contact ).
Most browsers and some mobile OS/apps include a Do-Not-Track (“DNT”) setting. No uniform DNT standard is finalized, so we do not currently respond to DNT signals. If a standard is adopted, we will follow it and update this notice.
In short: Yes. California residents are granted specific rights under the CCPA/CPRA.
| Category | Examples | Collected |
|---|---|---|
| A. Identifiers | Contact details (name, alias), IP address, email, account name | YES |
| B. Customer Records (Cal. Civ. Code 1798.80(e)) | Name, contact info, education/employment, financial info | NO |
| C. Protected classification characteristics | Gender, date of birth | NO |
| D. Commercial information | Transactions, purchase history, financial details | NO |
| E. Biometric information | Fingerprints, voiceprints | NO |
| F. Internet or similar network activity | Browsing/search history, usage data, interactions with our site | YES |
| G. Geolocation data | Approximate location (e.g., IP-based) | YES |
| H. Audio/visual/thermal/olfactory, etc. | Images, audio, video created in business activities | NO |
| I. Professional or employment-related info | Job title, work history (applicants) | NO |
| J. Education information | Student records | NO |
| K. Inferences from other personal information | Profiles/preferences derived from collected data | NO |
Selling/sharing: We have not sold or shared personal information in the preceding 12 months and do not sell personal information.
Your CCPA rights include the right to know, delete, correct, and to be free from discrimination for exercising rights. You may also designate an authorized agent to make a request on your behalf.
In short: Yes. We will update this notice as necessary to stay compliant with relevant laws.
The updated version will be indicated by the “Revised” date and is effective when posted.
If you have questions or comments, email us at hello.eggtrail@pm.me .
You can submit a request by emailing hello.eggtrail@pm.me . We will consider and act upon any request in accordance with applicable data protection laws.