Privacy Policy – Piecelet Connect
Effective date: 15 November 2025
This Privacy Policy explains how Piecelet Connect (“we”, “us”, or “our”) collects, uses, stores, and protects information when you use the Piecelet Connect online service (the “Service”), including when you connect your NeoDB accounts.
This Privacy Policy applies only to Piecelet Connect. The Piecelet apps you install on iOS, macOS, or other platforms are covered by the Piecelet Privacy Policy published on the main Piecelet website.
1. Data controller
For Piecelet Connect, the data controller is the maintainer(s) of the Piecelet project operating the piecelet-online-services infrastructure. You can reach us using the contact information described
in the “Contact us” section below.
2. Relationship with Piecelet app and NeoDB instances
2.1 Piecelet Connect is an optional online service. You can use the Piecelet app without using Piecelet Connect, and you can use Piecelet Connect with other clients.
2.2 This Privacy Policy does not apply to the Piecelet app itself or to any NeoDB instance you connect to. Each NeoDB instance is operated by its own provider, under its own terms and privacy policies. We do not control or operate NeoDB instances.
2.3 When you authorize Piecelet Connect on a NeoDB instance, you create a direct authorization relationship between yourself and that instance. Piecelet Connect acts as a technical intermediary that uses the access tokens you grant to perform limited actions on your behalf.
2.4 The Service is not intended to be offered to, and should not be used by, individuals or entities that are located in, ordinarily resident in, or organized under the laws of jurisdictions that do not have effective legal jurisdiction over the Service, including the People’s Republic of China, the Hong Kong Special Administrative Region, and the Macao Special Administrative Region. If you nonetheless access Piecelet Connect from such jurisdictions, you do so at your own risk and you acknowledge that the protections and rights described in this Policy are interpreted primarily under the laws identified in the “Governing law and jurisdiction” section of the Terms of Service.
3. Information we collect
We collect and process the minimum information needed to operate Piecelet Connect securely and reliably. Depending on how you use the Service, this may include:
3.1 Account and profile information
- Identifiers: an internal user ID, the external account handle from NeoDB (for example
@username@instance), and the account ID returned by the instance. - Contact details: the email address provided by the NeoDB instance, where available, and your display name.
- Profile data: optional avatar URL and username, as provided by the NeoDB instance.
3.2 Authentication and session data
- Session records: session ID, session token, creation and expiration timestamps, and an internal user reference.
- Device and network metadata: IP address, user agent string (browser or client information), and limited geolocation metadata derived from Cloudflare’s edge network, such as timezone, city, country, region, region code, data center (colo), and approximate latitude/longitude based on network routing.
- Cookies: authentication cookies used to keep you signed in across requests and sub‑domains.
3.3 NeoDB OAuth data
- OAuth tokens: access tokens and, where provided by the instance, refresh tokens and token scopes. Tokens are associated with the NeoDB instance you chose and with your internal user record.
- OAuth client registration data: for each NeoDB instance, we may store the client ID, client secret, and redirect URI that Piecelet Connect uses to perform the OAuth flow.
- OAuth state: temporary state values and callback URLs created during the authorization flow to prevent forgery and link the callback to your original request.
3.4 Logs and diagnostic information
- Server logs: limited technical logs (such as timestamps, request paths, error messages, and anonymized identifiers) used for debugging, abuse detection, and monitoring.
4. How we use your information
We use the data described above for the following purposes:
- to authenticate you and maintain secure sessions for Piecelet Connect;
- to initiate and complete OAuth flows with the NeoDB instances you choose, within the scope you authorize;
- to perform requests to NeoDB instances on your behalf, within the scope you authorize;
- to protect the Service against abuse, spam, and malicious activity;
- to monitor performance, debug issues, and improve reliability;
- to comply with applicable legal obligations and honor binding orders issued by courts or authorities that have jurisdiction over the Service, as further described in Sections 8, 9 and 12 of this Policy.
We do not sell your personal data and do not use Piecelet Connect data for targeted advertising.
5. Cookies and similar technologies
Piecelet Connect uses cookies and similar technologies only where necessary to provide the Service, including:
- session cookies that keep you signed in and associate your browser with your session; and
- cookies or equivalent mechanisms used to maintain security and prevent fraud.
We do not use Piecelet Connect cookies for cross‑site advertising tracking. If you block or delete all cookies, the Service may not function correctly.
6. Data retention and token redaction
6.1 We retain personal data only for as long as necessary to provide the Service, to meet legal obligations, or to protect our rights.
6.2 NeoDB access tokens are central to how Piecelet Connect works. To reduce risk, the Service applies specific token revocation and redaction policies:
- When you sign out, we attempt to revoke your NeoDB access tokens on the corresponding instances and
then replace the stored token values with an irreversible placeholder string (for example,
ACCESS_TOKEN_REDACTED_AT_...). - A scheduled background job regularly scans for NeoDB accounts whose tokens have not been updated for more than 24 hours. For those stale tokens, the Service attempts to revoke them at the instance level and then redacts them in our database in the same way.
6.3 Account and session records (including geolocation metadata) may be retained for a reasonable period after tokens are revoked or redacted, for purposes such as security auditing, abuse prevention, and compliance with the laws that apply to the Service.
6.4 Where feasible and legally permissible, we may further anonymize or aggregate data for statistical and reliability‑improvement purposes. Once data is anonymized, it is no longer considered personal data.
7. Legal bases for processing
Depending on your jurisdiction, we rely on one or more of the following legal bases to process your data:
- Contract necessity: processing that is necessary to provide the Service you request, including authentication and account linking.
- Legitimate interests: processing to secure the Service, prevent abuse, monitor performance, and improve reliability, where these interests are not overridden by your rights and freedoms.
- Legal obligations: processing required to comply with the laws and binding orders of competent authorities in the jurisdictions that govern the Service, primarily the United States (including the State of Delaware), Canada, and member states of the European Union, and not the laws of other countries that do not have jurisdiction over the Service.
- Consent: where required by law, we may rely on your consent, which you can withdraw at any time (for example, by revoking access on a NeoDB instance or signing out).
8. How we share information
We do not sell your personal data. We share information only in the limited circumstances described below:
- Infrastructure providers: We use Cloudflare and other service providers to deliver networking, storage, and compute. These providers may process your data on our behalf under data‑processing terms.
- NeoDB instances: When you authorize Piecelet Connect, we exchange data with the NeoDB instance you selected, within the scope of the OAuth flow (for example, sending authorization codes and receiving tokens and basic profile data).
- Legal and safety: We may disclose information where we are legally compelled to do so by a court order or governmental request that is valid and enforceable in a jurisdiction that governs the Service (primarily the United States, Canada, and the European Union), or where we reasonably determine that disclosure is necessary to protect our rights, your safety, or the safety of others. As a matter of policy, we do not voluntarily honor or respond to legal demands that originate solely from jurisdictions that do not have effective legal authority over the Service, including but not limited to the People’s Republic of China, the Hong Kong Special Administrative Region, and the Macao Special Administrative Region, except to the extent we are independently required to do so under the laws of a governing jurisdiction.
- Aggregated or anonymized data: We may share aggregated statistics or anonymized information that does not identify you.
9. Infrastructure, storage, and international data transfers
Piecelet Connect runs on Cloudflare’s edge network and data storage services, including Cloudflare Workers, D1, and KV. Data may be processed in and routed through multiple Cloudflare data centers around the world, and may not be stored in your country of residence. Cloudflare describes its security and privacy practices in its own documentation and privacy policy, including: D1 data security, D1 data location, and Cloudflare Privacy Policy.
By using the Service, you understand and agree that your data will be processed on Cloudflare infrastructure and may be transferred to, stored in, or accessed from countries whose data protection laws may differ from those in your home jurisdiction. We configure our D1 databases with Cloudflare’s “jurisdiction: none” setting, which means data is distributed across Cloudflare’s global platform rather than pinned to a single national data‑residency region. We do not intentionally operate Piecelet Connect from infrastructure that is subject to the domestic data‑access regimes of the People’s Republic of China, the Hong Kong Special Administrative Region, or the Macao Special Administrative Region, although network traffic may transit multiple countries as part of normal internet routing. Where required, we take reasonable steps to ensure that such transfers comply with applicable data protection laws in the jurisdictions that govern the Service.
10. Your rights (GDPR, CCPA, CalOPPA and similar laws)
Depending on your location and the laws that apply to you, you may have certain rights in relation to your personal data. In particular:
- Rights under the GDPR (EU/EEA and UK equivalents): If you are located in the European Union, the European Economic Area, or a jurisdiction that has adopted equivalent protections, you may have the right to access, correct, or delete your personal data; to restrict or object to certain processing; to receive a copy of your data in a portable format; and to lodge a complaint with a supervisory authority.
- Rights under the CCPA/CPRA (California): If you are a California resident, you may have the right to know what categories of personal information we collect, use, and disclose; to request access to specific pieces of personal information; to request deletion of personal information, subject to legal exceptions; to correct inaccurate personal information; and to be free from discrimination for exercising your rights. We do not “sell” personal information as that term is defined under California law.
- Rights under CalOPPA and similar laws: We aim to honor transparency and choice obligations under California’s Online Privacy Protection Act (CalOPPA) and similar state‑level privacy laws in North America, including providing clear notice of our practices and honoring browser‑level or platform‑level privacy controls where technically feasible.
Even if you are not covered by the specific laws above, you may still contact us to request access, correction, or deletion of personal data held by the Service, and we will consider your request in line with the protections described in this Policy and the laws that govern the Service (primarily the United States, Canada, and the European Union).
You can exercise many of your choices directly by revoking access on NeoDB instances, signing out of Piecelet Connect, or contacting us as described below. We may need to verify your identity before fulfilling certain requests.
11. Children’s privacy
The Service is not directed to children and is intended for use by adults and older teenagers who are capable of entering into binding agreements under applicable law. If you believe that a child has provided us with personal data without appropriate consent, please contact us and we will take reasonable steps to delete such information where required.
12. Changes to this Privacy Policy
We may update this Privacy Policy from time to time to reflect changes in our practices, technology, or legal requirements. When we make changes, we will update the “Effective date” at the top of this page. If we believe changes are material, we will use reasonable efforts to provide additional notice.
Your continued use of Piecelet Connect after an updated Privacy Policy becomes effective will constitute your acknowledgment of the changes and your agreement to the updated policy.
13. Contact us
If you have any questions, concerns, or requests regarding this Privacy Policy or our data practices for Piecelet Connect, please contact us using the contact details listed on the Piecelet website, by email at contact@connect.piecelet.app, or by opening an issue in the GitHub repository Piecelet Connect (piecelet-online-services). Because the Service is fully open source, you may also choose to review the source code, self‑host your own instance of Piecelet Connect on infrastructure you control, or opt not to use Piecelet Connect if you are uncomfortable with the data practices described here.
14. Revision history
- 15 November 2025: Initial publication of the Piecelet Connect‑specific Privacy Policy.