Last updated:
Scope
This policy describes how AI Competition Radar (aicompetition.dev) handles personal information for site visits, accounts, Personal Radar and the forum. We provide the service under the AI Competition Radar project name. You can contact us about privacy and information rights using the support email below.
Google sign-in and Google user data
If you choose Google sign-in, we request the basic openid, email and profile permissions. We receive your Google account identifier, email address and verification status, name and avatar URL to create or identify your site account, sign you in and link sign-in methods. The authentication system stores necessary account links and authentication tokens, scopes and expiry information actually returned by Google on the server. We do not receive your Google password or request permission to read Gmail, Drive, contacts or your personal calendar. Google user data is used only for these account functions and necessary security handling. It is not sold or used for advertising, credit assessment or training general-purpose AI models. Our use and transfer of Google user data to other apps complies with the Google API Services User Data Policy, including its Limited Use requirements.
Public forum content and moderation
Your chosen public nickname, optional bio, posts, replies, publication times and related competition information are visible to other visitors. Sign-in email addresses and authentication tokens are not published as forum profile information. Reports, moderation reasons and account restrictions are used to handle complaints and protect the community, with access limited to authorized personnel. Do not publish passwords, identity documents, private contact details or other people's personal information. Public content may be copied by visitors or indexed by third parties.
Accounts, authentication and security data
When you register or sign in, we process your email address, account name, email verification status, sign-in methods and account identifiers. An avatar URL supplied by a sign-in provider may also be stored. Password sign-in stores a password hash, not a plain-text password. Sessions, expiry times, IP addresses, browser information, verification records and necessary rate-limit records support authentication, account recovery and abuse prevention. Account data is stored in our server database, not solely in your browser.
Cookies, local storage and drafts
Sign-in uses cookies and server-side sessions. Sessions currently last seven days and may be renewed during use; signing out ends the current session. A language cookie lasts one year. While you are signed in, the browser may also keep an HttpOnly cookie for the rest of the UTC day so a repeat visit is not written again. That cookie contains a date and a check value, not your email address or page history. Personal Radar preferences, saved opportunities and hidden items currently remain in browser storage and do not automatically sync across devices. Post and reply drafts use session storage in the current browser tab. You can adjust these settings in the site or clear site data in your browser. Clearing local data may remove preferences and drafts, but does not delete your server-side account or published forum content.
Visitor analytics
The site uses Vercel Web Analytics to understand visits, page usage and aggregate product events, including completed registrations and sign-ins, authenticated returns on days 1, 3, and 7, verified official-site redirects, calendar entry clicks, and ICS file generation. These custom events do not include email addresses, user IDs, or profile data. When analytics is enabled, Vercel may process page addresses, referrers, device and browser types, visit times and approximate regions to provide aggregate statistics. Separately, while you are signed in, the server stores at most one activity row per account per UTC day. That row contains the account identifier, the UTC date, and a timestamp. It does not include a page address, email address, or profile fields. It is used to measure sign-up cohorts and return visits, and it is removed when the account is deleted. While you are signed in, the server also stores behavior events linked to the same account identifier: registration, sign-in, a competition detail view at most once per competition per UTC day, a click through to a verified official site, adding a deadline to a calendar or downloading an ICS file, publishing a forum post or reply, and saving or removing a competition in this browser. Each behavior event stores the event type, a target such as a competition slug or a forum post or reply identifier, a timestamp, and limited details such as the sign-in method, calendar provider, interface language, or whether a save was added or removed. These behavior events do not include page addresses, email addresses, post or reply text, or profile fields, and they are removed when the account is deleted. Saving a competition still happens in this browser and is not copied to other devices. The hosting platform may also keep request and error logs for operation, security and troubleshooting. Do not include passwords, identity documents or other sensitive information in URLs or search terms.
External websites and calendars
Opening an event website or adding an entry to Google or Outlook Calendar takes you to a third-party page. The event title, time, description and link you select may be sent as prefilled information. Calendar links are separate from Google sign-in and do not grant this site permission to read your personal calendar. You download, store and import ICS files yourself. Third-party services have their own privacy policies.
Service providers and sharing
We use Vercel for hosting and analytics, Neon PostgreSQL for account and community data, and Resend for verification and recovery emails when email features are enabled. Google or GitHub handles its sign-in flow when you choose that provider. Providers process information needed to deliver their respective services. Processing locations depend on our deployment and provider infrastructure and may be outside your region. We do not sell personal information. Non-public account information is not disclosed to unrelated parties except to provide the service, follow your instructions, investigate security issues or comply with applicable legal obligations.
Retention and what deletion does
Account and sign-in linkage information is kept as needed to provide account services. Sessions and verification codes expire, but expiry does not mean every historical database record is immediately erased. Posts and replies generally remain until you delete them or moderators act. Current post and reply deletion is soft deletion: public text is removed and a placeholder may remain; database records and other people's replies are not automatically erased. Moderation records, reports, security logs or backups may be retained for disputes, security or applicable legal requirements. Signing out or clearing browser data does not clear these server-side records.
Corrections, revoking access and deletion requests
You can change your public nickname in My account, update your bio on the account page, and edit or delete your own posts and replies. Account settings let you manage linked sign-in methods while retaining at least one usable method. You can also revoke authorization on Google's third-party connections page. Revocation or unlinking does not delete your site account or historical data. A self-service account deletion button is not currently available. To request access, correction, export or deletion of your personal data or account, email support below. We will verify account ownership and handle the request under applicable requirements, explaining the outcome and any data that must be retained.
Security and younger users
We use authentication, access controls and request limits to protect accounts and the community, but no internet transmission or storage is absolutely secure. Protect your email and sign-in credentials and never share passwords or verification codes. Users who are not old enough to consent independently under applicable local rules should use the service with their guardian's knowledge and consent. Guardians can contact support about personal information concerns.
Policy updates
We update this policy and its date when features or data handling change. Material changes requiring notice or consent will be addressed before implementation under applicable requirements. Existing Google sign-in permissions will not simply be reused for undisclosed new purposes. The Chinese and English versions are intended to convey the same information; contact us if you have questions or notice a discrepancy.
Support and privacy contact
For AI Competition Radar service, privacy, content-rights or account deletion requests, contact the email below. Where possible, write from your registered email and identify the relevant pages or data to help us verify ownership. We will not ask you to send passwords or verification codes by email.
ideaforceai@gmail.com