Mac ARM64 pilot · Google sign-in testing

Pilot account data use

fndry.sh pilot account data use. Contact: Wes Bailey, wes@parnotfar.com. This notice describes the current account-connected pilot.

Google sign-in requests only basic identity scopes: openid, email and profile. Google and Amazon Cognito authenticate the identity. The account service uses the provider identity, name and verified email to create or reuse your fndry account and show which account you are connecting. It does not request Gmail, Drive or contacts access. Google provider tokens are processed server-side for sign-in; they are not retained by the account service or sent to the CLI.

The account service runs on AWS in us-east-2. Cognito holds the federated user record. DynamoDB stores the account identity/profile, free Solo entitlement, pairing and session records. The account record has no automatic expiry. Pairing/sign-in flow records expire after ten minutes. Browser and installation sessions expire after thirty days; eligibility checks and retries retain the issued expiry rather than extending it. Expiry blocks use; it is not a promise of immediate deletion. DynamoDB TTL cleanup is asynchronous and the table has point-in-time recovery. Retained backups are not an immediate deletion service.

The account browser uses Secure, HttpOnly, SameSite=Lax cookies for sign-in and session continuity. The Mac installation stores its session in a device-local, nonsynchronizing Keychain item. Operational API/Lambda log groups have fourteen-day retention; API access logs record request identifiers, route/status and timing. The runtime avoids logging tokens, cookies, authorization codes and provider error bodies. Public release downloads separately produce retained private CloudFront access logs; their lifecycle is distinct from account-session expiry.

Google and AWS process the identity and service traffic needed for sign-in and account operation. Local Work files stay in your selected local workspace unless you separately authorize a transfer or an executor operation. Codex and other executors have their own accounts and data practices. This account sign-in does not itself grant repository, organization or billing access.

Signing out revokes the installation session online when reachable and retains protected revocation intent if offline. It does not erase account records, Work files, logs or backups. Contact Wes at the address for pilot data questions or removal requests; there is no self-service account-deletion command or promised deletion deadline in this pilot.

Installation · Account · Data use · Pilot use