Privacy policy

1. This static site

The static files contain no forms, JavaScript, cookies, analytics, advertising technology, or third-party media. They do not collect information by themselves. When hosted, the hosting provider may process ordinary request data such as IP address, browser information, requested URL, and time for delivery and security. Those website-delivery records are not Yahoo mailbox data.

2. Data a future first version would process

Only after separate provider approval and the user's express authorization, a future first version is intended to process:

• Authorization data: Yahoo OAuth authorization limited to the mail-r read scope for IMAP, held outside model context, prompts, source files, ordinary logs, screenshots, and support artifacts. The pilot will not request mail-w, CardDAV, or CalDAV.
• Mailbox data: bounded message headers and a bounded raw MIME body fetched through Yahoo IMAP to classify potentially consequential mail in Inbox and Junk/Spam. A raw MIME body can include encoded attachment parts even though J.SCEW does not separately open or decode attachments.
• Operational data: nonreversible message-ID digests, timestamps, authentication summaries, provider checkpoints, classification result and reason codes, alert/acknowledgment state, and software/configuration version.
• Support data: information a user deliberately supplies in a support or privacy request. Users should not include passwords, OAuth tokens, or message contents.

J.SCEW is not intended to automatically open links, render active HTML, load remote images, or separately open or decode attachments. Encoded attachment parts contained in a fetched raw MIME body may pass through bounded transient memory and are subject to the same non-retention rule as the rest of that body.

3. Purposes and limits

The first-version purposes are limited to detecting potentially consequential messages, creating privacy-minimized local alerts, maintaining read-only recovery checkpoints, preventing duplicate processing, measuring reliability, providing support, and investigating security or service failures.

The first version will not sell mailbox data, use it for advertising or cross-service targeting, or use mailbox content to train general-purpose models. Any materially different use requires a revised notice and an appropriate authorization before it begins.

4. Disclosure and processors

The initial owner-only pilot is limited to first-party processing and local alerts on the owner's own computer. It will not routinely or voluntarily disclose Yahoo-derived message content, headers, relationship data, credentials, URLs, encoded attachment parts, classifications, or alert events to an external classifier, host, alarm provider, analytics service, logger, or support provider. Yahoo continues to process mailbox data under Yahoo's own terms. The static-site host processes only ordinary website-delivery data described above, not Yahoo mailbox data.

Adding any recipient of Yahoo-derived data requires this policy and the Yahoo application disclosures to be updated before that disclosure begins.

Data may also be disclosed when required by law or when reasonably necessary to protect users, the service, or others, subject to applicable law. Mailbox data would not be disclosed to third parties for their own advertising.

The owner-only pilot does not intentionally transfer Yahoo mailbox data across national borders or to a remote processor. Ordinary static-site request data may be processed by the site's hosting provider in locations where that provider operates; it is not Yahoo mailbox data.

5. Retention

• Raw message content: intended to remain transient in bounded memory and not be retained by default.
• Encoded attachment parts: may be present inside a bounded raw MIME body fetched through IMAP, but are not separately opened or decoded and are not retained by default.
• Operational records: retained for no more than 30 days unless a longer period is required to investigate a specific security or reliability incident or by law. Any exception must be access-restricted and documented.
• Backups: if used, encrypted and access-separated copies expire no later than 30 days after deletion from the active system.

No mailbox may be connected until the implementation enforces and has been tested against this schedule.

6. Security

The design uses least privilege, separate identities and scopes, bounded parsing, inactive treatment of message content, minimized logging, and user-controlled revocation. No system is perfectly secure, and offline tests do not establish live-service security or reliability.

7. User choices, access, and deletion

A future user must be able to disconnect J.SCEW and revoke provider authorization independently. An authenticated user may also request access to or deletion of J.SCEW operational records, subject to legal and security exceptions. The sequence is to revoke authorization, stop ingestion, delete checkpoints and operational records, and expire matched backups under the schedule above.

See Revoke access and delete data. Requests will be acknowledged and resolved within 30 days unless applicable law requires a shorter period or a disclosed legal or security exception applies.

8. Children and changes

J.SCEW is not designed for children and no public enrollment is available. If a service launches, material policy changes will be dated and presented before they apply where consent is required.

9. Contact

Operator: Van Neistat

Operator location: California, United States

Privacy contact: privacy@jscew.com

Review the support status.