Philterd

Talk to the Team

Tell us about your stack and the privacy problems you're trying to solve. We typically respond within one business day.

Prefer email? support@philterd.ai

Prefer to skip the form? Pick a time on our calendar →
or send a message

Please do not enter PII or PHI in this form. If you need to share an example, use a sanitized one.

PhiSQL Trademark and Conformance Policy

How to use the PhiSQL name: the permitted descriptive uses, and the conformance and registration rules for PhiSQL-conformant and PhiSQL-certified claims.

“PhiSQL” is a trademark of Philterd, LLC. PhiSQL is an open specification with an Apache 2.0 reference implementation. This policy explains how you may use the PhiSQL name when you build on, integrate with, or describe an implementation of PhiSQL, and what it means to claim that an implementation is conformant. The goal is to keep the name meaningful: anyone can build on PhiSQL and say so, while claims of verified compatibility stay trustworthy.

In short

  • You may use the PhiSQL name descriptively without asking us, for example “compatible with PhiSQL” or “PhiSQL parser,” as long as the use is truthful and does not imply that Philterd endorses or produced your product.
  • You may not describe your implementation as “PhiSQL-conformant” or “PhiSQL-certified” unless it passes the published PhiSQL conformance suite for a stated specification version and is registered with Philterd.

The marks

This policy covers the word mark “PhiSQL” and any PhiSQL logos Philterd publishes. It does not grant any rights in Philterd’s other marks (for example “Philter,” “Phileas,” or “Philterd”).

Permitted uses (no permission needed)

You may use the PhiSQL name to describe your product’s relationship to PhiSQL accurately, including:

  • “compatible with PhiSQL”
  • “PhiSQL parser” / “a parser for PhiSQL”
  • “based on PhiSQL” / “implements the PhiSQL specification”
  • “supports PhiSQL”

These descriptive uses are permitted provided that:

  1. The statement is truthful and not misleading.
  2. You do not imply that Philterd sponsors, endorses, or is affiliated with your product beyond the relationship that actually exists.
  3. You do not use “PhiSQL” as, or as part of, your product name, company name, domain name, or logo in a way that could confuse users about the source of your product.
  4. You make clear that PhiSQL is a trademark of Philterd, LLC where reasonable.

Restricted uses (require conformance and registration)

The terms “PhiSQL-conformant” and “PhiSQL-certified” claim a verified level of compatibility, so they are reserved. You may use them only if both of the following are true:

  1. Your implementation passes the published PhiSQL conformance suite for a stated specification version, and
  2. You have registered the implementation with Philterd and it is listed on the PhiSQL conformance listing.

When you make such a claim, state the specification version it applies to (for example “PhiSQL-conformant (PhiSQL v1.0)”). A conformance claim applies only to the specific version tested.

What conformance means

An implementation is conformant for a given specification version when it passes that version’s conformance suite in the PhiSQL repository. The suite, and the process for proposing changes to the specification, are described in the repository’s contributing guide. Conformance is defined per specification version because the specification evolves; passing one version does not imply conformance with another.

Registration process

To list an implementation as conformant:

  1. Run the conformance suite for the specification version you target and capture the results.
  2. Submit a request to Philterd with your implementation’s name, version, the specification version it targets, the conformance results, and a contact. Submit it through the PhiSQL repository (an issue or pull request) or by emailing support@philterd.ai.
  3. Philterd reviews the submission and, when satisfied, adds the implementation to the PhiSQL conformance listing.

Registration confirms that, at the time of review, the implementation passed the stated suite. It is not an ongoing warranty by Philterd about the implementation.

Revocation

Philterd may revoke permission to use the restricted terms and remove an implementation from the conformance listing if the implementation no longer passes the conformance suite for a version it claims, if the claim is inaccurate or misleading, or if the name is used in a way that breaches this policy. Where practical, Philterd will give notice and a reasonable opportunity to correct the issue first. On revocation, the implementation must stop describing itself as PhiSQL-conformant or PhiSQL-certified.

General conditions

  • Do not alter the PhiSQL marks or combine them with your own marks in a way that creates a single combined mark.
  • Do not use the PhiSQL marks in a manner that disparages Philterd or its products.
  • All use of the PhiSQL marks benefits Philterd, LLC, which reserves all rights not expressly granted by this policy.

Questions and changes

Questions about this policy, or requests not covered by it, can be sent to support@philterd.ai. Philterd may update this policy from time to time; the current version is the one posted here.