Data and privacy
FPGA.camp collects only the data needed for accounts, Forum, Chat, submission moderation, and spam protection. Public user profiles are not shown, and contact data is not published unless editorial review requires it.
Data we use
- Account: name, email, user role, and technical session data.
- OAuth: provider identifier, email, and name returned by Google, GitHub, or Yandex.
- Submissions: submitted text, source links, author contacts, and moderation status.
- Forum: threads, replies, solution status, flags, and technical context explicitly posted by the user.
- Chat: web-chat messages are stored locally in the user's browser; the Telegram bot stores request and answer history in the database indefinitely until the user requests deletion.
- Telegram payments: paid-model deposits store invoice payload, Telegram Stars status, charge id, and a hidden OpenRouter key binding without exposing the key to the user.
- Security: IP address and captcha token are used for limits, spam protection, and form verification.
Why consent is required
The preselected sign-in and registration checkboxes confirm that the user understands the account rules and allows the minimum data processing needed for login, Forum, Chat, and submissions. The user can clear the checkboxes, but then site sign-in and OAuth sign-in will not continue.
Account session
After sign-in, the site keeps the account session for at least 3 days unless the user signs out, clears cookies, or an administrator revokes the session. The session cookie is used only for authentication and is not exposed to client-side code.
Publishing and moderation
User submissions are created as drafts. An administrator receives a draft link, checks the source, and decides whether the material can be published. If the link is unreachable or the claim cannot be verified, the record stays in drafts.
Access and removal
Users can sign out from the account page. Requests to correct or remove data are handled through the project contacts on the community page.
Updated: May 20, 2026