01 Information we collect

When you choose to sign in with LinkedIn, OpenDyna may receive:

• Your name and email address.
• Your LinkedIn account identifier.
• A profile image if LinkedIn includes one in the sign-in response.
• Authentication tokens and session information needed to keep you signed in.

OpenDyna requests this information when you authenticate and when your session is refreshed. It does not request your LinkedIn connections, posts, employment history, or LinkedIn password.

If you submit an FSAE data correction ticket, OpenDyna collects the competition, year, team, affected result, correction details, source reference, page URL, and the contact email required with the report. A salted, one-way hash derived from the request IP address is stored to rate-limit ticket spam; the raw IP address is not stored in the ticket table.

02 How we use information

We use this information only to:

• Create, identify, secure, and maintain your OpenDyna account.
• Provide authenticated engineering tools and account features.
• Review, track, and respond to submitted data corrections.
• Prevent abuse, diagnose failures, and protect the service.
• Comply with legal obligations and enforce the User Agreement.

We do not sell LinkedIn-derived information, use it for advertising, build employment or eligibility scores from it, or share it with other OpenDyna users.

03 Service providers and disclosure

• LinkedIn provides the OpenID Connect identity service and its own consent screen.
• Supabase processes authentication, stores the OpenDyna user record and data correction tickets, manages sessions, and runs the ticket-submission function.
• Resend delivers data correction ticket notifications to OpenDyna support.
• GitHub Pages hosts the public static website.
• jsDelivr delivers the Supabase browser library and may receive ordinary web-request information such as IP address and user agent.

We may also disclose information when legally required or when reasonably necessary to protect users, OpenDyna, or the public.

04 Storage, security, and retention

Authentication data is transmitted over HTTPS. Supabase stores the account record and manages browser sessions. OpenDyna keeps LinkedIn-derived account information only while needed to provide your account, unless retention is legally required. Access to future application tables will be restricted with Row Level Security.

Data correction tickets are retained while needed to investigate, document, and prevent duplicate correction work. Reporter contact information is used only for follow-up about that report. Ticket records are not directly accessible through the public browser client.

No internet service can guarantee absolute security. OpenDyna limits the data requested and keeps provider secrets out of browser code and the public repository.

05 Your choices and deletion

You may stop using LinkedIn sign-in or withdraw consent at any time by deleting your OpenDyna account. While signed in, open the account modal from your name in the site header and select Delete my account. This deletes the Supabase Auth user and associated application records configured to cascade with that user.

Signing out only ends the local session; it does not delete the account. You may also remove OpenDyna's authorization through your LinkedIn account settings. Data retained by LinkedIn, Supabase, GitHub, or jsDelivr is governed by each provider's policies and applicable law.

06 Changes

Material changes to the collection or use of LinkedIn-derived information will be disclosed before the changed practice applies. Renewed consent will be requested when required.

07 Questions

For privacy questions, consent withdrawal, or a deletion request when you cannot access your account, email privacy@opendyna.com. For general account assistance, email support@opendyna.com. Do not submit passwords, access tokens, or private credentials through public GitHub issues or email.