Loading Engineering Foundry…
Loading Engineering Foundry…
What Engineering Foundry collects, why it is used, and the choices you have.
Last updated: October 9, 2026.
This policy covers the Engineering Foundry website and its interview-preparation, account, and community features. Public information pages can be read without an account. The account, referral, feedback, and other interactive features described below collect information only where those features are enabled and you use them. Visiting a public information page does not create an account. External services you choose to visit have their own privacy policies.
Where account features are enabled, Supabase provides authentication, session handling, and account storage. Creating an account involves an email address and account identifier, along with the name and other profile information you provide. Where email-and-password sign-in is enabled, credentials are handled by Supabase authentication.
If you choose Continue with Google, Google and Supabase provide the identity information needed to sign you in: a Google account identifier, email address and verification status, and basic profile information such as your name and profile picture. We use this information to create or recognize your Engineering Foundry account, display your profile, and maintain your session. Google sign-in does not give Engineering Foundry your Google password or request access to your Gmail messages, contacts, Google Calendar, or Google Drive files.
Supabase stores the identity link and account information; your name and profile picture may populate your Engineering Foundry profile. Public visibility is controlled by your profile choices. If we seek additional Google permissions or change how Google information is used, we will explain the change and ask for consent before doing so.
Account features store the information you choose to save, including applications, interview preparation, behavioral stories and answers, progress notes, design attempts, saved mock reviews, interview-experience drafts and submissions, preferences, and reminders. Private workspace records are associated with your account so that you can retrieve and manage them.
Choosing a public profile makes the selected profile fields visible to others. Comments you post publicly and approved interview-experience reports submitted with publication consent can also be read by others. Avoid placing confidential employer information or someone else's personal information in public content.
If you use the referral network, your request can include your name, LinkedIn profile, experience, target role, and uploaded resume. With your consent, eligible verified referrers at the selected company can view the request and resume. Referrer verification uses a work email address. Withdrawing a request stops further access through the service but cannot erase a copy already downloaded by a recipient.
Authentication cookies keep you signed in. Browser storage also supports preferences, optional analytics consent, and learning progress or plans explicitly saved to this browser. Clearing browser data removes those local copies and can sign you out; it does not delete separately saved account records.
Referral Toolkit, Challenge Lab, and the company Interview Experience reflection builder keep their unsaved drafts in browser memory. Unsaved Mock Interview Lab ratings and notes are also session-only. These draft fields are not included in analytics, and refreshing the page clears them. Explicitly saved account records and browser-saved learning progress have separate storage controls.
Feedback submitted through the private feedback form is stored for authorized Engineering Foundry operators to investigate and respond to reports. It includes a category, message, sanitized page context, relevant content identifiers, and a private reference ID. Contact email is optional and used for follow-up only with your report-specific consent; submitting feedback does not create a marketing subscription. Anonymous submissions use a browser cookie and a hashed identifier to limit repeated submissions.
Signed-in feedback is included in that account's export while the account exists; deleting the account removes the account link but does not convert an already-submitted report into a public record. The report, including any message and optional contact details, remains in the private feedback system. Contact us with its reference ID if you want us to review a request to remove it.
Engineering Foundry may use PostHog for public pageviews and fixed product events only after you accept analytics. Until you accept, or if the choice is invalid or unreadable, PostHog stays uninitialized and earlier activity is not queued or replayed. Declining or withdrawing consent stops further capture. The choice applies to this browser, so make it separately on other devices.
When enabled, analytics can include browser and device information, identifiers, public-page paths, and predefined learning actions. Signed-in activity may be associated with your account identifier. The application disables autocapture, session recording, and private-route pageviews, and removes URL queries and fragments from public-page analytics. Free-text drafts, passwords, tokens, personal contact fields, compensation values, feedback contents, and clipboard contents are excluded from product event properties.
We use information to operate account and preparation features, provide requested communications, investigate problems, protect the service from abuse, and understand product use when analytics is accepted. Service providers process the data needed for their role: Supabase for authentication, database and file storage; Google when you choose Google sign-in; the website's hosting infrastructure for serving requests; and PostHog for optional analytics.
Where configured, Sentry receives filtered technical error reports, and email delivery services such as Resend handle account or opted-in reminder and referral messages. Server-based code execution services receive the code and test inputs needed when you run supported exercises. Technical services can process connection information, including IP addresses, to deliver requests and maintain security. These operational functions are separate from optional product analytics.
Information may also be disclosed when needed to comply with applicable legal obligations, address abuse, or protect people and the service. Following a link to Discord, GitHub, an employer, or another external resource brings you under that service's practices. Our providers may process information in countries other than your own.
Saved account information remains associated with your account until you remove it through the available controls or delete the account. Private feedback and related operational records have a separate support and abuse-prevention purpose and are not all removed by account deletion. Infrastructure providers may retain logs or backups under their own settings and policies; deleting an account does not necessarily erase every such copy immediately.
In Privacy & data settings, signed-in members can download a private JSON export and, when account deletion is available, permanently remove their authentication identity and associated account records. Uploaded referral resumes are removed through account deletion; the JSON export contains referral metadata rather than the PDF files, which you can download separately. If deletion is unavailable or you cannot access your account, contact us for help.
You can update account and profile information in settings, change profile visibility, manage reminder preferences, and accept, decline, or withdraw analytics from the footer. Withdrawing analytics consent does not delete previously collected events or your account. You can also revoke the Google connection in your Google Account; revoking it does not itself delete your Engineering Foundry account or saved work.
To request access, correction, or deletion of information beyond the available controls, email engineeringfoundry.dev@gmail.com. We may need to verify the request before acting on account information. Available rights and any exceptions depend on applicable law.
When encrypted database backups are enabled, a backup made before deletion may retain an encrypted copy for up to 14 days before expiry. Any restore must remain isolated with accounts disabled until prior deletion requests have been reconciled, before restored data returns to service.
We may update this policy as the service changes and will revise the date above. Questions about this policy or how your information is handled can be sent to engineeringfoundry.dev@gmail.com. Please do not send passwords, access tokens, or unnecessary sensitive information.