Privacy Policy

What BoardRepo collects, why it is used, and the choices you have.

Last updated: November 13, 2026

Summary

  • We need account details, project files, and product records to operate BoardRepo.
  • Your handle, name, and avatar are public. Public projects can be downloaded and indexed. Anyone with a valid private link may open it.
  • Members of an organization can see each other's handle, name, and email address.
  • AI features send relevant context to an AI service provider. We record Ask exchanges; project detail and documentation drafts omit request and response contents from drafting analytics and keep usage counts, timing, and outcomes.
  • Connected-assistant records may include content the connection was allowed to read.
  • We do not sell personal information or share it for behavioral advertising.

Who is responsible for the data

Flintt, Inc., a Delaware corporation at 2261 Market Street STE 13714, San Francisco, CA 94114, United States, operates BoardRepo and is the controller of the personal data covered by this policy. Email privacy questions or requests to privacy@boardrepo.com.

What we collect

Account information. We store your email address, handle, and any name or avatar you add. Your handle, name, and avatar are public: they appear on your profile page, on the boards you publish, and next to your comments. Your email address is not shown publicly. If you use a third-party sign-in or repository integration, we receive the account and repository information needed to provide that feature. Repository access is limited to the repositories you select.

Projects and activity. We store projects, original files, versions, generated artifacts, visibility settings, licenses, comments, saved projects, and other actions you take. BoardRepo also records operational data such as pages opened, searches, downloads, feature use, device and network information, timestamps, and errors. Anonymous download counts use a one-way hash of the network address, not the address itself.

BoardRepo Ask. To answer a question, Ask uses your conversation and the relevant project content. We keep a record of each exchange, including the request, the board context that was sent, and the answer, so we can operate, secure, troubleshoot, and improve Ask.

Connected assistants. We record usage and diagnostic information about connected-assistant requests. Those records may include the request and content returned from boards the connection was allowed to read, including private boards when you approved that access. Access credentials are not included in analytics.

KiCad plugin. The plugin sends diagnostic events about its own operation: which step ran, whether it succeeded, how long it took, and the plugin version, KiCad version, operating system, and processor type. Those events carry no design content. They are linked to your account once you sign in and are anonymous before that.

Messages to us. If you report a problem, request another file format, or contact us, we receive the message and the account, project, and technical details needed to respond. A report sent from inside the product also includes the page address and, when the capture succeeds, a screenshot of the page as it appeared to you, which can include board content. The form shows the screenshot before you send it.

Organizations and invitations

If you create or join an organization, its members and admins can see your handle, name, email address, role, and when you joined. Admins manage membership and decide which boards each member can reach. Boards owned by an organization are controlled by its admins, and we act on their instructions for those boards.

An admin can invite someone by email address. We receive that address from the admin and use it only to send the invitation and to match it to an account when the invitation is accepted. Every invitation email includes a link that stops further invitation emails to that address.

Why we use it

  • create accounts, authenticate users, and remember granted access;
  • run organizations, including memberships, invitations, and board access;
  • store, render, analyze, and deliver projects and their versions;
  • run BoardRepo Ask and connected-assistant tools;
  • send sign-in codes, invitations, service messages, and replies;
  • follow up personally after you sign up, to ask how BoardRepo is working for you and offer help;
  • prevent abuse, enforce limits, investigate incidents, and protect the service;
  • diagnose failures and measure how individual features work; and
  • evaluate and improve BoardRepo, including the quality of its AI and assistant features.

Cookies, local storage, and session replay

Necessary cookies keep you signed in, complete sign-in and repository connections, remember access grants, and prevent duplicate counts. Preference storage remembers your workspace and display choices. These do not depend on optional tracking consent. Neither does the creator link cookie br_creator: opening a creator's link stores that creator's code, so a sign-up in the next 30 days can be credited to them, whichever tracking choice you make.

Optional browser analytics (PostHog), session replay (PostHog and Sentry), and marketing measurement (Letter) stay off until you select Accept. Accept and Reject are offered to everyone, regardless of region. We remember either choice in the first-party cookiebr_tracking_consent for 12 months (365 days), with SameSite=Lax and Secure in production. A Global Privacy Control signal is treated as Reject unless you explicitly accept later. If a choice cannot be saved, we explain that instead of enabling tracking. If cookies are blocked, a tab-level denial in session storage (br_tracking_consent_rejected) can keep tracking off until the tab is closed.

lets you change or withdraw your choice at any time; the same control is in the site footer. Choosing Reject stops browser analytics and replay and clears PostHog cookies and local/session storage. Withdrawal reloads the page if optional code has already started, to stop third-party code that cannot reliably be unloaded. Acceptance takes effect without a reload. Neither choice deletes earlier records or changes server-side operational, product, AI or connected-assistant telemetry.

