Pirl Privacy Policy
Last updated: October 7, 2026 (revision 1)
Scope and responsibility
This policy describes Pirl, not just Hypherdyne's marketing website. Pirl acts as controller for dashboard identity, billing, security, and support data and as processor for customer data controlled by workspace/account operators. Maicon Lourenco de Souza, doing business as Hypherdyne, CNPJ 40.157.494/0001-37, is the controller and contracting party for Pirl. For privacy inquiries and LGPD data subject requests, contact privacidade@pirl.com.br.
Data and purposes
Billing profiles include name, email, CPF/CNPJ, Brazilian phone and billing address. Profiles are encrypted and the required fields are sent to Asaas for customer creation, payment processing and fiscal invoices. Card details are entered on Asaas-hosted pages, not received or stored by Pirl.
Pirl processes account identity, profile and preferences, memberships, invitations, sessions, access requests, billing records, and security/audit information. Customer processing includes identities, conversations, messages, media, archives, AI inputs/outputs, assistant conversations and attachments, and message-search embeddings. Pirl does not receive payment-card details from Asaas. Credentials are encrypted or hashed as appropriate and are not exposed in ordinary responses, events, or logs.
Dashboard identity/session processing supports the contract and security legitimate interests. Customer processing follows the controller-configured legal basis. Enabled AI requires a declared workspace basis. Optional advertising relies on your separate, withdrawable marketing choice; terms acceptance is not advertising consent.
Authentication and security
Google sign-in receives your verified email, Google identifier, name and available profile image. An optional, separately authorized Google People API import receives professional information for your review before saving it. Google processes the authentication and authorized API requests under its applicable terms.
Optional passkeys store only public credential material and metadata. Private keys and biometric data remain with your authenticator and never reach Pirl; account erasure removes the stored credentials.
Session records retain IP address, user agent, browser, and device for security and the user's session list. Verification, reset, and new-browser emails include the request time, browser/device, approximate connection location, and IP address; that location is not stored with the account. Necessary cookies keep sessions, protect commands from CSRF, bind signup verification, maintain short-lived OAuth state, and recognize previously used browsers. For security issues and vulnerabilities, contact seguranca@pirl.com.br.
Email communications
Marketing and research emails require separate, revocable consent and default to disabled for dashboard users. Essential security and transactional messages do not depend on this optional choice. Public email subscriptions are independent from user accounts and require email confirmation; unconfirmed subscriptions are deleted after seven days. Consent evidence records the choice, policy version and time. You can unsubscribe through email links or profile preferences. Public subscriber privacy requests use privacidade@pirl.com.br; account erasure does not automatically remove an independent public subscription.
Optional advertising
Only after permission, Pirl's separate Meta Pixel measures clean public login, registration, access-request, and terms-acceptance pages, plus completion of a new self-service registration after verification and terms acceptance. Meta receives browser/network information, public page URLs, Meta cookie identifiers where available, and static product/event labels. No dashboard pageviews, tenant/user identifiers, email addresses, credentials, invitation/verification tokens, or form values are intentionally sent. Automatic event collection, metadata configuration, and matching are disabled. Advertising scripts are absent from the authenticated dashboard document.
Your browser choice is separate from the marketing website, expires after one year, and is invalidated when its policy version changes. Anonymous consent evidence records a random browser identifier, decision, policy version, language, time, and expiry; expired evidence is purged. Closing preferences grants no permission. You can reject or withdraw in Cookie settings; refusing never blocks the service. Failed or blocked advertising delivery does not affect registration.
Providers and transfers
Azure PostgreSQL and its configured recovery storage are in Brazil South. Cloudflare Workers, R2, KV, queues, Durable Objects, Images, Email, Turnstile, Workers AI, and Vectorize support infrastructure and message search. Meta supports messaging and separately optional advertising. Google supports sign-in and optional professional-profile import. Asaas supports payments, billing and fiscal invoices. Configured AI providers receive inputs for enabled tasks. These providers may process information in other regions; database residency does not mean all Pirl data stays in Brazil.
Retention and rights
Retention follows the configured session, invitation, customer, conversation, archive, AI, notification, audit, and storage-cleanup settings. Unverified inactive signups are purged after seven days. Private retention backups are off by default, bounded independently, and not created for user-initiated deletion. Exception telemetry does not yet have an automatic purge. Legal acceptance evidence records policy versions and time and is erased with its subject under the current rights workflow.
Authenticated users can request access, correction, portability, or erasure; authorized operators handle verified customer requests. Requests have a 15-day target. Exports contain metadata manifests with authorized expiring media downloads. Erasure removes or anonymizes account data, revokes sessions/grants, and queues private media cleanup; shared-workspace ownership may need transfer. User security and data-rights actions remain available before terms acceptance. Incidents follow documented containment, investigation, and notification duties.
Cloudflare Turnstile
Pirl uses Cloudflare Turnstile to protect public forms against bots and abuse, including verification that may run invisibly. Cloudflare may process browser, device, and network signals for this security verification. See Cloudflare's Turnstile Privacy Addendum for details.