Request Themes & Plugins or Get New Updates
Can’t find your favorite WordPress item? Submit a request above, and we’ll add it to our repository!
Important: Extract Before Uploading
After downloading a file from our website, unzip it first. The main zip file may contain additional folders like templates, documentation, or other resources. Ensure you upload the correct file to avoid errors.
How to Install Plugins
How to Install Themes
Request Themes & Plugins or Get New Updates
Can’t find your favorite WordPress item? Submit a request, and we’ll add it to our repository!
Buy Latest Version & Future updates
₹500.00
₹199.00
Join Our Membership to Access All Products
Download this and 12000+ Plugins & Themes as a premium member for only $7.99.
On paper, adding Terms Of Service acceptance to a form sounds trivial. In practice, it is one of the most common places I see teams lose conversions, collect invalid consent, or ship a form that looks compliant but fails under review.
Gravity Perks Terms Of Service is built for the moment when “just add a checkbox” is not enough. You need the right text, the right link behavior, a reliable way to store what the user agreed to, and predictable validation across multi-page forms and conditional fields.
I have broken this setup more than once on live sites. Most failures were not dramatic. They were small, easy-to-miss details like a checkbox that could be prefilled by a browser, a hidden agreement field that still validated, or a multi-page form where the acceptance state did not carry forward the way the client assumed it would.
This perk is about turning “agreement” into a controlled form component. It lets you present Terms Of Service content in a way that is harder to misunderstand and easier to audit later.
In day-to-day builds, the value shows up in three places. First, the UI is clearer for users, especially when the terms are long. Second, the acceptance is validated consistently, so you do not end up with entries that slipped through without consent. Third, it reduces the amount of custom theme or snippet work you would otherwise do to make terms readable and accessible.
If you are expecting it to generate legal text, it will not. It is a form UX and validation tool, not a legal policy generator. You still bring your own terms and decide when you need acceptance.
It earns its keep on forms tied to accounts, payments, applications, and any workflow where you may need to prove the user actively agreed. Membership signups, service bookings, and B2B lead forms with explicit consent language are typical examples.
If you only need a casual “I agree” for a low-stakes newsletter form, you may not need a dedicated Terms Of Service experience. A standard checkbox can be fine when the legal and operational risk is low and you are not trying to standardize consent across many forms.
The fastest way to hurt form completion is to dump a wall of terms in the middle of a page and force users to scroll blindly. The second fastest is to hide the terms behind a tiny link that feels suspicious.
What works better is giving users a clean, readable way to view terms without losing their place. In one client build, we moved from a long inline terms paragraph to a controlled Terms Of Service presentation and saw fewer abandonment complaints. The form did not become “shorter”, but it felt lighter because the terms were presented intentionally.
Another practical win is consistency. When multiple departments build their own forms, terms acceptance becomes inconsistent quickly. Standardizing the pattern reduces internal review time because stakeholders stop arguing about placement and wording on every new form.
This is the classic one. A terms field gets hidden based on a selection, but validation still expects it. The fix is not always “turn off required”. You need to confirm how the field behaves when hidden and whether the agreement is actually needed for that branch of the form.
On multi-step forms, users expect their acceptance to persist. If the agreement is placed on an earlier page and the form is edited later, you can create confusing states. I have seen acceptance appear unchecked after navigating back, which erodes trust. Test forward, back, and save-and-continue flows if you use them.
It is easy to style the terms presentation so the link is not obviously a link, or the scrollable area traps keyboard focus. When I review these builds, I always tab through the field and verify the terms can be opened and read without a mouse.
Update WordPress, Gravity Forms, and your active theme. If you are running heavy caching or script optimization, plan to clear caches after activation.
Use the Gravity Perks Terms Of Service download package you obtained from your account or provider. Keep the ZIP intact. Do not unzip it unless you know you need to upload via SFTP.
In the admin area, go to Plugins, then Add New, then Upload Plugin. Select the ZIP, install, and activate. If your hosting limits uploads, use SFTP to place the plugin folder in wp-content/plugins, then activate it in the dashboard.
Go to the Gravity Perks settings area and verify that Terms Of Service is available. If it is listed but not applying to any form, double-check that the perk is enabled and that you have actually added the relevant field to the form.
Open a form in the editor, add the Terms Of Service component, and configure the text and link behavior. Submit the form in an incognito window. Then test on mobile and confirm the acceptance is stored in the entry data the way you expect.
After enabling caching, minification, or deferred scripts, re-test the terms display and the required validation. I have seen aggressive optimizers delay scripts in a way that makes the terms UI feel broken even though the form technically submits.
A standard checkbox field is fine for simple agreements, but it tends to drift into inconsistency. One form uses a link, another pastes the terms inline, and a third forgets to set it as required. You end up with a compliance pattern that depends on who built the form.
The other common workaround is custom HTML and JavaScript to open a modal or expand hidden text. That can work, but it is fragile. Theme changes, script optimizers, and accessibility regressions are frequent. In my experience, those custom solutions are also harder to hand off to another developer because the logic is split between the form builder, the theme, and random snippets.
Gravity Perks Terms Of Service keeps the behavior closer to the form system itself, which usually means fewer surprises when you clone forms, export/import, or move between staging and production.
This perk helps you present and validate terms, but it does not replace policy management. If your organization updates legal text often, you still need a workflow for versioning the policy and deciding whether old entries need to be tied to a specific revision.
Also, do not assume “terms accepted” equals “legally bulletproof”. If you need stronger evidence, you may want to store additional context such as timestamps, IP address, or the specific URL of the terms page at time of submission, depending on your policies and jurisdiction.
It records the acceptance as part of the form submission, like other field data. If you need more detailed auditing, plan what additional metadata you want to capture alongside the entry.
Yes, and that is often the cleaner approach when legal maintains a dedicated page. After setup, test that the link opens in the expected way on mobile so users do not lose their place in the form.
Generally yes, but you should test back/forward navigation and any save-and-continue flow you use. Most “it broke” reports I have seen were really navigation state issues, not installation problems.
This usually comes from conditional logic or required validation not matching the display logic. Review whether the agreement should be required for that conditional branch, and test each path as a separate user journey.
It is safe when you follow a normal release process. We install on staging first, test submissions, then deploy to production. The biggest risks are not the plugin itself. They are caching, script optimization, and form logic assumptions that were never tested end-to-end.
Geotoko is a trusted GPL website for WordPress themes, plugins, Shopify templates, and free giveaways. Download original, secure GPL files with lifetime updates.
All products on Geotoko are fully licensed under the GNU General Public License (GPL) and are independently reviewed for safety and quality.
