Privacy policy

This policy covers aswemaylearn.com and PredictOS, the invitation-only research bench at predictos.aswemaylearn.com, both run by As We May Learn, Inc. ("we", "us", "our"). PredictOS tests whether a change to a learner-prediction pipeline improves prediction, on de-identified learner data that partners provide under agreements with us.

What PredictOS keeps about you

Your account. Your email address; our sign-in provider's identifier for you and our own permanent one; your organizations, with your role and membership status in each; and your handle, old ones reserved for you after a rename.

Your agreement. The version and a fingerprint of the data-use text you agreed to, your address then, and the time.

The audit record. Every read of learner-level data and of results (cards, student work, probe views, flagged evidence, scorecards and comparisons), refused attempts included, with the time, what was read, the outcome, and your address or the token that read for you; and any pause on your reading.

Your work and tokens. The experiments, recipes, Runs, flags and components you create, with you as owner (a flag holds a reference, not the evidence), and each agent token's name, scopes and expiry, its secret only as a one-way hash.

Logs. The bench's own logs hold identities (your address or a token id), counts and timings, never learner records. The hosting provider keeps its own request logs, which include network addresses and browser details, for a short period set by its plan.

Only accounts from the earlier Google sign-in, before 17 October 2026, hold the name, picture link and Google account number Google sent, and an invitation-list entry with your address and who added it.

Cookies

Signing in sets one encrypted session cookie, holding your sign-in profile and tokens for 30 days or until you sign out, and a short-lived one during sign-in. No advertising or analytics cookies, and no tracking scripts.

Signing in with Google

If you sign in with Google, Google shares your email address, name and profile picture, if any, with our sign-in provider. We use the email address only for sign-in and your account record. Your name and picture stay with the sign-in provider and, encrypted, in your session cookie, not in the bench's database. We request no other Google access. Our use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. We share Google data only with the processors below. You can remove the bench's access in your Google Account's security settings.

The public site

Public pages set no cookies and run no analytics. The members area uses a shared password and a signed 30-day cookie, and your browser remembers the name you pick. A review service we operate keeps reviewer names and comments and shows them to other members; new reviews are switched off today.

How we use it

To sign you in, check your invitation, show what your access allows, keep the audit record, apply the read limits (telling the owner of any pause), credit your work and keep the service secure. We never sell your information, advertise with it or build profiles from it.

Who else handles it

Our processors, all in the United States: Vercel hosts the site and the bench, with their files and logs; Neon hosts the database; WorkOS runs sign-in, sends sign-in codes and invitations, and keeps your address, any name in your sign-in profile, your organizations and memberships; Amazon Web Services runs experiment Runs, holding a Run's de-identified inputs only while it runs; Anthropic, whose Claude models power the assistants that help us run and check the service; those assistants read log lines and the test copy, which can hold your address, and never learner records beyond counts.

People admitted to the bench see the work you create, with your address as its owner. On an organization's page, its leads and the bench's owner see each member's address, handle, role and status; other members see only counts. The bench's owner sees the audit record. We disclose information when the law requires it.

Where it is kept

In Vercel's Washington, D.C., Neon's US East and AWS's Northern Virginia regions (or another US region). Files sit in a private store with no public links, and every read of a learner record goes through the bench. A test copy, behind an extra sign-in, is used only for testing.

Keeping and deleting

We keep your account record and your agreement record while you are a member and after your access ends, as the record of who had access. Database backups are kept by our database provider for a short period.

You can see your own audit record on your status page. Write to info@aswemaylearn.com to ask what we hold about you, to correct it, or to close your account. On request we deactivate your account so it can no longer sign in, and we remove your handle from display; the audit record of your reads is kept, because it is the record of access to de-identified learner data.

Minors

The site and the bench are for adults; we do not knowingly collect personal information from visiting minors.

Changes and contact

Changes are posted here with a new effective date, and a change to the data-use text asks for your agreement again. Contact: As We May Learn, Inc., info@aswemaylearn.com.