This privacy policy explains what information is collected when you use the gAppointments website and plugin, how that information is used, and the choices you have about how it is handled.
Who we are
The gAppointments plugin is published by WpCrunch through the CodeCanyon marketplace. This site mirrors the product documentation and serves as the primary landing page for new customers.
Information we collect
We collect only the information needed to deliver the plugin and support it.
- Account and purchase details provided to CodeCanyon when you buy gAppointments, shared with us by Envato so we can deliver updates and support.
- Messages you send through the CodeCanyon item comment thread or through the author contact form.
- Basic server logs recorded by the host, including the requesting IP, date and time, and the page requested. These logs are kept only as long as needed for troubleshooting.
The gAppointments plugin itself stores appointment records on your own WordPress database. Those records never leave your site unless you connect an optional third party service such as Twilio for SMS or Google Calendar for calendar sync.
How we use information
- Deliver plugin updates and respond to support requests.
- Improve the plugin based on the issues customers report.
- Meet the record keeping requirements that Envato places on authors.
Third parties
Purchases are processed by Envato (CodeCanyon) and payment is handled by the gateway the buyer selects at checkout (PayPal, Stripe, Skrill, credit or debit card). We do not see card details. If you enable SMS notifications on your site, appointment phone numbers are forwarded to Twilio. If you enable Google Calendar sync, event details are forwarded to Google.
Your rights
You can request a copy of the information we hold about you, correct inaccuracies, or ask for your data to be deleted. Contact us through the CodeCanyon author profile with the email address used for your purchase.
Updates to this policy
If the policy changes we update this page and adjust the effective date below. Continued use of the plugin after changes means you accept the revised policy.
Effective date: 20 April 2026.