Privacy Policy

Who we are

Pointerly is operated by SEAN LUIS GUADA RODRIGUEZ CONSULTORIA EM TECNOLOGIA DA INFORMACAO LTDA, CNPJ 47.348.090/0001-70, a company incorporated in Brazil with its registered office at Avenida Prefeito Osmar Cunha, 416, Centro, Florianópolis – SC, CEP 88015-100, Brazil ("Pointerly", "we", "us"). This policy explains how we handle personal data when you use our websites, web app, iOS app, browser extension, API, and related services, and when you interact with links, pages, or messages that our customers create with Pointerly.

We are the controller for the processing described as ours below. Our data protection officer (encarregado under Brazil's LGPD) is Sean Luis Guada Rodriguez, who can be reached at privacy@pointerly.io. Use this address for any privacy question or request, including from outside Brazil.

Controller and processor roles

Pointerly as controller. We decide how and why personal data is used for our own purposes: running accounts and billing, our website and marketing, security and abuse prevention, usage metering, support, legal compliance, and the internal brand directory.

Pointerly as processor. Our customers (creators, brands, and businesses with a Pointerly workspace) decide what Pointerly does with their Customer Content. That includes data about their own audience: people who click their links or visit their pages, people who comment on their posts or message their Instagram, Facebook, WhatsApp, or Telegram accounts, broadcast subscribers, and contacts they import. For that data the customer is the controller (under LGPD, the "controlador") and Pointerly is its processor ("operador"), acting on the customer's instructions under our Terms and any data processing agreement.

If you are a visitor, subscriber, or other end user of a Pointerly customer and want to exercise your rights over that data, contact the customer directly. If you contact us, we will pass your request to the customer where we can identify them, and we will help them respond. We may still act as a controller for limited purposes on end-user data, such as security, abuse prevention, and metering, as described below.

Data we collect

Voice dictation in the web app uses your browser's built-in speech recognition. Pointerly receives only the resulting text. Your browser vendor (for example Google for Chrome or Apple for Safari) may process the audio under its own terms.

Visitors, subscribers, and other end users

When someone interacts with a Pointerly customer's link, page, or messaging account, we process the following on the customer's behalf:

• Link clicks and page views: IP address, user agent, device type, browser, operating system and its major version, approximate location (country, region, city) that our hosting provider derives from the IP address, referring page, campaign (UTM) parameters, the link and variant served, a visitor identifier, and whether the visit looks automated. We use this to route the visitor, report analytics to the customer, count usage, and detect abuse. The full IP address is used only while the request is handled: we store it shortened (IPv4 to its first three parts, IPv6 to its first 48 bits). The visitor identifier is a one-way hash of the IP address and user agent combined with a secret that changes every calendar month and is then destroyed, so it lets us count unique visitors within a month but cannot be linked back to an IP address afterwards. Visits flagged as automated are kept in analytics but are not billed as usage. Raw request details are deleted after 90 days, as described under "Retention".
• Comments and direct messages: the sender's platform user ID, username or name, profile photo where provided, message or comment text, and timestamps, so the customer's automations can reply.
• WhatsApp and Telegram subscribers: phone number or chat ID, name, messages exchanged, opt-in and opt-out status, delivery and read status, and which broadcast links they clicked.
• Abuse reports: the reported address, category, details, an optional email address, and a salted hash of the reporter's IP address and browser that changes daily, used only to limit repeat reports.
• Shop assistants: the shopper's messages and the products suggested. Shopper messages may be processed by OpenAI to understand the request, under the sensitive-data handling described in "AI processing": never by DeepSeek and never under a data-sharing program.

Public bio pages and links do not show a cookie banner and do not load our website analytics tools. The routing data above is processed server-side when the link is used.

Sources of data

We collect data from you; from members of your workspace; from platforms and tools you connect; from imports you run; from your use of the service; from end users who interact with our customers' links, pages, and messaging accounts; from payment, authentication, and infrastructure providers; and from public pages, such as retailer product pages, where relevant to a feature you use.

Purposes and legal bases

We use personal data for the purposes below. Where GDPR, UK GDPR, or LGPD apply, we rely on the legal bases shown.

Where we rely on legitimate interests, we have weighed them against your rights. You can ask us for details and you can object, as described under "Your rights". We do not sell personal data and do not use Customer Content to build advertising profiles.

AI processing

Pointerly's AI features run on third-party large language models. When you use Poppy, generate posts, captions, or scripts, receive message or keyword suggestions, run a shop assistant, when we classify a link destination for safety, or when a Delegated Workspace operator uses AI on your request, we send the relevant inputs to an AI provider. Inputs can include your prompt, the conversation so far, relevant workspace data (for example link, product, post, or analytics details), text from attachments, data from tools you connected when you ask Poppy to use them, and, for shop assistants, shopper messages.

We handle AI requests according to the kind of data they carry. Standard data is your own Pointerly content: your prompts and your links, products, posts, bio pages, and analytics. Sensitive data is data from accounts you connect and data about other people: Google user data (Gmail, Calendar, Drive, Sheets, Meet, and Analytics) and YouTube data, content from other workspaces and mailboxes you connect (such as Notion, Outlook, and IMAP mail), files attached to Delegated Workspace requests, and messages and comments from your audience (shop assistant chats, direct messages, and comments).

Pointerly's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Once a Poppy conversation, Delegated Workspace request, or automation step includes sensitive data, the rest of that work, including follow-up questions and file search, is handled the same way.

• We choose providers and fallback order based on cost and reliability, and we may change them. We will update this policy and our subprocessor list when we do.
• Pointerly does not train its own AI models on your content. AI output is stored in your workspace like other content.
• Do not submit sensitive personal data (such as health, financial account, or identity document data) to AI features unless it is necessary.
• The iOS app does not call AI providers directly. AI features in the app run on our servers in the same way as on the web.

Meta platform data

When you connect Instagram, Facebook, or WhatsApp, we access Meta platform data only through the permissions you approve and only to provide the features you use, such as replying to comments and messages, sending WhatsApp messages and broadcasts, publishing posts, and showing insights. We comply with the Meta Platform Terms and Developer Policies.

• We do not sell Meta platform data or use it for advertising profiles.
• We do not share it with third parties except our subprocessors, as needed to provide the features you use, or as the law requires.
• Disconnecting an account in Pointerly stops further access. You can also remove Pointerly from your Meta account settings.
• Meta sends us data deletion requests when a user removes our app. We process them and provide a confirmation code with a status page at /data-deletion-status. For how to request deletion yourself, see our data deletion instructions.

Google user data and YouTube

Connecting a Google or YouTube account to Pointerly is optional and always started by you. When you connect YouTube, Pointerly uses the YouTube API Services and Google OAuth. By connecting, you agree to the YouTube Terms of Service, and the Google Privacy Policy describes how Google handles your data.

We request the narrowest scopes that make the features work:

• Sign-in (openid, userinfo.email, userinfo.profile): your email, name, and profile picture, to create and identify your Pointerly account.
• Uploading (youtube.upload): uploads the video and thumbnail you composed in Pointerly to your own channel, only when you press publish.
• Reading your channel (youtube.readonly): confirms which channel is connected, tracks when YouTube finishes processing your upload, and shows view counts of your own videos.
• Channel metrics (yt-analytics.readonly): views, watch time, and subscriber counts, shown only to the workspace that owns the connection.
• Google Workspace tools (Drive, Sheets, Calendar, Gmail, Meet), where you connect them: the files, events, or messages a feature needs at your request. Some of these connections are brokered by our integration provider Composio.

Google user data. We handle information received from Google APIs in line with the Google API Services User Data Policy, as follows:

• We do not sell Google user data.
• We do not transfer Google user data to third parties except as necessary to provide or improve the features you requested, to comply with law, or as part of a merger or acquisition with notice to you.
• We do not use Google user data for advertising, ad targeting, or credit scoring.
• Google user data, including anything read from a connected Gmail mailbox, reaches the internal brand directory only if the workspace owner or an admin turns on "Contribute brands found in your email", and then only as a brand's business details (name, website, category, logo, social handles) and anonymized deal statistics. People's names, email addresses and message content from Gmail are never added, and staff never read Gmail messages for it.
• We do not allow humans to read Google user data unless you give explicit consent for specific data, it is necessary for security or to comply with law, or the data has been aggregated and anonymized.

Pointerly's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Google user data and AI. By default, Google user data is processed only by AI models that do not train on it: your workspace's own OpenAI key if you added one, or Pointerly's private no-training OpenAI project. It is never sent to DeepSeek. If a workspace admin turns on Allow AI on my Google data in Settings → AI, that data may be sent to OpenAI under a data-sharing program and may be used to improve OpenAI's models; it can be revoked at any time and applies from then on. The "Allow AI on connected data" opt-in does not cover Google data (see AI processing). This default follows the Google API Services User Data Policy, including Limited Use.

Storage and deletion. We store the OAuth tokens for the connection, encrypted, together with your channel identifier, public channel details, and the identifiers and metrics of videos published through Pointerly. You can disconnect at any time in Integrations, which deletes the stored tokens, and you can revoke access at myaccount.google.com/permissions. Deleting your workspace deletes the associated connection data.

Amazon and restricted partner data

Pointerly classifies Amazon Ads API and Creator Connections-derived data, such as campaign identifiers, advertising or affiliate metrics, eligibility and enrollment data, raw partner payloads, and credential references, as restricted partner data.

• We do not sell Amazon Ads, Amazon affiliate, or Creator Connections data.
• Automated third-party exports of restricted partner data are blocked by default.
• Exports that contain it must be started by the customer and sent only to the customer's own connected destination, and we keep audit records of them.
• Official Amazon Creator Connections API sync stays disabled unless Amazon approves the required app, scopes, and endpoints.

Brand directory

Customers who use Collaborations record the brands they work with, people at those brands, and their deals. Pointerly combines part of that business information, across customers, into an internal directory. For the directory Pointerly is the controller (not the customer's processor).

• What it holds: brand name, website domain, logo, category, niches, and social handles; the name, role, and business email address of people at brands, and whether the address works; and deal facts without the creator or workspace they came from: type of content, platform, amount and currency, month, how far the deal got, and the creator's content niche.
• Records found in email: brands, contacts and deals that Pointerly created or changed from a customer's connected mailbox (the inbox study, inbound proposals, Collaborations agents) are added only if the workspace owner or an admin turns on "Contribute brands found in your email" in Settings → Collaborations. We record who turned it on and when. From Outlook or another mailbox (IMAP), the brand, its business contacts and anonymized deal facts can be added. From Gmail (or when we cannot tell which mailbox it came from), only the brand's business details and anonymized deal statistics are added, never people's names or email addresses. Turning it off removes what came from email at the next update of the directory.
• What it never holds: the content of emails, anything from a connected mailbox without the opt-in above, contact details of people taken from Gmail, personal email addresses at free email providers used to identify a brand, or the customer's identity next to a deal.
• Why: to understand the brands and the market creators work in, improve matching between creators and brands, and improve Collaborations. For records the customer typed in, our legal basis is legitimate interests. We assessed them against the interests of the people listed: the data is business contact information people at brands already share for partnership work, it is used internally only, it is never sold or shown to other customers, and people can opt out at any time. For records found in email, the legal basis is the workspace's consent, which can be withdrawn at any time in the same setting; people listed keep the same right to opt out described below.
• Who sees it: a small number of authorized Pointerly staff, with multi-factor authentication and logged access. Statistics about a brand are shown to staff only when they combine deals from at least three different workspaces.
• If a brand contacts you through Pointerly staff: if we ever contact a person listed in the directory, our first message says where their details came from and how to opt out.
• Your choices: if you work at a brand and want to see, correct, or remove what the directory holds about you, email privacy@pointerly.io. When we remove you, we also block your address from being added again. This applies to the directory; a creator's own records in their workspace are theirs, and we will pass your request to them where we can identify them.

Delegated Workspace and staff access

If your workspace enables the Delegated Workspace add-on, Pointerly operators assigned to it can see and work with the workspace's data within the operator role to carry out your requests. Operators are Pointerly staff with an approved company email address, must use multi-factor authentication, cannot access billing, members, API keys, or the browser extension, and their access is logged. Access ends when the add-on ends.

Outside Delegated Workspace, a small number of authorized staff may access account data when needed to provide support you ask for, keep the service secure, investigate abuse or reports, or comply with law. Administrative access requires multi-factor authentication and is logged.

How we share data

• Subprocessors and service providers who host, store, process, or deliver data for us, listed on our Subprocessors page. That includes Cloudflare for DNS/CDN, Turnstile bot checks on public forms, and R2 storage of public link and automation images, and Supabase for the database and remaining file storage.
• Link safety services: destination addresses of links are checked against Google Web Risk and Cloudflare's DNS filtering resolvers (and abuse.ch URLhaus when enabled). The destination host and address and the page's public title, description, and site name may be classified by our AI providers (OpenAI, with DeepSeek as fallback). This is standard data: no visitor or account data is sent.
• Platforms and tools you connect, when you publish, send, export, or sync through them. They handle the data under their own terms.
• Members of your workspace, according to their roles, and Delegated Workspace operators where you enable it.
• The public, for content you choose to publish, such as bio pages, storefronts, creator and brand profiles, and posts.
• Authorities and others where the law requires it, to respond to valid legal process, to protect people from harm, to enforce our terms, or to report illegal content such as child sexual abuse material.
• A buyer or successor in a merger, acquisition, financing, or sale of assets, subject to this policy.

We do not sell personal data and do not share it for cross-context behavioural advertising.

International transfers

Pointerly is based in Brazil, and most of our providers process data in the United States. Some providers process data in other countries, including the People's Republic of China for our fallback AI provider (DeepSeek), which only receives standard AI requests and never the sensitive data described under "AI processing", and global edge locations for content delivery. These countries may not offer the same level of protection as your own.

Where GDPR, UK GDPR, or LGPD require a safeguard for these transfers, we rely on the contractual safeguards our providers offer, such as data processing agreements and standard contractual clauses, where they offer them, and on the other grounds the law allows, such as transfers necessary to perform our contract with you. You can ask us which safeguard applies to a given provider.

Retention

We keep personal data only as long as we need it for the purposes above. Typical periods:

Security

We protect data with encryption in transit, provider-managed encryption at rest, encrypted storage of connection tokens and AI provider keys, database-level workspace isolation, role-based permissions, multi-factor authentication for staff, and audit logs. No system is perfectly secure. See our Security page for details. If a personal data breach affects you, we will notify you and the authorities where the law requires.

Your rights

Depending on where you live, you may have the right to:

• confirm whether we process your data and get access to a copy of it;
• correct inaccurate or incomplete data;
• delete data, or have it anonymized or blocked where it is unnecessary or unlawful;
• receive your data in a portable format, or have it sent to another provider;
• restrict or object to processing, including processing based on legitimate interests and direct marketing;
• withdraw consent at any time, without affecting earlier processing;
• know which third parties we share data with, and the consequences of refusing consent;
• ask for review of decisions made solely by automated processing;
• complain to a data protection authority, such as your local EU supervisory authority, the UK Information Commissioner's Office, or Brazil's Autoridade Nacional de Proteção de Dados (ANPD).

You can access, export, and delete much of your data in the product, and delete your account in account settings. Otherwise, email privacy@pointerly.io. We will verify your identity and, for requests made on someone else's behalf, your authority. We respond within the time the law requires, for example one month under GDPR (extendable in some cases) and 15 days for a full response under LGPD. If we turn down a request, we will explain why and how to appeal.

If your data reached us through a Pointerly customer, such as a creator whose link you clicked or a business you messaged, see "Controller and processor roles" above.

California and other US states

This section applies to residents of California and other US states with comprehensive privacy laws. In the past 12 months we collected these categories of personal information: identifiers (name, email, IP address, account IDs); customer records and commercial information (billing and purchase history); internet and network activity (usage, clicks, logs); approximate geolocation; the content of communications you send us or through the service; and account login credentials, which are sensitive personal information. Sources, purposes, recipients, and retention are described above.

• We do not sell personal information or share it for cross-context behavioural advertising.
• We do not use sensitive personal information to infer characteristics about you.
• We do not knowingly sell or share the personal information of consumers under 16.

You may request to know, access, correct, or delete your personal information, and to appeal our decision, by emailing privacy@pointerly.io. You may use an authorized agent. We will not discriminate against you for exercising your rights. We do not sell or share personal information. We also honour a Global Privacy Control signal on our website as a refusal of analytics cookies, which otherwise stay off unless you accept them.

Children

Pointerly accounts are for adults aged 18 or older. Our services are not directed to children, and we do not knowingly collect personal data from children under 13 (or under 16 in the EU and UK, or the age set by local law). Our customers must not use Pointerly to target children with messages or restricted products. If you believe a child has given us personal data, contact privacy@pointerly.io and we will delete it.

Automated decisions

We use automated processing to route links, flag likely bot traffic, enforce usage limits, detect abuse, and power AI features. We do not make decisions based solely on automated processing that produce legal or similarly significant effects on you. Where an automated signal leads to an enforcement action on your account, you can ask for human review, as described in our Acceptable Use Policy.

Marketing communications

We send service messages, such as security, billing, and product notices, as part of providing the service. We send marketing email only where the law allows, and every marketing email has an unsubscribe link. Push notifications in the iOS app can be turned off in your device settings.

Changes to this policy

We may update this policy when our services, providers, or the law change. We will update the date above and, for material changes, notify you by email or in the product before they take effect.

Contact

Questions about this policy or our data practices: email privacy@pointerly.io or write to SEAN LUIS GUADA RODRIGUEZ CONSULTORIA EM TECNOLOGIA DA INFORMACAO LTDA, Avenida Prefeito Osmar Cunha, 416, Centro, Florianópolis – SC, CEP 88015-100, Brazil.

Version history

• October 10, 2026: Clarified that public link and automation images may be stored on Cloudflare R2 (media.pointerly.io) in addition to Supabase Storage for workspace uploads and legacy images; see Subprocessors for Cloudflare's expanded role (Turnstile, R2, DNS/CDN, Browser Rendering).
• October 8, 2026: Added the brand directory: what it holds (brand details, business contacts at brands, de-identified deal facts), what it never holds (email content, contact details of people from Gmail, the creator's identity next to a deal), records found in email only with the workspace owner's revocable opt-in (consent basis; Gmail limited to brand details and anonymized statistics), the legitimate-interests basis for records typed in, staff-only access with a three-workspace minimum for statistics, notice to people we contact, opt-out with a block on re-adding, and its retention.
• October 5, 2026: AI processing: by default Google user data and YouTube data run only on OpenAI under no-training terms (your own key or our project with data sharing off). A workspace admin may turn on "Allow AI on my Google data" in Settings → AI to send that data on OpenAI's shared program (may be used to improve models); it is recorded with who and when and can be revoked. Other connected data still needs "Allow AI on connected data". Limited Use remains the default, with the Google opt-in stated next to it. Standard data may run on OpenAI or DeepSeek depending on your Settings → AI choice.
• October 2, 2026: Added abuse reports and link safety checks. Filled in company details and data protection officer. AI: sensitive data (Google user data, mailboxes, attached files, audience messages) is processed only by OpenAI, never by DeepSeek or another fallback provider. Visitor data: IP addresses are stored shortened, raw request details are deleted after 90 days, the visitor identifier uses a monthly secret that is then destroyed, and bot clicks are not billed. Archived workspaces are deleted 12 months after archiving, with notice to former members. Backups: stated the actual 7-day backup retention. Global Privacy Control is honoured as a refusal of analytics cookies.
• October 1, 2026: Rewritten. Named our AI providers (OpenAI and DeepSeek) and the data each receives, added controller/processor roles, end-user data, Meta platform data, Delegated Workspace access, international transfers including China, a retention table, and rights under GDPR, UK GDPR, LGPD, and US state laws.
• September 4, 2026: Previous version.