Privacy
Last updated: 14 November 2026
This page describes how PlaySonar (“we”, “us”) collects, uses and protects your information when you visit this site or book a call with us.
This site is a static page. It sets no cookies and runs no trackers or analytics. The fonts and the artwork load from this site itself, not from a third party.
Information we collect
- When you book a call: your name, your email, and your answers about your game, your players and your research question.
- When you write to us: your email address and what you write.
- Log data: like any website, the service that hosts this site may keep standard logs (IP address, access times and referring URLs) to operate and secure it.
How we use your information
We use the information we collect to:
- Prepare and hold the call you booked, and reply when you write to us
- Operate and secure this site
- Comply with legal obligations
We don’t add you to a list, we don’t pass your details on, and we do not sell your personal information.
Booking a call
The Start playtest button opens a booking page run by Google Calendar on our Google Workspace account. What you give there (your name, your email, and your answers about your game, your players and your research question) goes to Google and to us. We use it only to prepare and hold the call, and for nothing else. Google handles its part under Google’s privacy policy.
Third-party services
We use a small number of trusted services to run this site and our calls: Google Workspace for booking and email, and a hosting provider for the site. Each processes data according to its own privacy policy. We select service providers that maintain reasonable security practices; however, we are not responsible for the privacy practices of third-party services.
Game builds
When a game studio sends us a build for a study, we agree in writing beforehand where it is stored, who can see it, when it is deleted and whether it trains any AI. That agreement, not this page, governs the build.
Data retention and security
We keep booking details and emails only as long as we need them to talk with you. You may request deletion of your data at any time by contacting us.
We implement reasonable technical and organisational measures to protect your data, including encryption in transit (TLS). However, no system is perfectly secure, and we cannot guarantee absolute security.
Your rights
Depending on your location, you may have the right to:
- Access the personal data we hold about you
- Request correction of inaccurate data
- Request deletion of your data
- Export your data in a portable format
- Withdraw consent where processing is based on consent
To exercise these rights, contact us at team@playsonar.ai. We will respond within 30 days.
Children’s privacy
PlaySonar is not intended for anyone under 18 years of age. We do not knowingly collect information from children.
Changes to this page
We may update this page from time to time. The “Last updated” date at the top reflects the most recent revision.
Contact
Questions about this page? Contact us at team@playsonar.ai. See also our Terms.
Credits
The pond, the koi and every creature in the deep are drawn in code by our team. A few open-source pieces help it along, and their authors are credited here.
- The glyph-cell motion (the fixed-step loop, the follow-the-leader spine, wander and flee steering, the click splash, the wake field and the curl-noise current) is adapted from ascii-sharks by drewdi (github.com/stackedlol/ascii-sharks), MIT licence, Copyright 2026 drewdi.
- The fish schools in the deep follow the boids code by Ben Eater (github.com/beneater/boids), MIT licence, Copyright 2020 Ben Eater.
- The fonts are Young Serif, Atkinson Hyperlegible and Geist Mono, under the SIL Open Font License 1.1, and Departure Mono by Helena Zhang and Tobias Fried, under the MIT License. Their licence texts are in the fonts folder.
The full MIT notices are kept in the site's source files (pond.js).