PULSO

Privacy policy

Updated November 1, 2026

Who provides Pulso

Pulso is provided by PDEVELOP LLC. Contact contact@pdevelop.net for questions about the service or your data.

Information we use

• Account: name, email address, account identifier, cryptographically protected password and hashed session tokens. These support sign-in, access control and account security.
• Campaigns: campaign name, content link, selected platform, goal, package, duration, target countries, audience notes, status history and reports. These let you prepare requests and let the team review and manage campaign work.
• Billing and purchases: billing name, tax identifier, address, country and email if supplied; store product and transaction identifiers, purchase status, amounts and refund records. These support purchase verification and billing records. Pulso does not receive full card details.
• Support: ticket subjects, messages, campaign references and account notifications, used to answer questions and document follow-up.
• Technical data: request and error information needed to operate and protect the service. Infrastructure receives request IP addresses; access controls use a cryptographically derived identifier for rate limiting.

Storage and providers

Account, campaign, billing, purchase and support records are stored using Cloudflare Workers and D1. The native app uses the device's secure storage for its session token. Team access is limited by account role.

Where native purchases are available, Apple or Google processes payment. RevenueCat receives the internal account identifier, transaction information and technical app/device information to verify purchases, restore account purchase history and synchronize refunds. Passwords, campaign briefs and billing forms are not sent to RevenueCat by the app.

When a campaign is accepted for fulfillment, the team may share the content link and relevant campaign brief with the advertising platform or service providers needed to deliver it. Availability depends on review and platform requirements. Creating a brief does not automatically start advertising.

Providers may process data in countries where they operate, subject to their terms and privacy policies.

Stripe campaign payments

When Stripe checkout is available, Stripe collects your payment details on its secure checkout page. Pulso sends internal account, campaign and payment references, the advertising budget, management amount and currency to create and reconcile the payment. We receive payment status, transaction references, amounts, processing fees, refunds and dispute information. Pulso does not receive your full card number or card security code. Stripe processes payment and technical information under its privacy policy. Previous store purchases continue to be reconciled through their original providers.

Advertising and tracking

Pulso lets you request advertising for your content. The current app does not embed third-party advertising SDKs or track your activity across other companies' apps and websites for personalized ads. Purchase data is used to administer purchases and related reporting.

Retention and your choices

We keep records while needed to provide the service, support active campaigns and reconcile purchases. You can edit your account password, eligible campaign briefs and billing details in the app. For access, correction or a copy of your data, email support from your account email address. We verify ownership before acting.

In app version 2.1.4 and later, open Account > Delete account and confirm with your current password. Accounts with no payment history are deleted immediately. Accounts with campaign payments receive a tracked deletion request, with reconciliation and completion within 30 days. No separate email is needed for an in-app request. Processor cleanup may take up to 30 days. See how to request deletion. Pending campaigns, purchases, refunds or recordkeeping obligations may require reconciliation or limited retention. Where information must be retained, support will explain what and why. Store providers maintain their own records under their policies. Never send passwords, card details or store credentials.

Changes

Updates will appear here with their date. Contact support if you need help understanding how your data is used.

AI app connectors

If you choose to connect your account to an AI app such as ChatGPT or Claude, the connector allows that app to request read-only access to your own campaign briefs, status history and recorded performance reports. It does not purchase services, change records, launch campaigns, or distribute music.

You approve the requesting client and its access scope on the connection page. Your password is sent securely to our existing account service to verify your sign-in; the connector does not store it or send it to the AI app. The connector stores an encrypted account session token and authorization records in Cloudflare KV. Access tokens last up to one hour and the connection expires after seven days unless you sign in again. The underlying account session expires after at most 30 days. Short-lived consent cookies protect the sign-in process and expire after ten minutes.

The AI app receives only the data returned by the tools you use. Its own privacy policy and your account settings govern how it handles that data. The connector excludes legal names, billing identities, purchase receipts, audio files and artwork files. It does not send your entire chat history to our account service.

You can disconnect through the AI app and contact our support to revoke a connection. Deleting your product account prevents the connector from reading its records immediately; expiring connector authorization records are removed automatically. Dynamic client registrations can remain for up to 90 days after their last renewal. Technical hosting logs are handled according to Cloudflare's policies.