Privacy Policy
Last updated:
This policy explains what personal data SILIXON LIMITED (company number 16614979, 1-2 Paris Gardens, London SE1 8ND; "siliXon", "we", "us") collects when you use our website, dashboard, and electronics design platform (the "Service"), how we use it, and the choices you have. Contact us any time at hello@silixon.io.
1. Data we collect
- Account data: your name, email address, and username when you register, and your password (stored only as a secure hash).
- Google sign-in data: if you choose "Continue with Google", Google shares your name, email address, and profile picture with us to create and sign you into your account. We do not receive your Google password, contacts, files, or any other Google account content.
- GitHub sign-in data: if you choose "Continue with GitHub", GitHub shares your name, username, email address, and profile picture with us to create and sign you into your account. We do not receive your GitHub password or access to your repositories.
- Content: the projects, designs, files, and prompts you create or upload while using the Service.
- Payment data: if you buy a paid plan, you enter your card and billing details on Stripe's own checkout page. We receive your plan, payment status, and invoices from Stripe, but never your full card number.
- Manufacturing order data: if you order boards through the Service, the delivery contact's name, address, phone number, and email address, and, if you give them, a company name and VAT, tax, or customs number. We store delivery details encrypted.
- Feedback: bug reports and feedback you send us, with your email address so we can follow up.
- Usage and log data: technical information such as IP address, browser type, pages visited, actions taken, page performance measurements, network timings, and application error diagnostics, used for security, debugging, and improving the Service.
- Newsletter: your email address if you subscribe to updates on our website.
2. How we use your data
- To provide, operate, and secure the Service and your account.
- To communicate with you about your account, such as verification and important service notices.
- To understand how the Service is used and improve it.
- To show the boards you publish to Community to anyone who visits it.
- To place and deliver the manufacturing orders you make through the Service.
- To send you product news and offers by email.
- To comply with legal obligations, including tax and accounting records.
We do not sell your personal data, and we do not use it for third-party advertising. We do not use Community boards to train or update our AI.
Marketing emails. Every marketing email we send contains an unsubscribe link. Using it stops further marketing emails. You can also opt out by emailing hello@silixon.io. We will still send emails you need to use the Service, such as sign-in, security, billing, and order emails.
3. Google user data
siliXon's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google sign-in data is used only to authenticate you and personalise your account, and is never sold or used for advertising.
4. Who can see your data
Anyone who visits Community. If you publish a board to Community, anyone, signed in or not, can see the board design, its project name, and your username, and search engines can list it. Signed-in users can copy the board. Each copy keeps a credit with your username, as the open hardware licence requires. If you delete your account, the credit becomes "siliXon user" (see section 5). Your name, email address, chat with Rocky, project history, project description, and private notes are never shown.
Service providers. Otherwise we share data only with the service providers below, and only to the extent needed to operate the Service:
- Convex: authentication, database hosting, and file storage, in the United States. We transfer your data to Convex under its data processing agreement, which incorporates the EU standard contractual clauses and the UK addendum to them. Convex also receives a website visitor's IP address and anonymous analytics ID when our homepage offer gives them a code, and keeps only one-way hashes of them.
- Google: sign-in with Google (if you use it), and Google Analytics, which measures visits to our website.
- GitHub: sign-in with GitHub (if you use it).
- Vercel: application hosting.
- Amazon Web Services: hosting our servers in the United Kingdom, processing your boards and storing the files this produces, and managing the encryption keys that protect delivery details for manufacturing orders.
- PostHog: product analytics, page performance and network timing measurements, application error diagnostics, and session recordings. Recordings may include ordinary non-password form values. Password inputs are masked in the browser before replay data is sent to PostHog. PostHog also receives your email address to send our product and marketing emails, and copies of your conversations with Rocky, our AI design assistant, so we can monitor the quality and cost of its replies.
- Sentry: error monitoring for our app and servers. An error report contains technical details of the error and the page or request where it happened, which can include data sent in that request. Sentry does not record your screen or sessions.
- AI model providers: OpenRouter runs Rocky. It passes Rocky's requests to the AI model's provider (such as Google), so they receive your messages to Rocky, any images or documents you attach, and the board and project content Rocky works on, to generate Rocky's replies. OpenAI powers part search and board reviews, and receives the text of Rocky's part searches and the board designs it reviews.
- Stripe: payments for paid plans. Stripe collects your card and billing details on its own checkout page, and we send it your email address and account identifiers. For manufacturing orders, Stripe also holds the delivery name, phone number, and address until we delete them (see section 5).
- PCBWay and JLCPCB: manufacturing the boards you order through the Service. We send the manufacturer you choose your board's manufacturing files (Gerber and drill files, plus the bill of materials and component placement file for assembled boards), the delivery contact's name, address, phone number, and email address, and any company name and VAT, tax, or customs number you give. You pay the manufacturer directly on its own payment page. Both manufacturers are based in China, and each keeps its own order records under its own privacy policy.
- TypeSafe: an automated check, before an order is placed, that the board meets the manufacturer's rules on prohibited uses. It receives your project's name and description, its parts list, and your recent messages to Rocky. When you delete your account, TypeSafe may also be asked to label a board we archive, from that project's recent chat messages (see section 5).
- Resend: account, billing, and order emails, such as email verification, password resets, invitations, receipts, order updates, and account deletion notices, and newsletter sign-up confirmations.
- Linear and Discord: our issue tracker and team chat, which receive the bug reports and feedback you send us, with your account ID and not your name or email address.
Some of our blog articles show images hosted on other websites. When you view one, your browser requests the image from that website, which receives your IP address and browser details.
We may also disclose data if required by law, or as part of a merger, acquisition, or sale of assets (in which case this policy continues to apply to your data).
5. Retention and deletion
We keep your data while your account is active.
Deleting your account. You can delete your account yourself on your Account page, or ask us to by emailing hello@silixon.io. Your account locks at once and you are signed out everywhere. We schedule its deletion for 14 days later and, if we have your email address, email you the date. Deletion can take longer if a step has to be retried. If you sign in before it starts, you can restore your account, unless we have paused the deletion for a legal reason. If you ask us by email, we can delete it sooner.
What we delete. When we delete your account, we delete your profile, picture, sign-in details, likes, and uploads, and your access to other people's projects. We delete your projects with their chats with Rocky, files, history, and board jobs. A copy of a project that our staff made is deleted with it where our records link the copy to your project; a copy that has its own manufacturing order is kept like a project with an order. Messages you wrote in a project that belongs to someone else stay in that project's chat. The other exceptions are described below: we archive a copy of fully routed boards, and we keep a project with a manufacturing order, with the files its chats show. We keep only an internal ID with no name, email address, or sign-in details, so the records we keep still fit together.
Routed boards. If a board in a project you own is fully routed when we delete your account, we keep a copy of the board in a staff-only archive that helps us improve siliXon. This includes private boards, and a project you had already deleted that we still hold. A project of yours that is still in use in someone else's workspace is not archived. The copy has a neutral name and no description. In the design's names, values, and descriptions, your name, username, email addresses, and phone numbers are replaced with placeholders, and email addresses are replaced everywhere else in the design. Other technical fields, such as the identifier of a parts library or a file embedded in the design, are kept as they are and can contain a name you gave them. Beside it we keep a few labels about the project (what you were building, whether you got what you asked for, what got in your way, how frustrated you seemed, and how experienced you seemed), some counts (such as how many of your recent messages we read and how many times the board was routed), and which plan you were on. The chats themselves are deleted, unless the project is kept for a manufacturing order (below). To make the labels, TypeSafe reads up to the 40 latest messages in the project's chats, yours and Rocky's, with email addresses, phone numbers, and long key-like strings masked. Other details in those messages, such as names, are not masked. We keep only TypeSafe's labels, never the text. If a board has no chat, or TypeSafe cannot label it, we archive it without labels. We do this on the basis of our legitimate interest in improving the Service. A board that is not fully routed is not archived.
Projects with a manufacturing order. A project you placed a manufacturing order for is kept whole, its chats included, together with its order. We take it off Community, and people who share the workspace it is in keep their access to it. We delete it six years after the end of our financial year in which its orders last changed state (for example, were delivered or cancelled), or later while one of its orders is still open with the manufacturer, or where the law requires it or we need it for a legal claim. Our financial year ends on 31 October. We keep it for the same reasons as the order records below: to meet our tax and accounting obligations and to handle legal claims.
Community. Boards you published to Community stay there for others to view and copy. In every credit we hold, including copies other users already made on siliXon, your username becomes "siliXon user". Files someone already downloaded keep the credit they had. To take a board down, delete its project before you delete your account.
Analytics. While your account is locked, the app stops linking your visits to your account in PostHog as soon as it learns of the lock. When we delete your account, our servers stop sending PostHog anything about it, and we ask PostHog to delete the person linked to your account with its events and session recordings, then ask again 30 minutes later. Until the app resets it, a browser you were signed in on can still send analytics under your old PostHog ID, such as page views or a session recording, even after these deletions.
Feedback. Bug reports and feedback you sent us are kept for our team to read, no longer linked to your account. Copies already sent to Linear, Discord, or our team's inbox keep what they contained, which can include your email address.
Records we keep after deletion. We keep records of payments and manufacturing orders, including invoices, for six years after the end of the financial year they belong to, as UK tax and accounting law requires, or longer where the law requires it (for example during a tax inquiry). We use these records only to meet those obligations, to handle legal claims, and to complete or reconcile an order that is still open with the manufacturer. If you delete your account, we delete our records of your orders, checkouts, and purchases six years after the end of our financial year in which each last changed. We keep them longer where the law requires it or we need them for a legal claim, and we keep an order while it is still open with the manufacturer. Our record of a subscription follows Stripe, which keeps its own. Once your account is deleted, these records no longer carry your name or email address, except an order's delivery contact details until they are deleted. Delivery contact details for a manufacturing order (name, address, phone number, and email address) are deleted 90 days after the order is placed with the manufacturer, cancelled, or refunded, unless we need them for a legal claim. If you delete your account, they go sooner (again unless we need them for a legal claim): in our next cleanup run for an order that was never sent on or is waiting for your answer, and otherwise once the order is delivered or cancelled. When we delete your account we also delete your customer record at Stripe. Stripe, PCBWay, and JLCPCB keep their own records of your payments and orders under their own privacy policies, and we cannot delete those for you.
Boards removed from Community by moderation are deleted 30 days after removal, unless we need them for an open review.
6. Cookies and local storage
The Service uses cookies and browser local storage to keep you signed in. We also use PostHog cookies and local storage for product analytics, performance and error monitoring, and session recordings to understand and improve the Service. Our website also uses Google Analytics cookies to measure visits. We do not use third-party advertising cookies.
7. Security
Data is encrypted in transit and access to production systems is restricted. No system is perfectly secure, so we cannot guarantee absolute security. Please use a strong, unique password.
8. Your rights
Depending on where you live (including under UK and EU GDPR), you may have the right to access, correct, export, restrict, or delete your personal data, and to object to certain processing. To exercise any of these rights, email hello@silixon.io. You can also delete your account yourself (see section 5). You also have the right to complain to your local data protection authority.
9. Children
The Service is not directed at children under 16, and we do not knowingly collect their data. If you believe a child has provided us personal data, contact us and we will delete it.
10. Changes to this policy
We may update this policy as the Service evolves. If a change is material we will give you reasonable notice (for example by email or an in-product notice). The "Last updated" date above always reflects the current version.
See also our Terms of Service.