michele/periscope
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fase A identity on PCB HEAD: operator fence, keep BOM/SPOF/EMI.

Browse Source 
Replace Faradworks Inc. TOS/privacy/contact/metadata with Michele Bigi.
Dual-read pinscope_* keys; write periscope_* only. AGPL LICENSE and
GitHub fork parent unchanged. validate.py not edited.
This commit is contained in:
michele
2026-09-20 12:41:17 +02:00
parent 1b3529501f
commit a63e5bd7ab
25 changed files with 1561 additions and 600 deletions
Download Patch File Download Diff File Expand all files Collapse all files
frontend/content/privacy.md
+35 -153
View File
@@ -1,185 +1,67 @@
# Periscope Privacy Policy
**Last updated: April 5, 2026**
**Last updated: 20 September 2026**
This Privacy Policy explains how Faradworks, Inc. ("Faradworks," "we," "us," and "our") collects, uses, and discloses information in connection with the Periscope website (periscope.michelebigi.it), platform, and related services (the "Service").
This Privacy Policy explains how Michele Bigi ("Operator," "we," "us") collects, uses, and discloses information in connection with the Periscope instance at [periscope.michelebigi.it](https://periscope.michelebigi.it) (the "Service").
This Privacy Policy is intended for free users and self-serve paid users. Enterprise customers typically use the Service under a separate agreement and (if applicable) a data processing agreement ("DPA"), which may include additional privacy and security terms.
Faradworks, Inc. does **not** operate this instance and is not the controller for Personal Data processed here.
## 1. Key definitions
## 1. Roles
**"Customer Content"** means any files, data, text, images, netlists, schematics, datasheets, design files, chat inputs, or other materials uploaded or submitted by you.
The Operator is the controller for Personal Data used to run this instance (for example account email, authentication identifiers, and server logs).
**"Outputs"** means analyses, checks, summaries, recommendations, or responses generated by the Service based on Customer Content.
If you upload Personal Data inside design files on behalf of a business, you may be the controller of that data and the Operator may process it as a processor. A DPA can be discussed at [mikbigi@gmail.com](mailto:mikbigi@gmail.com).
**"Derived Data"** means technical artifacts generated solely to operate the Service, such as parsed text, indexes, embeddings, summaries, or extracted metadata.
## 2. Information we collect
**"Content"** refers collectively to Customer Content, Outputs, and Derived Data.
Only what is reasonably necessary:
**"Personal Data"** (or "personal information") means information that identifies, relates to, describes, is reasonably capable of being associated with, or could reasonably be linked, directly or indirectly, with an individual, as defined under applicable law.
- **Account:** name, email, password hashes / session tokens, optional organization
- **Customer Content:** netlists, schematics, datasheets, PCB files, chat context
- **Usage:** request logs, pipeline progress, API cost estimates for your runs
- **Contact form:** name, email, message
## 2. Roles: controller vs. processor (business customers)
If billing or Stripe is not enabled on this instance, we do not collect payment card data. We do not store card numbers.
Faradworks is the controller for Personal Data associated with operating the Service for users and prospective customers (for example account data, billing metadata, and website analytics).
## 3. How we use information
If you upload Personal Data within Customer Content on behalf of a business, you may be the controller of that Personal Data and Faradworks may process it as a service provider/processor. Where required, we will make a DPA available upon request.
To operate the Service: authenticate you, run reviews, store projects in instance storage, send transactional mail if configured, debug failures you report, and comply with law.
## 3. Information we collect
We do **not** use Customer Content to train general-purpose or foundation AI models unless you explicitly agree.
We collect only the information reasonably necessary to operate the Service.
Reviews may send excerpts of datasheets and circuit context to a configured model provider (for example DeepSeek). That provider processes the excerpt under its own terms.
### 3.1 Account information
## 4. Sharing
- Name, email address, and organization (optional)
- Authentication identifiers (for example password hashes, session tokens, and account IDs)
- Subscription and plan metadata
We share information with subprocessors only as needed to host and run the Service (compute, storage, email, AI APIs). We may disclose information if required by law or to protect the Operator and users from abuse or security incidents.
### 3.2 Billing information
We do not sell Personal Data. We do not share it for cross-context behavioral advertising.
- Payments are processed by Stripe, a PCI-compliant third-party processor.
- Faradworks receives billing status and subscription metadata (for example plan name, renewal date, and payment status).
- We do not store payment card details.
## 5. Retention
### 3.3 Customer Content
Project files and accounts remain until you delete them or the Operator deletes the instance data. Residual backups may persist for a limited operational window. You may request deletion at [mikbigi@gmail.com](mailto:mikbigi@gmail.com).
- Engineering files (for example netlists, schematics, datasheets, and images)
- Chat inputs and related context
- Design rules and configuration preferences
## 6. Security
### 3.4 Usage and operational data
TLS in transit, access isolation per user when authentication is enabled, and credential hashing for local accounts. No system is perfectly secure.
Usage and performance telemetry (for example request timestamps, feature usage, response times, error rates, and billing/usage measurements). This data is generally operational in nature and is designed not to include the substance of your Customer Content, except as described in Section 6.3 (Support diagnostics).
## 7. International transfers
### 3.5 Cookies and analytics preferences
This instance and its subprocessors may process data in the European Union and in other regions where providers operate (including outside the EEA). Where required, appropriate safeguards will be used.
- We use cookies and similar technologies needed for core site operations and security.
- We store an analytics preference cookie that records whether analytics tracking is granted or denied.
- When analytics is granted, we may collect site and product usage and performance telemetry through providers such as Vercel Analytics and Speed Insights.
## 8. Your rights
### 3.6 Contact and enterprise inquiry data
Depending on your jurisdiction (including GDPR/UK GDPR and, where applicable, California law), you may have rights to access, correct, delete, restrict, object, and port Personal Data, and to withdraw consent.
- Contact and profile details submitted through contact or enterprise inquiry forms (for example name, email, business type, and capacity needs)
- Interest signals (for example request for a demo, free review evaluation, or higher-limit self-serve access)
- Inquiry notes and follow-up communications related to your request
Privacy requests: [mikbigi@gmail.com](mailto:mikbigi@gmail.com) — subject line "Privacy Request".
## 4. How we use information
The Service is not directed to children under 13 (or the applicable local threshold).
We use Personal Data and Content to:
## 9. Changes
- Provide, operate, and maintain the Service
- Perform AI-assisted engineering analysis
- Enforce usage limits and prevent abuse
- Diagnose errors and improve reliability
- Respond to support requests
- Investigate support requests and Issue Reports and, where you explicitly opt in, use those submissions and the related context to evaluate, test, debug, monitor, develop, and improve the Service
- Send service-related communications, including onboarding, feedback requests, product updates, and security notices
- Review and respond to contact or enterprise inquiries, including demo requests and plan-fit conversations
- Comply with legal obligations and enforce our Terms
Material changes will be posted on the Service or emailed before they take effect.
## 5. AI model training and service improvement
## 10. Contact
### 5.1 No training on Customer Content for foundation models
Faradworks treats all Customer Content as confidential and does not use it to train, fine-tune, or improve any general-purpose or foundation AI models. Your content remains isolated to your account and is not shared across customers or included in public datasets.
### 5.2 Aggregated and de-identified service improvement
To improve and operate the Service, we rely primarily on aggregated or otherwise de-identified usage metrics (for example error rates and feature usage) that are not reasonably capable of being traced back to you.
## 6. How we share information
We do not sell Personal Data.
We may disclose information in the following circumstances:
### 6.1 Subprocessors and service providers
We use subprocessors and service providers to host and operate the Service (for example hosting, storage, authentication, billing, observability, and database providers). We may share Personal Data and Content with these providers only as necessary to provide the Service.
### 6.2 AI model providers
To generate Outputs, relevant portions of Customer Content are transmitted to AI model providers acting as subprocessors. Providers may include services such as DeepSeek, Anthropic, Google, or similar AI platforms.
These providers process Content to generate responses. Their data handling, retention, and caching practices are governed by their respective terms and our configuration.
### 6.3 Support and troubleshooting diagnostics
When needed for reliability, security, abuse prevention, or support troubleshooting, we may process account-linked technical diagnostics (for example request IDs, timestamps, stack traces, provider error payloads, and limited excerpts of inputs or outputs associated with a failing request).
If you submit a support request, submit an Issue Report, or otherwise ask us to investigate an issue with the Service, we may access and review the Customer Content, Outputs, and related Derived Data reasonably necessary to investigate, reproduce, resolve, remediate, and prevent recurrence of that issue. This may include the affected project, review results, uploaded files or excerpts, citations, configuration context, and associated diagnostics.
If, through the applicable in-product support or feedback flow, you explicitly opt in to broader improvement use, we may also use the submitted materials and the reasonably necessary related project/review context to evaluate, test, debug, monitor, support, secure, operate, develop, and improve the Service and related features, systems, and workflows, including for the benefit of other users. This may include quality evaluation, failure analysis, prompt and retrieval improvements, ranking or classification improvements, validation logic, reliability engineering, abuse prevention, and other product-quality, safety, and operational improvements.
We limit this access and use to authorized personnel and permitted service-related purposes. We do not use this content to train, fine-tune, or improve any general-purpose or foundation AI model unless you separately and expressly opt in to that use.
Outside of those circumstances, we do not access or review the substance of your Customer Content except: (a) at your request, (b) to investigate security issues or incidents, (c) if legally compelled, or (d) with your explicit consent.
### 6.4 Legal and safety
We may disclose information to comply with applicable law, lawful requests, and legal process; to protect the rights, property, and safety of Faradworks, our users, and others; and to enforce our agreements and policies.
### 6.5 Business transfers
If Faradworks is involved in a merger, acquisition, financing, reorganization, bankruptcy, or sale of assets, information may be transferred as part of that transaction, subject to standard confidentiality protections.
## 7. Cookies and analytics controls
You can control analytics cookies through the in-product or site controls (where available) and through your browser settings. If you deny analytics cookies, we will not run optional analytics tracking, but essential cookies may still be required for core functionality and security.
## 8. Data retention and deletion
### 8.1 User-controlled deletion
You may delete uploaded files, chats, and review history from within the Service (where available) and you may request closure of your account.
### 8.2 Retention periods
**Active accounts.** We retain Customer Content and Outputs for as long as your account remains active, unless you delete them earlier.
**Account closure.** When you close your account (or we close it at your request), we will delete Customer Content and Outputs associated with your account within 30 days, except where retention is required by law or for legitimate business purposes described below.
**Backups.** Residual metadata or encrypted backups may persist for a limited period (generally up to 90 days) for security, integrity, and disaster-recovery purposes.
**Operational artifacts.** We may retain limited technical artifacts (for example hashed identifiers, aggregated statistics, and anonymized error metadata) for security, abuse prevention, system integrity, and service improvement. These artifacts are not intended to and are not reasonably capable of reconstructing your original designs.
**Support and improvement records.** If you submit a support request or an Issue Report, we may retain the support record, related investigation notes, and the limited associated project/review context needed to document, resolve, and prevent recurrence of the issue. If you explicitly opt in to broader improvement use, we may also retain the submitted materials and related analyses for the service-improvement purposes described in this Policy, subject to the same confidentiality and deletion framework described in this Policy.
**Billing and accounting.** We retain billing records and aggregated usage statistics as required by law and for legitimate business purposes (for example taxes, accounting, and audit).
## 9. Security
We use commercially reasonable administrative, technical, and organizational safeguards designed to protect information, including encryption in transit (TLS) and at rest, per-user access isolation, secure credential management, and monitoring. No system is perfectly secure.
## 10. International data transfers
By default, the Service is hosted in the United States. If you access the Service from outside the United States, information may be transferred to, stored in, and processed in the United States and other countries where we or our subprocessors operate. Where required, we will use appropriate safeguards for international transfers (for example contractual protections in a DPA).
## 11. Your rights and choices
### 11.1 GDPR/UK GDPR
Depending on your jurisdiction, you may have rights to access, correct, delete, restrict, object to processing, and port your Personal Data. You may also have the right to withdraw consent where processing is based on consent.
### 11.2 California (CCPA/CPRA)
If you are a California resident, you may have rights to know, access, delete, correct, and opt out of the "sale" or "sharing" of Personal Data, and to limit the use of "sensitive personal information," as those terms are defined under California law. Faradworks does not sell Personal Data. We do not share Personal Data for cross-context behavioral advertising.
### 11.3 How to exercise rights
Privacy requests (data access, deletion, correction): dev@faradworks.com
For faster handling, use subject line: "Privacy Request (Access/Deletion/Correction)".
We will respond to verified privacy requests within applicable legal timelines (typically within 30 days for GDPR requests).
## 12. Children
The Service is not directed to children, and we do not knowingly collect Personal Data from children under 13 (or under the age threshold applicable in your jurisdiction).
## 13. Changes to this Privacy Policy
We may update this Privacy Policy from time to time. If we make material changes, we will provide reasonable notice by email or by posting a notice on the Service before the changes take effect. The updated policy will be effective as of the "Last updated" date unless otherwise stated.
## 14. Contact
Questions about this Privacy Policy: [dev@faradworks.com](mailto:dev@faradworks.com)
Michele Bigi
[mikbigi@gmail.com](mailto:mikbigi@gmail.com)