Privacy policy

This policy explains what data pageo ("pageo", "we", "us") collects at pageo.me, why, who we share it with, and the choices you have. It covers three groups of people: owners who make a pageo page, visitors who view a page, and submitters who fill in a form or subscribe to an owner's updates.

1. Who is responsible

pageo is the controller for owners' account data and for the analytics we collect about how pageo is used.

When a submitter sends a form or subscribes to an owner's updates, the owner decides what that data is for, and pageo processes it for the owner. Questions about how an owner uses your message or email address go to that owner. You can always ask us to delete it too.

2. Data we collect

From owners

• Account: name, email address, password (stored only as a hash), and the profile image from Google when you sign in with Google.
• Your page: username, bio, links, images, layout, theme, forms, pageo pass settings, and anything else you add in the editor or in a pageo.json file on GitHub.
• Connected services: when you connect Instagram, YouTube, Dribbble, or GitHub, we store an access token and the public profile and media data needed to show your grid or graph (see section 4).
• Billing: your plan, its status, renewal dates, and Dodo Payments' customer and subscription ids. Dodo Payments holds your card details. We never see or store them.
• Messages to us: feedback, support emails, and waitlist sign-ups.
• Search performance: how often Google shows your page and which searches lead to it, from Google Search Console, so we can show it in your analytics. Searches that look like an email address or a phone number are never stored.

From visitors

• Analytics events: page views, link clicks, form views and sends, the referring site, an approximate country, browser and device type. Owners see these as totals in their analytics.
• Technical data: IP address and user agent, used for security, rate limits, and the approximate country.
• Players: an owner's page can show players from Spotify, YouTube, Calendly, and other services. Each player loads from its service, and that service's privacy policy applies. Video players load only after you tap play.
• Reports: when you report a page, we store the reason, any details you write, and a keyed hash of your IP address, so one visitor counts once. We never store the address itself with a report.

From submitters

• The fields of the form you send (usually a name, an email address, and a message), the time, and the form it came from.
• For audience subscriptions: your email address, the confirmation code we email you, and the owner you subscribed to.

3. How we use data

• To run pageo: show public pages, save your edits, send form messages to owners, and send the emails you ask for.
• To keep pageo secure: stop spam and abuse, rate limit requests, and investigate problems.
• To bill pageo Pro and to send receipts and plan emails.
• To improve pageo, using analytics about how features are used.
• To write a draft update email when an owner asks for one. The list of page changes is sent to Google Gemini to write the draft. No subscriber data is sent.
• To run the free link checker and link preview checker. They fetch the links a visitor enters and keep no copy.

We do not sell personal data, and we do not use it for advertising.

4. Instagram, YouTube, Dribbble, and GitHub

These connections are optional, and only start when an owner connects them from the editor.

• Instagram (Meta): we request instagram_business_basic and instagram_business_manage_insights. We receive the account id, username, profile picture, follower count, and recent media with captions, timestamps, and engagement counts. We use this only to show the owner's grid. Meta's use of data follows the Meta Privacy Policy.
• YouTube (Google): we request read-only access (youtube.readonly) to show the owner's channel and videos. pageo uses YouTube API Services, so the Google Privacy Policy applies. Owners can also remove pageo's access at Google security settings.
• Dribbble: we receive the owner's public shots to show their grid.
• GitHub: we read the owner's public pageo.json file and contribution graph, and receive a push webhook when the file changes.

When an owner disconnects a service, we stop fetching new data and delete the stored token. Cached media expires on its own schedule.

5. Who we share data with

We use these service providers to run pageo. Each only gets the data it needs for its job.

When an owner on pageo Pro connects Kit, Mailchimp, or beehiiv, we send each new subscriber's email address and first name to the tool and list the owner chose, using the API key the owner gave us, which we store encrypted. That tool processes the data for the owner under its own terms.

When an owner on pageo Pro adds a webhook, we send each new subscriber and form message to the address the owner chose. That address belongs to the owner or a service the owner picked, and the owner is responsible for it. We keep only the delivery status for 7 days, not the data we sent.

We also share data when the law requires it, to protect people from harm, or as part of a merger or sale of pageo, under this same policy.

Some providers process data outside your country, including in the United States. Where the law requires it, these transfers use standard contractual clauses or a similar safeguard.

6. Cookies and similar technologies

• Required: a session cookie that keeps owners signed in, and stored preferences such as your cookie choice and unsaved editor drafts. pageo does not work without them.
• Analytics: until you choose, PostHog runs without a cookie and keeps its id in memory for one page view. If you accept analytics cookies on pageo's site, PostHog keeps an id in a cookie and local storage so it can count return visits and record sessions to fix bugs. If you decline, PostHog stops capturing.
• Owner analytics: an owner on pageo Pro can add Google Analytics, Google Tag Manager, or a Meta Pixel to their page. The owner chooses whether the page asks visitors for consent before Google Analytics and the Meta Pixel load. Google Tag Manager loads without a pageo banner, and the owner sets up consent inside it. These tools send data to Google or Meta for the owner, under the owner's responsibility.

We do not use advertising cookies.

7. How long we keep data

• Account and page data: while the account exists. When you ask us to delete your account (Settings, then Your data), we delete it within 30 days, except for backups, which expire within 30 more days.
• Search performance: 16 months, the same window Google keeps.
• Reports: while the reported account exists.
• Form messages and subscribers: until the owner deletes them or the account.
• Billing records: as long as tax law requires, usually up to 8 years.
• Rate limit counters: one day. Server logs: a few days, as our hosting provider keeps them.

8. Your rights

Depending on where you live, you can ask to access, correct, export, or delete your data, or to object to or limit how we use it. Owners can change most data in the editor, and owners on pageo Pro can download their subscribers and form messages as CSV. For anything else, including a full export or deleting your account, use Settings, then Your data, or email sanyam@pageo.me from the address on your account. We reply within 30 days. You can also complain to the data protection authority where you live.

9. Security

Passwords are hashed, connections use HTTPS, access tokens for connected services are stored server-side and never sent to the browser, and production data access is limited. No system is perfectly secure. If a breach affects your data, we will tell you as the law requires.

10. Children

pageo is not for children under 13, and we do not knowingly collect their data. If you think a child has given us data, email us and we will delete it.

11. Changes

When we change this policy, we update the date at the top. If a change is material, we email owners or show a notice in pageo before it applies.

12. Contact

Questions or requests about privacy: sanyam@pageo.me.