The rules we follow
- Checking in takes only a name. No account, no email, no profile. If the host asked a question, the answer goes with the name. If they turned on presence checks, the phone's location or network is compared once and thrown away; only the result stays.
- Rooms auto-delete. A room and everything in it (names, times, answers, check results) is deleted when its timer runs out, within 24 hours. The one exception: a signed-in host's finished rooms stay in the room history on their own account.
- Hosts are anonymous unless signed in. A random id in a cookie is how we know which rooms are yours. Signing in, only needed for room history and classes, adds your email, and your name and picture if you use Google.
- Stats are totals, not people. We count rooms, check-ins and the like. Nothing in those counts says who, and nothing we keep about a browser holds a name.
- Nothing linked to you lasts more than a year. Every cookie we set and marker we keep expires within a year. A signed-in account, its room history and its classes stay until you delete them, or until 18 months without signing in.
- Data is not shared or sold. The only companies involved are our server's data center, Cloudflare, Google if you sign in with it, Paddle if you buy Pro, and Google and Microsoft ad tags on pages about hosting, never on room or check-in pages.
- Kids get the same protections. At any age, checking in takes only a name, in a room someone opened for them, and it's gone within a day.
- You can delete it. End a room or remove a name at any time. Signed-in hosts can delete sessions from their room history, a class, or their whole account.
Students and schools
Im Here! is used in classrooms, often with kids under 13, so a check-in collects as little as possible: a name typed into a room a teacher opened, deleted within a day unless the teacher is signed in, which keeps it in the room history on their own account.
- COPPA. Kids never make an account, and Im Here! never asks them for an email, phone number or address. Check-ins are used only to run the room and count how the app is used, never for ads or anything else commercial, and no ad tags load on room or check-in pages. A school using Im Here! for its own classes can consent in place of parents, as the FTC allows for tools used only for the school's benefit.
- FERPA. Attendance a school takes with Im Here! is the school's record. We handle it only to provide the service on the school's behalf, never sell or disclose it, and delete it when the school asks. Teachers can download it, and delete their room history themselves at any time.
- Parents. To see or delete what's held about your child, ask their teacher or school, or contact us at [email protected]. Usually nothing is left: rooms delete themselves within a day.
If your school needs a data privacy agreement, contact us at [email protected].
What we keep
- Rooms The PIN, start and end time, an anonymous host id, and for each check-in the name, time, answer and check results. Gone when the room ends, within 24 hours.
- Accounts Only hosts who sign in: their email, and with Google their name, picture and Google account id, used only for the account and never shared. A code to sign in by email is kept for 10 minutes, only as a one-way code. Finished rooms go into its room history. A class keeps its name, settings, roster (with any other names a person checks in as) and when its sessions opened. Names are encrypted. It also keeps the time zone, week start and clock you pick in Settings, and the date the account first reached each free plan limit. Kept until deleted, or after 18 months without signing in. Each sign-in notes the browser and device it's on (like Chrome on a Mac) and when it was last used, so you can sign one out from Settings. That goes when the sign-in ends, within 30 days.
- Cookies A random host id (30 days), an id per room you check in to (gone with the room), your sign-in (30 days), and a few small markers for counting, like which link brought you or whether this browser has checked in before. None holds a name, and none lasts more than a year.
- Counts Daily totals like rooms opened and check-ins, a marker per host id once one of their rooms reaches three check-ins (a year after their latest room), and host survey answers with no host id (1 year; answers in the home page's rating stay as its record).
- Bug reports The kind of page, browser type and country, plus the spot in our own code that failed. Every number, id, link and quoted value in the error is stripped before it's stored. 7 days.
- Abuse limits Requests per IP address (1 hour), and rooms open per network under a one-way code (until those rooms close).
- Your browser Your quick room roster, settings, the name you last checked in with, which free tools were already counted today, and, if you're not signed in, your room history. They stay on your device.
Presence checks
Hosts can turn on up to three checks. None ever stops anyone from checking in: names that don't pass are only marked for the host. A QR scan is read on the phone, and only whether the code was current is kept. Location asks permission first; the phone's position is compared with the host's once and thrown away, keeping only the result (and the distance in whole kilometres when it fails). The network check compares the phone's IP address with the host's; the phone's isn't kept, and the host's goes with the room. Hosts see results, never anyone's coordinates or address.
Ads
We advertise on Google and Microsoft. If you came from one of those ads, its click id stays in your browser for up to 90 days. If you open a room in that time and it reaches three check-ins, we tell that ad network the click id and when, nothing else (kept 90 days). Their tags, which set their own cookies, load only on pages about hosting, never on room or check-in pages, with ad personalisation off. Visitors in the EU, UK and Switzerland are asked first, and anyone can turn it off.
Companies involved
- Our server, rented from a data center in the United States. Everything we store lives there, and we run it ourselves.
- Cloudflare, which every request passes through, encrypted, to block attacks and keep the site fast. Its logs hold details like IP addresses and pages requested, and its Web Analytics counts page views without cookies. It also sends the emails with sign-in codes and contact form messages.
- Google, only if a host signs in with it.
- Paddle, only if a host buys Pro. Paddle is the merchant of record: it runs the checkout, takes the payment and handles sales tax, so card details go to Paddle and never reach our server. We keep what Paddle sends back to give your account Pro: the email used at checkout, the plan, its status and when it renews.
- Google Ads and Microsoft Advertising, only on pages about hosting.