Your data in this portal.

Signing in to Quaevera Labs

You can sign in with Google or Microsoft. Signing in alone does not grant access to the private catalog or applications. You must accept a valid invitation and receive administrator approval. We keep your provider’s verified account identifier in a private server session for up to eight hours. Google invitation acceptance additionally requires the verified Google email to match the invitation address. Once accepted, your membership is bound to that provider’s stable issuer and account identifier. We never link an existing tester membership to another provider just because the email matches. Use the same provider and account when you return. The explicitly configured owner can still use their Google-verified personal Gmail address to enter their existing active administrator account. We do not request access to Gmail messages, contacts or files.

Sign-in and invitations

We store the email address entered by your administrator, your sign-in provider’s issuer and account identifier, your access status and timestamps. Google or Microsoft handles sign-in and its own account data. We never ask for your provider password.

Invitation codes and session cookies are random credentials. Only their hashes are stored in the database. Short-lived Google or Microsoft sign-in state is stored server-side and removed after the sign-in attempt or expiration. Google and Microsoft access and refresh tokens are not retained.

Invitation emails

When the administrator chooses to send or resend an invitation, our email delivery provider, Resend, receives the recipient address and invitation message, including its private link. We use the existing shared email service operated for our projects. Resending creates a new link and invalidates the previous one. We retain the delivery attempt and whether the email service accepted it for 30 days; this does not confirm inbox delivery. We store invitation hashes, not message bodies or readable invitation links. Messages may remain with the provider and in recipient mailboxes after a link expires. The portal does not track email opens or clicks or automatically subscribe you to release announcements. Resend processes delivery information under its privacy policy.

Access reminders

The administrator can email an access link to a tester who has already accepted an invitation. This uses the same email provider and does not change membership, approve an account or create a new invitation. We keep the latest delivery reference, state and timestamp while the account exists to prevent duplicate or uncertain delivery attempts from being replayed. These records are erased with the account. Reminder audit events are retained for 30 days. No email opens or clicks are tracked.

Optional release announcements

You can opt in to selected major application release announcements in that application’s email preferences. Subscriptions start off. We use published GitHub release notes explicitly selected for announcement and send only to opted-in accounts with active access, for releases published after consent. Our email provider receives your address, the announcement and a private unsubscribe link. Every announcement includes an unsubscribe confirmation that works without signing in. We do not track opens or clicks. We retain your preference and consent timestamp while your account exists, plus a release/account delivery record to prevent duplicate messages. SMTP acceptance means the provider accepted the message; it does not confirm inbox delivery. Uncertain attempts are held rather than resent automatically. Unsubscribe credentials are stored only as hashes and remain valid while your account exists. Delivery records and unsubscribe hashes are removed when your account is erased. The source changelog and campaign record remain without your account details.

Connecting a companion

A browser connection request includes the display name supplied by your companion, a random comparison code, and a separate private device secret. Device secrets and comparison-code lookup values are stored only as hashes. The comparison code may also remain in your private browser session on this server while you sign in and consent. Device requests expire after ten minutes and are removed by regular maintenance. The browser never receives the companion device secret or its access token. After you approve, only the requesting companion can collect its new token, once. The new token replaces the previous companion connection for your account.

Access records and retention

We record invitations, approvals, revocations, companion connection approvals/declines, token issuance/renewal, download requests and successful run authorizations for 30 days. A run authorization records your account reference, the requested feature and the time; it does not prove that a computation started or completed. Companion tokens expire after seven days and only their hashes are stored. The companion renews its token at startup and once a day while running; each successful renewal invalidates the previous token. Request identifiers used to reject repeated checks are retained until their token expires, for at most seven days. A download request does not prove that a download completed. Expired sessions and invitations are removed by regular maintenance. Active and pending account records remain while participating in the beta; revoked accounts and expired, unaccepted tester invitations are removed after 30 days.

To limit repeated sign-in attempts and access checks, we retain a hash derived from the connecting IP address for up to ten minutes. Token-issuance limits retain a hashed account reference for up to one hour. The portal does not load third-party analytics, advertising cookies or third-party scripts. Its required session cookie expires after eight hours, or ten minutes before sign-in. Your hosting provider may also process connection information under its own policies.

File downloads

After checking your beta access, this portal sends you a temporary link to download the approved file directly from GitHub. GitHub receives your IP address and normal download request information. Your beta session, companion token and spreadsheet contents are not sent with that download. A copied temporary link can be used until it expires; revoking beta access prevents new links but cannot immediately withdraw a link already issued. Files already downloaded remain on the recipient’s computer.

Your files stay on your computer

This portal distributes the beta files and checks access for builds configured to require online approval. It does not receive spreadsheet cells, formulas, workbook files, calculation results or local certificates during calculations. You can explicitly share screenshots through feedback as described below. Desktop companion applications perform calculations on your computer. Its own privacy information describes that workflow.

Feedback you submit

Sending feedback from an application transmits the title and message you type, the active tab where you opened the form, and any screenshots you choose to attach to this portal. After checking beta access, we create an issue in the project’s private GitHub repository. The issue includes the contact email and account reference linked to your signed-in beta membership so the team can identify your report and reply. These details come from the authenticated portal account, not from text entered in the feedback form. Repository collaborators and authorized support automation can read them. Screenshots may contain spreadsheet contents or other information visible in the images you select; review them before sending. We do not automatically attach workbook files, cells, formulas, device details, provider identity identifiers or access credentials. Selected PNG or JPEG images are resized and image metadata is removed before upload to private GitHub attachments. The portal retains your account reference, a submission receipt, a content hash and the internal issue number for up to 30 days to prevent duplicates; it does not retain feedback text or screenshot files. Images are processed in memory and uploaded to GitHub; a failed multi-image upload can leave an attachment there without an issue. The feedback, screenshots, tab context and contact details remain on GitHub until removed by maintainers. Repository collaborators can read them. Contact the administrator with your receipt to request removal. Feedback rate limits retain a hashed account reference for up to one hour.

Your choices

You can sign out at any time. Contact the beta administrator to leave the beta or request removal of your account records. Removing portal access cannot erase files already downloaded to your computer.

Contact: gusmaogabriels@gmail.com

Google’s sign-in processing is described in its privacy policy. Microsoft’s sign-in processing is described in its privacy statement.