After acceptance, PostHog receives product events, page/device information and searches; signed-in analytics includes your account ID and email. PostHog replay masks text inputs. Sentry Replay masks text and inputs and blocks media by default, but replay can still show page structure, including board pages. Submitted product events and support reports are separate from replay masking. Sentry error monitoring remains active without optional consent, with default PII collection disabled and network-identity redaction; it does not require a browser cookie.

After acceptance, public pages may load Letter (lettervisit.com) for visit and marketing measurement, including matching a visit to the company or person behind it so we can follow up. Letter can use cookies, browser storage, network and page information, and can load additional third-party code, including visitor-identification providers such as Vector and Maverick Intelligence. Its remote cookie names and durations are not fixed by BoardRepo's code. See Letter's privacy information and vendor opt-out. BoardRepo's Reject choice prevents its loader from running; it does not delete records already held by Letter or clear third-party cookies belonging to other domains.

Service providers

We use service providers to host and deliver BoardRepo, store files, send email, provide optional sign-in and repository connections, process AI requests, monitor errors, understand product use, and handle support messages. They receive only the information needed for the work they perform. We may change providers as BoardRepo develops.

When manufacturing quotes are available and you request a quote or order, the design files needed to price it go to the manufacturing provider, ProvenMetal, under your instruction.

The information involved can include account details, service and request data, project content, AI conversations and relevant board context, usage and device information, diagnostic records, and messages you send us.

We may also disclose information to comply with law, respond to valid legal process, investigate abuse, or protect BoardRepo, our users, or the public. If BoardRepo is involved in a merger, financing, reorganization, or sale, data may be transferred as part of that transaction subject to this policy or notice of a replacement policy.

Public projects and private sharing

A public project, including its files, comments, metadata, and license, can be viewed, downloaded, indexed, and read by people or automated systems. Do not publish personal or confidential information. Private-link and password-protected projects are left out of BoardRepo browse and carry noindex metadata, but noindex is an instruction to crawlers, not an access control. Anyone with a valid private link, and the password where one is set, may be able to open the project.

AI features and outside assistants

BoardRepo Ask selects the project context needed for a response and sends it with your conversation to an AI service provider. The provider processes this content to produce the answer, under its business terms. We may change AI providers over time. Ask is limited by the project access BoardRepo checks for the request.

An outside assistant connects through a separate consent screen, and a connection has only the permissions that screen showed you: which boards it may read (public boards only, or public boards plus boards you own, and eligible users can include organization boards) and, where the screen offers it, whether it may save boards and new versions for you. A permission you were not shown is one the assistant does not have; a read-only connection cannot edit, rename, publish, or delete your projects. Some read tools can queue derived analysis, such as connectivity, checks, or a review, without changing the source design. The company that operates the assistant also receives whatever the assistant reads and handles it under its own terms and privacy policy. You can revoke a connection in Settings.

BoardRepo makes no automated decision about you that has a legal or similarly significant effect. Automated systems apply rate and storage limits and flag abuse; decisions to hide content or restrict an account are made by people.

Project detail and documentation drafts

When you choose Draft from files or Generate documentation for a personal project, BoardRepo sends a bounded selection of retained filenames, README excerpts, component information, and PCB geometry and connectivity facts to Anthropic. This can include private project information. Files excluded from your upload and detected credentials are left out. Documentation generation uses the saved version's retained files. Organization projects are not included.

Generating a draft does not publish or save it. You review and edit the text before creating the project or saving its details. BoardRepo does not store the temporary drafting request or response as a separate record, and drafting analytics omit their contents. Usage counters and diagnostic events record counts, timing, and outcomes. Anthropic processes the selected information under its commercial API terms and applicable retention policy. You can write every field yourself without using AI.

How long we keep data

We keep account information while the account is open and project content until it is deleted. Deletion removes the project from the active service first; residual copies may remain for a limited time in backups or where we need them for security, legal, or recovery purposes. Database backups roll off within about five weeks.

Email sign-in codes expire after 10 minutes and invitation links after 24 hours. Already-issued sign-in links retain their original 15-minute expiry. A signed-in session lasts up to 30 days. A connected-assistant credential expires after 30 days and a KiCad plugin credential after about a year; you can revoke either earlier in Settings. Copyright notice correspondence is kept for three years after the matter is closed.

Retention for operational, security, analytics, diagnostic, Ask and connected-assistant records varies with the reason the record exists and the settings of the service providers involved. Some records may remain after a connection is revoked, a review is deleted, or an account is closed. Reviews and other records from the retired Astra Arena feature are being deleted; database backups that still hold them roll off on the schedule above. Email us if you need a specific record reviewed or removed.

