FI3LD Early Access Privacy Policy
Last updated: July 2, 2026
Effective date: July 2, 2026
This Early Access Privacy Policy explains how FI3LD collects, uses, stores, shares, and protects personal information during FI3LD's early-access period.
Who We Are
"FI3LD", "we", "us", and "our" mean Diego Mínguez de León, an individual based in L'Alfàs del Pi, Alicante, Spain, unless FI3LD is later operated by a company or other legal entity.
Privacy contact: contact@fi3ldalpha.com
Support: support@fi3ldalpha.com
What FI3LD Is
FI3LD is an early-access workspace for writing, files, maps, windows, publishing, and collaboration. Early access is seat-limited and may change over time. The first 1,000 approved seats are free; after those seats are full, FI3LD may process one-time paid access purchases through Stripe. FI3LD also supports optional donations through Stripe.
Information We Collect
Account And Access Information
We collect information needed to create and manage accounts, including email address, display name, username/profile information you provide, Supabase authentication identifiers, Google OAuth information if you use Google login, early-access status, waitlist status, free or paid app access status, and related security metadata.
Payments And Donations
If you buy paid early access or donate, Stripe processes payment details. FI3LD stores payment metadata needed to grant or revoke paid access, keep donation records, show public donations when you choose a public donation, handle refunds/disputes, and meet tax or legal obligations. Private donations are not shown in the public Top Donations list.
User Content And Files
FI3LD stores content you create, upload, import, or choose to publish, including text documents, file names, folders, maps, linked-file relationships, versions, branches, revision history, PDFs, images, audio, code, markdown, binary files, comments, collaboration metadata, share-link metadata, and publishing metadata.
User content is private by default unless you publish it, create a public/share link, invite collaborators, or otherwise choose to disclose it.
Technical And Usage Information
We may collect IP address, browser, device, operating system, app version, approximate region, log data, request metadata, error data, security events, abuse-prevention data, authentication cookies/tokens, OAuth state cookies, consent state, UI preferences, shortcuts, and local app configuration.
Bug Report Diagnostics
FI3LD may use PostHog only for bug-report diagnostics and related product debugging evidence. This may include bug-report context, diagnostic metadata, client errors, and session or user identifiers where available. FI3LD does not use PostHog for advertising during early access.
Bug Reports And Support
If you submit a bug report or contact support, we collect the information you send and metadata needed to respond. Bug reports may include route/context metadata, screenshots, console entries, client errors, selection diagnostics, persistence diagnostics, file integrity diagnostics, submission metadata, and PostHog IDs where available.
How We Use Information
We use information to:
- provide, maintain, secure, debug, and improve FI3LD;
- create and authenticate accounts;
- manage early access, seats, waitlists, and access state;
- store, sync, version, export, publish, share, and collaborate on files;
- send service emails;
- provide support and investigate bugs;
- prevent abuse and enforce terms;
- comply with law;
- process early-access paid access and donations through Stripe.
How We Share Information
We share information with providers only as needed to operate FI3LD, process user-requested features, provide support, secure the service, or comply with law.
Current early-access providers are Supabase for backend services, Vercel for hosting, PostHog for bug-report diagnostics, and Stripe for paid access and donations.
The early-access provider list is in legal/early-access/subprocessors.md.
Cookies And Local Storage
FI3LD uses cookies, local storage, IndexedDB, and similar technologies for authentication, sessions, OAuth redirects, consent, preferences, local cache/outbox, recovery support, security, bug-report diagnostics, and payments or donations.
FI3LD does not currently use advertising cookies, remarketing cookies, affiliate tracking, or third-party ad pixels.
Legal Bases
For users in the European Economic Area, United Kingdom, or similar jurisdictions, our legal bases may include contract, consent, legitimate interests, and legal obligation.
Examples include contract for accounts/files/features you request and payments or donations, legitimate interests for security/debugging/reliability/abuse prevention, consent where required, and legal obligation for lawful compliance and payment/tax requirements.
Data Retention
FI3LD is still in early access and retention schedules are not final.
During early access:
- Account information is kept while your account exists.
- Workspace files, documents, versions, branches, and uploaded assets may be kept while your account exists and may remain in version history, backups, published copies, collaborator copies, or logs.
- Deleted files may be soft-deleted and retained for recovery.
- Public/published files may remain available until unpublished, archived, disabled, or removed.
- Support, security, access, and operational logs may be retained as needed for service operation, security, legal compliance, and dispute resolution.
FI3LD does not currently provide a complete self-serve account deletion or export flow. Requests may require manual handling during early access.
Your Choices And Rights
You can choose what content you create, upload, publish, or share; avoid submitting bug reports with private content you do not want reviewed for debugging; and unpublish or stop sharing files where controls exist.
Depending on where you live, you may have rights to access, correct, delete, export, restrict, object to, or withdraw consent for personal information. Contact contact@fi3ldalpha.com to make a request.
Children's Privacy
FI3LD is not intended for children under 14, and we do not knowingly collect personal information from children under 14. If you believe a child under 14 has provided personal information to FI3LD, contact us.
If you are under the age required by your country or region to consent to online services, you may use FI3LD only with permission from a parent or legal guardian where required.
FI3LD is not currently a school-managed education service.
Sensitive And Regulated Information
FI3LD is a general note-taking and file workspace. It is not currently designed for regulated medical records, protected health information, payment-card storage, government identity records, highly sensitive financial data, attorney-client systems, or other regulated workflows unless we expressly say otherwise in writing.
Security
We use technical and organizational measures intended to protect FI3LD, including provider security controls, authentication, access controls, database policies, private storage policies, encrypted transport where supported, and operational safeguards.
FI3LD does not claim end-to-end encryption. FI3LD server-side features may process plaintext content for collaboration, save/versioning, previews, exports, support, security, and bug reports.
No online service is completely secure. During early access, bugs, downtime, sync issues, and data loss may occur. Keep independent backups of important content.
International Transfers
FI3LD and its providers may process information in Spain, the European Economic Area, the United States, and other countries. Where required, we will use appropriate transfer safeguards, such as provider data processing terms or standard contractual clauses.
Changes
We may update this Policy as FI3LD changes. We will post the updated version and update the "Last updated" date. If changes are material, we will provide additional notice where appropriate.
Contact
Privacy questions and requests: contact@fi3ldalpha.com
Support: support@fi3ldalpha.com