Gamine Documentation
Privacy Policy — English reference
A plain-language English reference for how Gamine handles personal information.
Reference translation — not legally reviewed
This English page is provided to help readers understand the main points. It has not yet received professional legal review and is not the authoritative version.
The Japanese document applies if wording differs.
Basic policy
Gamine handles information only as reasonably necessary to provide and protect a community for game-related posts, assets, reviews, and recruitment. The operator aims to minimize collection and avoid retaining information that is not needed.
Information we handle
Account information
- User ID, username, display name, profile and header images, and email address
- Identifiers, display name, email address, and profile image received from Google, GitHub, or Discord
- Authentication tokens, scopes, and expiry information when required by the provider
- Account creation, update, sign-in, role, suspension, and administrative status information
Profiles, posts, and community activity
- Profile text, areas of involvement, skills, links, and other public profile information
- Games, assets, reviews, comments, progress, recruitment, applications, images, and external links
- Categories, tags, genres, licenses, credits, age restrictions, content warnings, and notes
- Follows, blocks, user/word/tag mutes, and personal content-filter settings
- Likes, comments, helpful reactions, and external-link click records
- Generative-AI disclosure details, Improvement Board suggestions and reactions, announcement read state, notifications, reports, and moderation history
Inquiries, technical information, and cookies
- Contact name, reply email, subject, message, target URL, receipt ID, category, and handling status
- IP address, user agent, request time, destination, referrer, errors, and other server or security logs
- Cookies or similar identifiers used for sessions, anonymous viewing, click aggregation, and abuse prevention
- Hashed IP or email values and rate-limit records used for abuse prevention
- Uploaded image filename, storage key, MIME type, size, and storage time
Why information is used
- Authentication, accounts, profiles, posting, search, editing, and deletion
- Storage and delivery of images and other service content
- Personalized display controls, follows, blocks, mutes, and warning preferences
- Reports, moderation, account restrictions, spam prevention, security, and incident investigation
- Contact responses, identity checks, transactional email, and important notices
- Feature improvement, bug fixes, aggregate usage understanding, and Improvement Board operation
- Compliance with laws, the Terms of Service, and Community Guidelines
Information visible to others
Public profiles, posts, images, links, categories, tags, licenses, credits, visible counts, and public Improvement Board suggestions can be seen by other visitors. When an Improvement Board suggestion is shown anonymously, the public profile is hidden, but Gamine retains the internal account link for abuse prevention and account actions.
Reports, blocks, mutes, personal filters, and moderation records are generally limited to the user, administrators, or the minimum audience required by the feature.
Service providers and disclosures
Personal information is not provided to third parties without consent except when required by law, necessary to protect life, safety, property, or rights, needed to address abuse, or entrusted to a provider as necessary to operate the service.
| Provider | Purpose | Information that may be processed |
|---|---|---|
| Cloudflare | Application hosting, database, image storage, delivery, Turnstile, and abuse prevention | Accounts, posts, images, IP address, access logs, and browser or device signals |
| Google sign-in | Google account ID, email, display name, and profile image | |
| GitHub | GitHub sign-in | GitHub account ID, username, email, and profile image |
| Discord | Discord sign-in | Discord account ID, username, email, and profile image |
| Resend | Authentication, contact, and important transactional email | Email address, contact name, subject, message, and delivery logs |
These providers have their own terms and privacy policies. They may be located, store data, or process data outside Japan.
Retention and backups
| Information | General retention approach |
|---|---|
| Account information | Generally while the account exists; minimum records may remain for abuse prevention, legal response, or moderation |
| Posts, reviews, recruitment, progress, and profiles | Until deleted, made private, or the account is deleted; some records may be hidden or anonymized when relationships or moderation require it |
| Sessions and cookies | For the configured lifetime, until invalidated, or until removed by the browser; the anonymous external-link identifier lasts no more than one year |
| Logs and inquiry history | As reasonably needed for security, incidents, abuse prevention, support history, and provider operation |
| Improvement Board and moderation records | May be anonymized and retained after withdrawal when needed to preserve decisions, card history, safety, or legal response |
| Images | Generally until the associated account or post is deleted; temporary copies may remain in caches, logs, or provider backups |
| Backups | May remain in provider recovery systems or reasonable operator-made preservation copies; no fixed retention or rotation period is promised |
Because Gamine is operated by an individual, a uniform deletion schedule, backup frequency, fixed retention period, point-in-time recovery, or restoration of individual data cannot be guaranteed. Keep your own originals of important posts and images.
Access, correction, deletion, and restriction
Subject to identity verification and applicable law, users may request access, correction, addition, deletion, restriction of use, or restriction of third-party disclosure. A request may be limited where identity cannot be verified, other people’s rights or safety would be affected, records are required for reports, moderation, abuse prevention, security, or law, or separation is technically or operationally impracticable.
Use by minors
Minors should obtain guardian consent where required. Age restrictions and content warnings reduce exposure but cannot guarantee complete protection; users and guardians should also use viewing settings, mute, and block.
Privacy questions and requests
Use the contact form and choose the privacy category. Describe the requested action and information or account involved. If identity verification is needed, instructions will be provided in the reply.
Do not include passwords, verification codes, sign-in links, or identity documents in the initial message. Use Contact—not the public Improvement Board—for privacy, rights, account-specific, or undisclosed security matters.