ETNET Co., Ltd.
Privacy notice
Updated: 2026-11-13
This notice covers the setup plugin and the provider’s information/support. Contact the relevant personal Site’s administrator about its operation.
Provider and scope
ETNET Co., Ltd. provides the Relay setup workflow and application source. This notice covers the setup plugin, the provider’s Relay information pages and support inquiries. It distinguishes those activities from operation of a personal Site in a user’s account and processing by hosting providers.
User-owned storage
Initial setup provisions a dedicated Site, R2 file store, D1 database and encryption key in the user’s Sites account. The distribution contains no provider files, transfer history, keys, sessions or user IDs. Files are not sent to a shared transfer database or relay service. Setup does not automatically grant ETNET editing access or an encryption key.
Data used by a personal Site
A personal Site uses the caller’s Site-scoped ID and display email for authentication and ownership. Files, names, sizes, creation and expiry times, sharing status and download-start counts support sharing and quota management. Download passwords are stored as a salted verification hash and separately encrypted recovery data in D1. Short-lived receiver and workspace grants are stored as hashes. Hashed share/connection information, attempt counts and timestamps limit repeated password attempts.
Model-visible information and secrets
Setup may use a Site ID, endpoint and the caller’s Site-scoped ID in the conversation. Asking for transfer history can return the owner’s file names, sizes, statuses, expiry times and active share URLs to the model. File contents, download passwords, encryption keys and workspace tokens are not included in ordinary model-facing results. Enter download passwords in the personal Site’s UI and do not reuse another service’s login password.
Recipients and hosting providers
Anyone given the share URL and password can retrieve the file from the user’s personal Site without Codex or ChatGPT sign-in. Sites and its hosting infrastructure process information for authentication, storage, delivery and operation. OpenAI’s processing of conversations and plugin execution is also governed by the user’s agreement, settings and OpenAI policies. Japan-only storage and end-to-end encryption are not guaranteed.
Retention in a personal Site
Shares expire 1 hour, 24 hours, 3 days or 7 days after creation. Expiry blocks new authorization and download starts. Files are deleted in batches during history/new-transfer requests or maintenance; each Site configures its own schedule and failed deletions are retried. File names, sizes and dates remain in history for 30 days after successful file deletion, then are hidden from retrieval and physically cleaned up in batches. Physical deletion is not instantaneous at the deadline. Receiver access expires within 15 minutes, workspace access within 30 minutes, and expired management records are cleaned up later. The language-preference cookie lasts one year.
Support records held by ETNET
Names, reply addresses, inquiry content and correspondence submitted to ETNET support are used to respond and review the support history. Ordinary inquiry records are retained for one year after the case is closed, then deleted. Do not send file contents, passwords, encryption keys or sign-in credentials. This period is separate from file and history retention in a personal Site.
Access for support
ETNET limits any access to user file contents to an explicit user request or legally necessary handling. Routine maintenance uses expiry, status and counts without reading contents. For an explicit request, the identity, target, purpose and necessary scope must be confirmed; any required access is granted through a method controlled by the user. Contacting support does not automatically transfer Site permissions or keys.
Controls and platform records
Senders can revoke a share and delete its stored file from their history. A user manages or deletes the entire Site/account through their own Sites settings. Recipient-saved copies and downloads already in progress cannot be recalled. Hosting operational logs may include IP addresses, URLs, times and HTTP status. Provider logs and backups follow the relevant provider’s settings and agreements; the 30-day and one-year periods here do not promise identical retention or immediate complete erasure across that infrastructure.
Contact
Use https://www.etnet.co.jp/contact/ for Relay help, data-handling questions and abuse reports. Include “Relay” in the subject or message. The same contact point handles questions about accessing, correcting or deleting support records held by ETNET.