What we do with personal information.

The Algorithmacy Conference is convened by Roger Hunt and hosted by the Caribbean Emergence Institute in Port of Spain, Trinidad and Tobago. Studio is a separate service on the same site, offered under the name Algorithmacy: an engineer sets up agents for an owner-run office and manages them. Registering for the conference does not start a Studio engagement, and a Studio inquiry does not register you for the conference.

Conference questions, including a request about a submission or a registration, go to rhunt@bentley.edu. A Studio inquiry, and a request to delete a Studio inquiry, goes to topanga@algorithmacy.org.

The form at the bottom of /studio collects the office type (and whether you want the office engagement or other work), your name, the business, your email, a phone number if you give one, and the chore or message. It also records that you agreed to the terms and to this notice. The form does not send unless that box is checked. A hidden field is there for spam. If that field is filled in, the note is discarded and nothing is sent. The server also ignores a form that is submitted too quickly, or too often, so automated posts are less likely to get through.

We use what you submit only to respond and to follow up about the Studio service. We do not sell it, and we do not add it to a mailing list. The same note is stored as a lead in Firebase when that store is configured. Sending the form does not create a contract.

The form is emailed to topanga@algorithmacy.org from this site, through Hostinger Email. Your email address is written at the top of that message, because that is how we reply. There is no separate form company in the middle. You can send the same note yourself by emailing that address. The email link under the form only opens your own mail program. This site does not receive that copy unless you send it.

Clients of the Studio engagement can sign in at /portal. Sign-in is by an email link, or with Google, through Firebase Authentication. We keep the account that was invited: the office name, the kind of office, the email addresses of the people on it, meetings, the record of what the agents did (including the drafts they wrote and who approved them), approvals, and the changes you asked for. A draft can contain client information, and that draft is stored in the portal. Client files themselves stay in the office’s own systems and are not copied to the portal. A booking from /book stores your name, email, business, the time, and an optional note, and emails you and Roger through Mailgun, with a calendar file attached.

Payment, when an engagement goes ahead, is taken by Stripe. We store Stripe’s customer and subscription ids so the portal can show whether the monthly charge is on. Card numbers stay with Stripe. Stripe’s notice applies to the payment page.

The sign-in is remembered in this browser so you stay signed in. That is the session, not an analytics cookie. The cookie notice says so.

The form at /submit collects the title, authors and affiliations, a contact email, the submission type, the track, keywords, the abstract, an outline, author bios, a contribution statement, a conflict statement, and a special-session note if you add one.

We email a one-time confirmation link to that contact address through Mailgun. Until you confirm, the submission is held in Upstash Redis for one hour and then deleted. We do not publish it before you confirm.

When you confirm, the submission — including the contact email — is published as a pull request on the public GitHub repository rogerSuperBuilderAlpha/algorithmacy-conference. Reviews are public and signed. There is no anonymized stage. That is the intake the conference describes on the submission page.

We also store a hash of the contact email, not the address itself, so a later submission from the same address can update that pull request. The address itself remains in the public pull request. A separate rate-limit record, also a hash of the email, and a short-lived record of the IP address, expire after one hour. They exist to slow repeated form posts.

Register Now leaves this site and opens a form hosted by Jotform. We do not run that form on this server. Jotform collects what you type there, and we receive the responses in order to register you for the conference. Conference fees are not yet set on this site, and the conference pages do not take payment. Jotform’s own privacy notice applies to the form platform. A Studio engagement, if you go ahead after a call, is paid in the portal through Stripe, as described above.

If you email either address above, we keep the correspondence so we can answer it. The site is hosted on Vercel. Logs for the form endpoints can include the IP address and the time of the request. We use those logs to operate the site.

This site does not run analytics and does not use advertising cookies. The conference pages do not ask you to create an account. A Studio client account exists only after an invite. The cookie notice says what that means in the browser. This page does not claim a privacy or security certification.

An unconfirmed submission expires after one hour. Rate-limit records for paper submissions expire after one hour. A published pull request stays public for as long as the repository keeps it. A Studio inquiry stays in the mailbox at topanga@algorithmacy.org, and in the lead record, while the conversation is open. The Studio form also keeps a short-lived count of recent submissions, in the server’s memory, to slow repeats. That count is not the inquiry itself. A client account, its meetings, and the agent record stay while the engagement is open. A ten-minute hold on a booking time expires on its own.

Mailgun, Jotform, GitHub, Upstash, Vercel, Hostinger, Stripe, and Firebase keep their own logs under their own rules. We do not control those retention periods, and this page does not restate them.

Email rhunt@bentley.edu for conference information. For a Studio inquiry, email topanga@algorithmacy.org. You can ask what we hold, ask us to correct it, or ask us to delete it. A request to delete Studio form data goes to that same Studio address.

We will delete or correct what we still hold: a pending submission, a rate-limit record, a mailbox thread, a registration response we received, a Studio lead, or a client account you ask us to close. Email roger@algorithmacy.org for a Studio account. A pull request that is already public is different. We can close it or edit what we control. Forks, review comments, and GitHub history can remain. We will tell you when that is the case. Stripe and Firebase may keep their own records after we delete ours.

The conference and Studio are not directed at children. We do not knowingly collect information from anyone under 16. If we learn that we have, we will delete it.

If this notice changes, the date at the top of the page changes with it.