Deleting your account

You can delete your account in Settings, under Account, or by emailing privacy@boardrepo.com. In Settings we first send a code to your email address to confirm it is you. Deletion takes effect as soon as you confirm. There is no waiting period, and a deleted account cannot be restored.

  • We delete your profile, email address, sign-in methods, sessions, and plugin and connected-app credentials; your personal boards with every version and file; your personal parts libraries; any organization where you are the only member, with its boards; and your comments, stars, notifications, feedback reports, review comments and approvals, access to other people's boards, and pending invitations sent to your email address.
  • If you belong to an organization with other members, you leave it and its boards stay with it. Versions you published to boards you do not own stay, without your name. If you are an organization's only admin, make another member an admin or delete the organization first.
  • Replies other people wrote to your comments stay as their own comments. Remixes other people made of your public boards are their copies and keep the credit that names your handle.
  • We keep your handle reserved, with nothing else attached, so nobody can take it and appear as you on old links. Our security audit log keeps a record that the account was deleted, with its account ID and handle but not its email address, and earlier audit entries that name the account ID, such as organization membership changes.

Stored files are removed from file storage within about three days. Files from an upload that was still in progress are removed once its upload link expires. Database backups that still contain the account roll off within about five weeks. We delete your PostHog analytics profile and its events within one month. Sentry error reports do not carry your account ID or email address and expire under Sentry's retention settings. KiCad Browser keeps its own copy of workspaces you opened there, which account deletion does not remove yet; email us and we will delete it. Emails we sent you remain in our email provider's delivery logs for the period that provider keeps them.

We process account, organization, and project data as needed to provide the service you requested. We use legitimate interests to secure BoardRepo, prevent abuse, diagnose problems, understand use, improve the product, and deliver an organization invitation that a member asked us to send, after considering the effect on the people concerned. We also process data to meet legal obligations. We rely on legitimate interests to follow up personally with people who have signed up. We do not send marketing email that requires consent unless you have given it. Where consent is legally required, we will ask for it and you may withdraw it.

International transfers

BoardRepo is operated in the United States. Our providers may process data in the United States and other countries. Where required for transfers from the EEA or UK, we use a recognized safeguard such as standard contractual clauses.

Imported GitHub profiles and copyright notices

Some public project pages were imported from public GitHub repositories and are owned by a placeholder profile until the author claims them. For those profiles we hold the GitHub login, display name, avatar, and public repository metadata that GitHub already publishes. We do this to run a public-data directory of electronics projects (legitimate interests). We do not email the address on a GitHub profile. To object, claim the board, or ask us to take the copy down, use the contacts on the copyright page. You do not need an account or a reason. When you object, we hide the copy so it no longer appears anywhere on BoardRepo, and we keep the hidden record only so the same repository is not imported again.

If you send a copyright notice or counter-notice, we keep the correspondence needed to handle it, including the URLs named and the contact details you give us, for three years after the matter is closed. We do not publish those notices.

Your choices and rights

You can edit your profile, change project visibility, delete projects, revoke connected assistants, and delete your account in the product. If you would rather not hear from us after signing up, reply to any follow-up or email privacy@boardrepo.com and we will stop; sign-in codes and other service messages continue while you have an account. You can ask us to access, correct, export, or delete personal information, or object to or restrict certain processing, by emailing privacy@boardrepo.com. We may need to verify that the request concerns your account. We answer within one month, or within 45 days where California law applies, and tell you if a complex request needs longer. We will not treat you differently for making a request. If we refuse a request, we say why, and you can ask us to look at it again. You may also complain to your local data protection authority.

California residents may have rights to know, access, correct, or delete personal information and to receive equal service when exercising those rights. BoardRepo does not sell personal information or share it for cross-context behavioral advertising, so there is no sale or advertising-sharing opt-out to exercise.

Security

We use technical and operational controls intended to protect BoardRepo, but no online service can guarantee perfect security. Keep your own copy of important source files and report suspected vulnerabilities to security@boardrepo.com. The current controls are described on our Security page. If a breach of our systems affects your personal data, we will notify you and the authorities that the law where you live requires, without undue delay and within the deadline that law sets.

Children

BoardRepo is not directed to children under 13, and we do not knowingly collect their personal data. Contact us if you believe a child has submitted personal data.

Changes

We will update this page as BoardRepo and its data practices change. For a material change, we will update the date above and give notice where appropriate.

Contact

Email privacy@boardrepo.com. You can also read our Terms of Service.

Sign in to BoardRepo

New here? Signing in creates your account; there is no separate sign-up.