How your data is handled

Your account and private collection

Clerk handles sign-in. Convex stores application records and uploaded evidence. Account records include an authentication identifier, your handle, display name, profile information and saved links. Your collection can contain product relationships, notes, dates, costs and supporting evidence.

Private collection access is tied to your signed-in identity. Evidence records can include source URLs, original uploads, message metadata, observations, excerpts and capture history. These records are stored by the service; they are not kept only on your device.

Connected sources

Connecting Gmail grants read-only Gmail access, a broader permission than the metadata the current reader requests. The reader requests message identifiers, timestamps and the From, Subject and Date headers. It does not request message bodies or attachments. These headers can contain personal information, and unmatched headers can be retained as private evidence.

New and reconnected mailboxes start with scheduled maintenance disabled. The collection provides controls for supported reads and maintenance. Saved mailbox credentials are encrypted by the application; this does not mean all stored evidence is end-to-end encrypted.

Supported activity connections can retain snapshots and their measurement periods. For example, the GitHub connection requests account information and a contribution calendar for a one-year period. A snapshot does not establish complete usage, every repository or all work performed.

What becomes public

Saving a collection and publishing it are separate actions. You select saved cards and details, review an exact preview, then approve publication. Visitors and browser agents can read the resulting public profile without signing in. Raw mailbox evidence and credentials are not part of that public profile.

Review your display name, biography and links as well as the cards in the preview. A display name may initially come from your sign-in identity, including an email address. Removing every public card can leave your public name, profile information and an empty collection visible; it does not delete the published identity.

Disconnecting and deleting are different

Disconnecting a mailbox removes its saved credentials and stops future reads through that connection. Existing private evidence, source history and relationship history are retained. Disconnecting locally does not revoke the grant in your Google account. You can separately revoke the app through your provider's account permissions.

Activity-connector disconnection removes the local saved secret and stops that connection's updates. Existing snapshots, relationships and published cards can remain. It does not establish that a linked provider account or its grant has been removed.

Deleting an original evidence payload does not erase all information derived from it. Observations, excerpts, source identifiers, hashes, provenance, relationships and published records may remain. A complete self-service account deletion workflow and automatic evidence-expiry schedule are not implemented. Disconnecting or deleting an original does not fully erase your data.

Services and browser storage

Product presentation can use Context.dev and official product sources. Brand lookups send the product domain to the branding service. Product images and fonts can load from external hosts, so visiting a page can make requests to those hosts.

Your appearance preference is saved in your browser's local storage. Authentication and hosting services also process requests and may use cookies and logs as part of their services.

Questions about your data

Contact Keegan Moody at 33@lecturesfrom.com about access, retained evidence or deletion. Describe what you need without sending passwords, tokens or private originals. The disconnecting and deletion section above explains what the application currently retains.

• Contact Proper Respect