1. Responsibility and scope
FanPay.pe (“FanPay”) is operationally responsible for the processing described in this policy. It covers fanpay.pe, its fn.pe alias, the user panel, public pages, short links, QR codes, designs and professional scheduling tools.
For questions or to exercise data rights, contact privacidad@fanpay.pe.
2. Data we process
Sign-in and accounts
- Google handles sign-in and supplies authorized basic claims under the
openid,emailandprofilepermissions. FanPay keeps Google’s stable identifier, authorized name and email when verified by Google. We do not receive your Google password or retain sign-in access, refresh or ID tokens. Optional Calendar access uses separate consent, described below. - We store information you add: username, display name, biography, links, destinations, pages, campaigns, QR codes, designs and revisions. We also store your chosen interface language.
- We store session hashes and creation and expiry dates to protect access. Temporary OAuth uses state, nonce and PKCE against impersonation.
Visits and statistics
We count views and clicks, not identified people. We may store date and time, referring host, UTM parameters or campaign code, device family, operating system, browser, language, country and region. IP addresses may be processed briefly to derive approximate location, but are not stored in statistics tables or used to create an identifier that follows someone between visits.
Account access and usage
At sign-in, we record time, access method, an IP reported by a trusted proxy, approximate country and region, and device, browser and operating-system families. If infrastructure cannot verify the address, it is shown as unavailable; we do not accept browser-declared addresses. VPNs can change approximate location.
While you use your account, we record FanPay screens opened and confirmed actions, such as creating links, generating QR codes or setting up appointments. We store predefined categories and dates, not form content, URL parameters, passwords, tokens, external browsing destinations or client data. No tracking cookie is added. Authorized staff may view activity for support, security and product improvement; full IP access requires moderation or administration permissions.
Hosting and network providers may process IP addresses, headers and technical logs to deliver the site, prevent abuse and diagnose incidents.
Profile photos and public contact information
When Google supplies a photo during verified sign-in, we retain its address and, when the editor opens, save a normalized copy in FanPay as the default photo. We do not send tokens to the image server, and visitors do not load that photo from Google. A custom photo takes priority; otherwise a generic avatar is used when no photo is available.
You may upload a JPG, PNG or WebP profile photo. We validate it, remove metadata and crop it square. It is saved in the draft and becomes public when the profile is published, including its shared view and design. Replacing or removing a draft photo does not change the public photo until publication. Removing a custom photo restores the Google photo if available, or a generic avatar.
A WhatsApp button makes the number and initial message you provide part of a public link. Opening it takes visitors to WhatsApp under its own policy. FanPay does not send the message automatically or access conversations.
Appointments and private receipts
Professionals may publish the payment holder’s name, Yape or Plin number, bank and account, payment link or payment QR image for external payments. These appear during booking confirmation and are retained with its conditions. We do not request payment passwords, bank keys or access to payment applications.
Account-free bookings process the client’s name, stated email, optional phone number, service, time, status, chosen language and change history. These details are shared with the professional. When email is enabled, the address is used for a verification link and pending approval or confirmed booking notices in the booking’s language. We record verification time and delivery attempts to manage the booking and retries. Verification checks access to the email, not identity or phone ownership.
If requested, clients may attach a JPG or PNG receipt. We validate the format and remove metadata. Receipts are private and are not used to verify payment. Only the owning professional can view them. Do not submit diagnoses, medical histories or other health data: scheduling is an administrative function.
Professionals must have a legitimate basis and necessary permissions for manually entered appointment data and its use outside FanPay.
Professional setup and payment QR images
We save setup progress, including incomplete contact fields, so it can be resumed. A setup draft does not replace the published profile until confirmed. Payment QR images are normalized as PNG without metadata or cropping. Clients can see them when the payment method is active or part of an accessible booking. They are kept separate from private receipts. Payment details and QR images associated with a booking are retained even if the payment method changes later. Unreferenced images are removed after 24 hours through maintenance.
Optional Google Calendar
Calendar is connected only when you request it and authorize availability and application-created calendar permissions. We retain the connected account identifier and verified email, with encrypted access and refresh tokens. Only busy intervals from the primary calendar are read, not event names or descriptions. Intervals are processed temporarily to calculate and revalidate available times; we do not retain a copy of external events.
A separate calendar named “FanPay” receives confirmed appointment dates, times and generic titles. Client names, emails, phone numbers, sensitive services and receipts are not shared. Disconnecting removes active connection tokens and stops synchronization. We attempt to revoke permission; if that fails, we ask you to remove it from your Google account. Exported events are not automatically deleted and can be removed in Google.
Google Maps reviews
If you choose a business listing, we store only its Place ID. When displayed, we request listing details and up to five relevant reviews from Google Places, without permanently storing reviews, authors or ratings. Original attribution and links are included. Author photos load from Google servers, which may receive the visitor’s IP and technical data. We do not write, edit or manually select reviews. You can remove the listing and publish the change or omit the feature.
Support, security and administration
When you contact us, we process the information in your message. Limited records of administration, moderation, account status and requests help protect the service and investigate incidents.
3. How we use data
- Authenticate you and maintain a secure session.
- Manage availability, holds, bookings, receipts and appointment changes requested by clients or professionals.
- Create, edit, publish and deliver the requested tools.
- Display aggregate page, campaign and link statistics.
- Analyze account tool usage to prioritize improvements, without profiling anonymous visitors or advertising.
- Prevent fraud, spam, phishing, malware and prohibited uses.
- Handle requests, enforce terms and comply with legal obligations.
- Maintain, diagnose and improve FanPay’s security and reliability.
Processing supports the service you request, consent where appropriate, legitimate security needs and applicable obligations.
5. Providers and transfers
We use Google for identity and providers of hosting, databases, security and connectivity to operate FanPay. They process data under their own terms and applicable service instructions. Some may operate outside Peru.
Information received from Google is limited to sign-in, the default photo and requested optional Calendar and review integrations, subject to the Google API Services User Data Policy, including its Limited Use requirements. We do not sell personal data or share it with advertisers.
We may disclose information to a competent authority when a valid legal obligation requires it or when necessary to protect rights and safety.
6. Public content and external services
When you publish a page, short link, QR code or design, information marked public may be viewed and shared by anyone. Links may lead to third-party sites governed by their own policies. FanPay does not control processing outside our domains.
7. Retention and deletion
Account data and content are retained while the account is active or needed for the service. Security, moderation and audit records may be retained for a reasonable additional period to investigate incidents, resolve disputes or meet obligations.
Sign-in IP records and account usage history are retained for 30 days. After that, they disappear from reports and are deleted by periodic maintenance. Protected backups are replaced on their operational schedule and may retain earlier versions until then.
Appointments and administrative history are kept as needed to manage scheduling and handle requests. Disabling appointments or changing profile type does not delete them. Attachments become inaccessible at the retention deadline configured at booking: by default 30 days after the appointment, configurable from 1 to 365 days. Physical deletion occurs during maintenance. Explicit rescheduling updates retention while the attachment is still valid; expired files are not recovered.
Draft, published and default Google photos are kept when they differ. Replaced photos unused by any version are removed from the application. Unpublishing prevents public photo access while retaining the draft.
OAuth flows expire after 10 minutes and user sessions after 7 days. Expired records are removed by maintenance, and backups are replaced on the provider’s operational schedule.
8. Your rights
You may request information, access, updates, correction, cancellation or erasure, objection and, where applicable, portability or removal from search indexes. Consent may also be withdrawn without affecting earlier processing.
Send requests to privacidad@fanpay.pe. We may request reasonable identity verification to protect your account. If you believe a request was not addressed, you may contact Peru’s National Authority for Personal Data Protection.
9. Security
We use separate access controls, encrypted connections, credentials outside the public root, random tokens stored as hashes and minimal database permissions. No system is infallible. Report suspected incidents to privacidad@fanpay.pe.
10. Changes to this policy
We may update this policy to reflect changes in FanPay, providers or rules. The current version will be published at this URL with an updated effective date. Material changes will be communicated through reasonable means where appropriate.
Use of FanPay is also governed by the Terms of service.