1. Scope
This policy applies to the Silex website, connected-account sign-in, project and contact submissions, community interactions and administration of the Silex editorial listing service.
2. Information we process
Connected accounts
When you sign in with an enabled provider such as Discord or Google, Silex receives a stable provider identifier and may receive your provider username, email address and avatar. Silex stores the provider identity needed to associate future sign-ins with your account.
Sessions and security records
Silex processes session tokens, CSRF tokens, account roles, account status, OAuth state and timestamps needed to operate secure sessions and protected administrative features. The browser receives a session cookie; server-side records use protected token representations.
Information you submit
Contact, listing and advertising forms may include names, contact details, project information, contract addresses and message content you choose to provide.
Community and technical information
Votes and community interactions may use an identifier and timestamps to enforce limits and calculate aggregate results. Standard server and analytics records may include page activity, device or browser characteristics, approximate network information, error information and request timestamps.
3. How information is used
We process information to:
- authenticate users and maintain secure sessions;
- enforce account roles and protect administrative actions;
- respond to contact, listing and advertising submissions;
- operate community voting and prevent duplicate or abusive activity;
- maintain editorial records and attributable administrative audit history;
- diagnose faults, secure the service and understand aggregate product usage;
- comply with legal obligations and protect legitimate interests.
6. Retention
Information is kept only for as long as reasonably necessary for the purpose for which it was collected, security and dispute handling, editorial accountability, or a legal obligation. Session and OAuth-state records expire according to configured security periods. Administrative audit records may be retained longer to preserve the integrity of editorial decisions.
7. Your choices and rights
Depending on applicable law, you may request access, correction, deletion, restriction, objection or portability concerning your personal information. You may also withdraw consent where processing relies on consent and lodge a complaint with a competent data-protection authority.
You can stop future connected-account sign-ins by revoking Silex access through the relevant provider. Revocation at the provider does not automatically erase information already held by Silex; contact us for an account-data request.
8. Security and international processing
Silex uses technical and organizational controls intended to protect account and administrative data, including signed sessions, CSRF protection, role enforcement, origin validation, rate limits and server-side audit attribution. No online service can guarantee absolute security.
Some providers may process information outside your country. Where required, appropriate safeguards should apply through those providers' terms and applicable data-transfer mechanisms.
9. Changes to this policy
We may update this policy as Silex or applicable requirements change. Revisions will be published here with an updated effective date.
10. Contact
For privacy questions or a data-rights request, use the current operator contact channel published through the official Silex community destination in the shared footer. Provide enough information to locate the relevant account or submission without sending secrets, passwords or private keys.