Privacy Policy

Last updated: 2026-04-18

Editor Eye for Game Creators ("the Service") places the highest priority on protecting user privacy. This policy explains the scope, purpose, retention, and third-party disclosure of the personal information and transmitted data handled by the Service.

Note: this policy is a courtesy translation; in the event of any discrepancy, the Japanese version prevails.

1. Data we collect

The data collected by the Service is strictly limited to the following.

• Account information: the user identifier and email address provided by the OAuth provider (GitHub / Google).
• Transmitted data (Route A): the type, component names, and serialized field values of the selected GameObject in Unity Editor.
• Request logs: timestamp, plan, and license identifier (request bodies are not included; logs are automatically deleted within 24 hours).

We never collect your C# script bodies. Source code and logic are never transmitted. Other GameObjects in the scene, project files, and asset paths are also out of scope.

2. Retention period

Transmitted data and request logs are automatically deleted within 24 hours as a rule. Because the deletion job runs hourly, the operational upper bound is approximately 25 hours (aligned with planning doc §11.3 / §28.4). Account information (OAuth provider identifier and email address) is retained while the account remains active.

3. Third-party disclosure

The Service does not share collected data with any third party other than the following:

• Lemon Squeezy (Merchant of Record, powered by Stripe): payment processing and subscription management
• GitHub: OAuth sign-in and user information retrieval
• Google: OAuth sign-in and user information retrieval
• UptimeRobot: external health-check pings

We do not provide or sell data to any other third party. Disclosures required by applicable law are excepted.

4. OAuth token handling

The Service never stores access tokens or refresh tokens issued by OAuth providers (GitHub / Google). Tokens are discarded immediately after user information is retrieved during sign-in (consistent with planning doc §24.3). The scopes associated with the tokens (such as read:user and email, the minimum required) are not used for any purpose other than sign-in.

5. Potential future telemetry

Starting with Phase 2, the Service may begin collecting passive telemetry (metadata statistics only, such as component usage frequency and co-occurrence patterns) for quality improvement. If collection begins, this policy will be updated and the change will be announced via email, Discord, and the landing page. C# script bodies will never be transmitted, even after Phase 2 (consistent with planning doc §11.2).

6. Contact for deletion or disclosure requests

To request the deletion, disclosure, or suspension of use of collected data, please contact us via the channels below.

• Email: [email protected]
• Discord: DM in the official community (once launched)

During the MVP we do not provide a self-service disclosure UI (such as a usage dashboard). Individual requests are handled via the contact channels above. A usage dashboard is planned for Phase 3 (aligned with planning doc §11.3, purpose (2)).

Contact

For inquiries about this policy, please contact [email protected].