Gravity and Gravity Forms are trademarks of Rocketgenius, Inc. Throughout this policy, we use “Marks” to refer collectively to our names, logos, icons, slogans, design elements, trade dress, and other brand identifiers, whether registered or unregistered, that we use to identify and distinguish our products and services. Our Marks include Gravity, the Gravity “G” logomark, and the names of individual Gravity products and services (Gravity Forms, Gravity SMTP, Gravity Flow, Gravity CRM, Gravity Checkout, Gravity Experts, and others).
The list above is not exhaustive. The absence of a name, logo, or mark from this list does not waive any intellectual property rights we have in our product, feature, or service names or logos.
We ask that you follow the guidelines below when referring to our products so we can protect our Marks and avoid user confusion.
Why we have this policy
We see sites and products that misrepresent our brand, distribute modified versions of our software with malware embedded, or trade on the trust users have in our name. When that happens, users either blame us for the issue or come to us for help with software we did not produce. A clear naming policy reduces that confusion and protects the users we serve.
This policy is also about clarity for the ecosystem. The naming space around our Marks needs to be predictable so that customers can tell at a glance what is an official Gravity product and what is a third-party product built for the platform.
What this policy covers
This policy applies to uses of:
- “Gravity” as a standalone product name. Gravity is the parent platform that contains all of our products and services.
- “Gravity Forms” and the names of any other Gravity products.
- Names that combine “Gravity” with another word in a way that suggests an official product, service, feature, program, or affiliation.
- The Gravity logo, the Gravity “G” logomark, and the logos of individual Gravity products and services.
Domain and subdomain names
Do not use “Gravity,” “Gravity Forms,” or the name of any Gravity product in a domain name or subdomain in a way that suggests an official Gravity site, product, service, team, program, or affiliation with Rocketgenius, unless you have written permission from us.
This includes confusingly similar variations, misspellings, spacing changes, or singular/plural forms, such as “Gravity Form,” “GravityForms,” or “Gravity-Forms.”
Examples of constructions that would not be permitted:
gravityforms.example.comgravityaddons.comgravitymcp.comgravityforms-tutorials.com
These examples are illustrative, not exhaustive.
Acceptable domain alternatives:
“GF” for example, gf-tutorials.com, learn-gf.com
Descriptive names that do not lead with our brand, for example, formtips.com, webformhelp.com
If you already own a domain that includes one of our Marks, redirecting it to a non-infringing domain is permitted, provided the destination site does not itself use our Marks in its domain or subdomain, and provided you stop actively promoting the original domain in your marketing, documentation, and links.
A useful rule of thumb: if the domain, subdomain, or site could plausibly be mistaken for an official Gravity site or one operating on our behalf, do not use it.
Product and company names
Do not name a product, service, plugin, theme, app, SaaS tool, agency, or company in a way that suggests it is an official Gravity product or an official extension of one.
This means avoiding:
- Product names of the form “Gravity [Word]” (e.g., “Gravity Helper,” “GravityTools,” “Gravity Pro Pack”).
- Company names that lead with “Gravity” in a context where customers would reasonably assume affiliation with us.
- Names that mimic the cadence or structure of our product naming (e.g., “Gravity Mail,” “Gravity Workflow”). These read as official apps even when they are not.
Not allowed: “Gravity Toolkit,” “Gravity Helper,” “GravityForms Pro Pack”
Allowed: “Cosmic Toolkit for Gravity Forms,” “FormHelper, an add-on for Gravity Forms”
Not allowed: “Gravity Agency,” “The Gravity Group,” “Gravity Forms Pros”
Allowed: “Apogee Consulting, a Gravity Forms development firm,” “Parallax Studio, specializing in Gravity Forms development”
The same rules apply to agencies, consultancies, and service businesses. A consulting company can describe its business as “123 Web Services, offering Gravity Forms development for small businesses,” but cannot call its business “The Gravity Forms Consulting Company” or “The Gravity Pros.” A theme shop can describe itself as “XYZ Themes, makers of premium themes for Gravity Forms,” but cannot call itself “Gravity Themes” or “The Gravity Theme Portal.”
Managed services, cloud services, and SaaS built on Gravity
If you provide a managed service, hosted installation, cloud service, SaaS product, API offering, or fully-managed implementation that includes or is built on Gravity software, the same naming rules apply. Your service is yours, not ours. You may describe your offering as built on or providing Gravity Forms, but you may not name it as if it were an official Gravity service.
Not allowed: “Hosted Gravity Forms,” “Managed Gravity,” “Gravity Cloud,” “Gravity Hosting,” “GravitySaaS,” “Gravity API,” “Gravity Forms-as-a-Service”
Allowed: “ParallaxCloud, managed hosting for Gravity Forms,” “ApogeeHost, a fully-managed Gravity Forms service”
Managed services must not use our logos or imply that Rocketgenius is the source, sponsor, or approver of the service.
App store and marketplace listings
The same rules apply to listings on WordPress.org, the Chrome Web Store, npm, Packagist, GitHub, the Shopify app store, and similar platforms. Do not title a listing in a way that uses our Marks as the lead element of your product name.
Allowed: “Acme Smart Fields, an add-on for Gravity Forms”
Not allowed: “Gravity Smart Fields” or “GravityForms Smart Fields”
This also applies to plugin and repository URL slugs. A WordPress.org slug should be cosmic-smart-fields rather than gravity-smart-fields or gravityforms-smart-fields. The same applies to GitHub repository names, npm package names, and Packagist identifiers. This includes organization names, package scopes, vendor prefixes, namespaces, and repository owners on developer platforms.
Social media handles and account names
Do not register social handles, channel names, or account names that use “Gravity” or “Gravity Forms” as the lead element in a way that suggests an official account.
Not allowed: @gravity_tutorials, @gravity_tools, Gravity Tips on YouTube
Allowed: @CosmicStudios with “Gravity Forms tutorials” in the channel description, @FormHelperPro
Logos and visual identity
Do not use the Gravity logo, the Gravity “G” logomark, or any logo or visual identity used by an individual Gravity app, as part of your own logo, product icon, app icon, or favicon. Our logos may not be incorporated, modified, or imitated in third-party branding. Do not create derivative logos, and do not intentionally imitate the distinctive overall look and feel of our branding in a way that is likely to confuse users about the source, sponsorship, or affiliation of a product or service.
For approved logo usage in articles, tutorials, integration listings, and marketing materials that reference our products, see our Brand Assets page.
Acceptable use of our Marks
Across domains, product names, listings, and social handles, the same general principles apply:
- Lead with your own brand. Use the Gravity or Gravity Forms name only as a descriptor that follows your brand. Example: “Acme Toolkit for Gravity Forms,” not “Gravity Toolkit by Acme.”
- Use “for Gravity” or “for Gravity Forms” as a descriptor, never as the lead element of your name.
- Use “GF” in technical or developer-facing contexts where it functions as shorthand rather than a brand element.
Truthful descriptive references to our products are always permitted, including:
- “Works with Gravity Forms”
- “An add-on for Gravity Forms”
- “Built on the Gravity platform”
- “Compatible with Gravity”
Legitimate nominative fair use of our Marks, to accurately describe compatibility, integrations, commentary, reviews, tutorials, or support relating to our products, is permitted under this policy.
The test in every case: would a reasonable customer assume your product, site, or account is officially produced by or affiliated with us? If yes, change the name. If no, the use is likely permissible under this policy.
Non-affiliation disclaimer
If your site, product page, course, tutorial library, marketplace listing, or channel is primarily about Gravity products, include a clear statement of non-affiliation, such as:
“This site is not affiliated with, endorsed by, or sponsored by Rocketgenius, Inc. Gravity, Gravity Forms, and other Gravity product names are trademarks of Rocketgenius, Inc.”
A disclaimer does not cure an otherwise confusing name, logo, domain, or presentation. If your site is named or styled in a way that suggests affiliation, the disclaimer alone is not sufficient. The name or styling must also change.
Affiliation and partnership claims
Do not describe yourself, your product, or your service as official, certified, approved, endorsed, sponsored, or partnered with Gravity or Rocketgenius unless we have given you written permission. This applies to marketplace listings, agency pages, social media accounts, YouTube channels, support sites, course descriptions, and any other public-facing materials.
If you participate in one of our official programs (such as our Certified Developer program), the terms of that program govern how you may describe your relationship with us.
Use of our Marks in a descriptive manner does not imply approval, endorsement, sponsorship, certification, or partnership unless we have expressly agreed otherwise in writing.
Advertising and search listings
Do not use our Marks in advertisements, search listings, page titles, metadata, or promotional copy in a way that suggests your product, service, or site is official, endorsed, or operated by Rocketgenius.
Affiliates, partners, and certified developers may be subject to different terms in their agreements with us.
Existing third-party usage
If you have an existing agreement with us covering your use of our Marks, that agreement governs. If you do not have an agreement and would like to discuss one, please contact us. We are open to conversations with established ecosystem participants whose use of our Marks predates this policy, but going forward, continued use may require changes to the use or, in some cases, a written agreement.
Reporting and contact
If you find a site, product, or account that uses our Marks in a way that conflicts with this policy, please contact us so we can reach out to the owners.
If you are unsure whether your intended use is permitted, write to us first. We would rather answer questions early than resolve confusion later through a formal notice or enforcement process.
Reservation of rights
This policy does not grant a trademark license or transfer any rights in our Marks. We reserve all rights not expressly stated in this policy, including the right to object to uses that we believe are likely to cause confusion, misuse our brand, or harm users.
Any reputation or value built through use of our Marks belongs to us, not to the party using them.
We may review use of our Marks at any time and request reasonable changes to bring uses into compliance with this policy. Where uses cannot be brought into compliance, we may require that use of our Marks be discontinued.
Open source software vs. trademarks
While some of our software may be open source, our Marks are not. Any open source license that applies to our code does not extend to our Marks. They remain the exclusive property of Rocketgenius, Inc.
You may be entitled to fork, modify, and redistribute the code in accordance with the open source license applicable. However, you must give your fork or modified version its own name that is not similar to any of our Marks, and you must remove all of our Marks from your fork. This includes our names, logos, and other Marks wherever they appear in the code, user interface, headers, strings, documentation, or any other component of the software. You may use our Marks only in descriptive text to truthfully describe your fork’s relationship to our software.
Acceptance of this policy
By using our Marks, you acknowledge that you have read and agree to comply with this policy. Any use of our Marks constitutes acceptance of this policy. If you do not agree with these terms, you may not use our Marks except as permitted by law (such as nominative fair use).
We may update this policy from time to time. Continued use of our Marks after any changes constitutes acceptance of the revised policy.