Privacy Policy

1. Controller and scope

This policy describes how Pagatu, or Pagatu Pro, as the operator of the service, processes personal data on its official domains pagatu.io and app.pagatu.io, covering the web application, the public booking and payment pages, quotes, scheduling, manually recorded payments, receipts and operational communications.

Main country of operation: Peru. Privacy and support contact: hola@pagatu.io.

2. Data we process

Depending on the features you use, Pagatu may process account data such as name, email, phone number, profile picture where authentication provides one, preferences and business details. It may also store information you enter about clients, quotes, appointments, payment methods, manually recorded payments, receipts, logos, signatures and whatever is needed to set up your brand kit.

We also process technical data needed to run the service: session identifiers, essential authentication cookies, IP addresses, browser, device, security logs and the events needed to prevent abuse, debug errors and keep the service available.

Pagatu uses this data to provide the service, authenticate users, manage quotes, organize appointments, sync authorized events, send operational communications, record payments, prevent fraud or abuse, provide support and meet applicable obligations.

3. Google and Google Calendar data

Connecting Google Calendar is optional. The connection starts from Scheduling > Integrations and requires you to accept the permissions on Google’s consent screen.

The current implementation requests the email address of the connected Google account and the Google Calendar permission needed to create, update and cancel events tied to appointments managed inside Pagatu. Pagatu uses the connected account’s main calendar, identified as primary.

Once the integration is authorized, Pagatu may store the connected Google email address, the identifier of the calendar in use, encrypted access and refresh tokens, the token expiry date, the permissions granted, the status of the integration, the identifiers of events created in Google Calendar, event links and Google Meet links where they are generated for an appointment.

Google tokens are stored encrypted using AES-GCM authenticated encryption with a server key configured as CALENDAR_TOKEN_ENCRYPTION_KEY. No client secrets or tokens are stored in the browser.

Pagatu does not download your full calendar for advertising purposes, does not sell Google Calendar data, does not use it to build advertising profiles and does not share that data with third parties for advertising. Google information is retained while the integration is active or while it remains necessary to keep operational records of appointments managed in Pagatu.

4. Limited use of Google information

Pagatu’s use and transfer of information received from Google APIs is limited to providing or improving features that are visible to the user, and will comply with the Google API Services User Data Policy, including the Limited Use requirements.

Pagatu does not sell Google data, does not transfer it to advertising networks, does not use it for personalized advertising and does not use it to determine creditworthiness. Human access to Google data is limited to justified cases: an explicit support request, a security investigation, legal compliance, or authorized internal operations necessary to provide the service.

5. Security and retention

Pagatu uses HTTPS, authentication through Clerk, per-user access control, Convex as its database, Cloudflare Workers to run the application, secrets kept out of client-side code and encryption of Google tokens at rest. Convex functions filter information by authenticated identity so that one user cannot reach another user’s data.

Data is retained while the account or integration is active, while it remains necessary to provide the service, or for the reasonable period required for security, support, auditing or applicable obligations. When you disconnect Google Calendar, Pagatu attempts to revoke the token with Google and deletes or invalidates the stored tokens.

6. Service providers and transfers

Pagatu uses technical service providers to run the service: Clerk for authentication, Convex for the database and backend functions, Cloudflare for infrastructure, R2, Workers and the website metrics described below, Google for the optional Calendar integration, and the transactional email services configured in the project.

These providers may process information outside the user’s country of residence. Pagatu applies the contractual and technical controls available for each provider and each purpose of processing.

7. Website metrics

Pagatu’s public website (pagatu.io) uses Cloudflare Web Analytics to understand how people navigate it and how the pages perform. It collects, in aggregate, the page visited, the page it was reached from, the approximate country, the device and browser type, and load times.

This measurement does not use cookies and stores nothing in the browser. It does not build profiles, does not identify individual people, does not follow browsing across other sites and is not used for advertising. The data is not combined with the account of anyone who has one with Pagatu.

Inside the application (app.pagatu.io) there are cookies necessary to keep you signed in, managed by the authentication provider, and a language preference stored in the browser. Neither is used for advertising or for cross-site tracking.

8. Rights, revocation and deletion

You can request access, correction, deletion, objection, portability where applicable, and revocation of consent by writing to hola@pagatu.io. Pagatu will assess the request and respond through the same channel.

You can disconnect Google Calendar from Scheduling > Integrations. You can also revoke access from your Google Account, in the connected applications section. Full self-service account deletion still has to be confirmed by the owner; in the meantime, requests must be sent by email to the contact above.

Pagatu is not directed at minors. If we find an account being used by someone who does not meet the applicable minimum age, we may restrict or remove access as the case requires.

If we update this policy because of relevant changes to the service or to the use of Google data, we will publish the new version on this page and, where appropriate, notify you inside the application or by email.