Privacy

AdminIgloo LLC, trading as adminigloo, of the State of Utah, USA (full registered address available on request), is the controller of the personal data described below.

Write to dallinhumphrey@gmail.com about anything on this page, including a request to see, correct or delete what we hold.

Only what the service needs in order to work. This list is generated from the parts this service is actually built out of, so it does not describe features we do not have.

Your account

Your name and email address, held so you can sign in and so other people in your company can see who you are.

Your company

Which company you belong to, what you may do inside it, and any invitation sent to you or by you.

An audit trail

A record of administrative actions — who changed what, and when. It is kept deliberately, because the alternative is being unable to answer that question after a security incident.

Errors

When something goes wrong, the failure is recorded with enough context to reproduce it, which can include your account id and the page you were on.

Feedback you send

When you submit feedback through the widget: your description, an optional screenshot of what you were looking at (with sensitive form fields blanked before capture), your recent clicks on the page, and any browser errors from your session. On this site's marketing pages the widget is a demo: what you send is kept on a board tied to a random cookie that ends with your browser session, is shown only to that browser, and is not routed to our team. It stops being shown 24 hours after your last activity (48 hours after you started, at most) and is deleted — screenshots included — by the next daily cleanup after that.

Visits

When you visit this website we count the visit without cookies and without storing anything on your device: the pages you view (with any invoice, invitation or booking link code removed from the address), the website that linked you here (its name only, never the page), campaign tags on the link you followed, your country, the general kind of device, browser and operating system, clicks on our public pages and on a few labelled buttons elsewhere (never what you type), how fast pages loaded for you, and how long the page was in front of you. Your IP address and browser details are used only in memory, to make a code that recognises the same visitor within one day; the random ingredient of that code is deleted within two days, after which no visit can be linked back to anyone. Visits by search engines and AI crawlers are logged by page, with whether the request came from that company's published addresses. Totals — never anything about one visitor — are shown publicly on our homepage. Visit records are kept for 13 months and then deleted. If your browser sends Global Privacy Control or Do Not Track, nothing is counted; you can also switch counting off for this browser below.

Calls you book

When you book a call on our booking page: your name and email address, your phone number (needed only if you choose a phone call), your company and notes if you add them, the time zone you viewed the times in, how you chose to meet, the time you picked, and the campaign tag on the link that brought you, if there was one. We use them to hold the time for you, to send you a confirmation, a reminder before the call and a notice if it is moved or cancelled, and so the person taking the call knows who they are speaking to and how to reach you. Booking, moving and cancelling are recorded with when they happened, and our visit count (see Visits) notes that a visit ended in a booking, with nothing that identifies you. While a time is held for you, the hold also keeps a one-way code made from your network address, so that one visitor cannot hold many times at once; the code is removed when you book, and a hold you abandon is deleted by the next daily cleanup. The confirmation includes a private link that lets whoever holds it see, move or cancel the call, so keep it to yourself. Your booking is kept as the record of the call; it is not deleted automatically. To have it deleted, write to the address in "Who we are" from the email address you booked with.

The booking demo

The booking widget on our Book-a-call feature page is a demo, and a booking made there is not a call. It goes into a sandbox: a sample business's throwaway calendar, tied to a random cookie that ends with your browser session, and shown only to that browser. It never reaches our team, nobody is emailed (whatever address you type), and no real calendar is read. If you choose "Add sandbox event to Google Calendar" or "Download sandbox .ics", the event is created in your own calendar or on your own device, marked as a sandbox event that is not a real booking, and nothing is sent to us. What you type into it, such as a name, an email address, a phone number or notes, is kept only in that sandbox. The sandbox stops working 24 hours after it was made and is deleted, at the latest, by the first daily cleanup after that. Our visit count (see Visits) notes that a visit booked a demo call, with nothing that identifies you.

Orders

What you bought, when, for how much, and the reference Stripe gave the payment. Card details are not held here.

What your plan includes

Your subscription, its status, and the allowances it grants you — including how much of each you have used.

To give you the service you asked for, to keep it secure and working, and to meet obligations we cannot contract out of — tax records on a purchase, for instance.

Have a lawyer write this clause. Which lawful basis applies to which category is the question a regulator asks first, and it depends on where you and your customers are, not on how the software is built.

These are the companies that process data on our behalf. The list is generated from the services this deployment is built on, so it is complete for the software — add anything you have connected since, such as analytics or a support desk.

The rows marked optional are services this deployment can use and only does once they are switched on: Sentry, Upstash. Check which are configured here, and delete the rest of these rows from src/legal.ts.

Say where, and be specific. Each company above operates in particular regions and several let you choose. Name the regions you have actually selected, and say what covers a transfer out of them if there is one.

Set real periods here. “As long as necessary” is not a retention policy and does not survive scrutiny. Two things in this service outlive an account on purpose and should be named: the audit trail, which exists to answer questions after an incident, and any record kept for tax or accounting.

Depending on where you live you can ask for a copy of what we hold, ask us to correct it, ask us to delete it, or object to some of what we do with it. Write to dallinhumphrey@gmail.com and we will answer.

Check this against your jurisdiction. The rights, the deadline you have to answer in, and the regulator a complaint goes to all differ, and this paragraph names none of them.

When this changes we update the date at the top. If a change matters to you — a new company in the table above, a new purpose — we will tell you rather than relying on you re-reading this page.