PageSignal

Privacy Policy

Effective date: November 18, 2026. This notice describes the PageSignal-hosted workspace and the current Community software. A self-hosted operator controls their own deployment and must provide their own applicable notice.

Documents and AI processing

Original uploads, local OCR, edits, and conversations are held in your browser tab in the current workspace. PageSignal does not provide a durable document library. Export your results before closing or refreshing the tab. If you enable AI, rendered page images and extracted text pass through the server to OpenAI. Document questions send numbered page text and relevant conversation context. These requests use store: false; provider processing, logs, and retention are subject to the provider's policies and settings.

Accounts and usage

If account sign-in is enabled, PostgreSQL stores your account ID, name, email address and verification state, provider identifiers, encrypted provider credentials where returned, sessions, IP address/user-agent metadata, verification records, and usage counters. GitHub and LinkedIn receive sign-in requests. Email magic links are delivered through Resend, which receives your email address and the sign-in message. Sign-in does not grant PageSignal access to your repositories or LinkedIn posts.

Optional community registration

If you submit the Who’s using PageSignal? form, we store your organization (if supplied), use case, integration selection, sharing consent timestamp, and optional permission to contact you, linked to your sign-in account. This registration is private to the maintainer, not a public showcase. It is not required to install or use the npm packages. You can update or withdraw it on the Community page; withdrawal removes the registration but not your sign-in account or existing hosted usage records. Contact permission is optional and does not subscribe you to a newsletter.

An allowlisted maintainer can view account names, verified account emails, registration dates, optional registrations, and hosted AI request counts to understand service adoption and usage. These counts include attempts, not documents or unique npm downloads. No package installation telemetry is added; self-hosted and anonymous npm installations are not tracked.

Cookies and technical services

Essential cookies maintain sign-in sessions and OAuth state. The hosted website loads Google Tag Manager (container GTM-MKHN9RHR), which manages the tags configured and published by the PageSignal operator. Google Analytics, if enabled in that container, can measure visits, approximate location, devices, and referral sources and may use analytics cookies. This integration does not explicitly send uploaded documents, extracted field values, filenames, chat contents, or account emails to the data layer. Tags and automatic collection settings are controlled separately in Tag Manager; the operator should disable form interaction and user-provided data collection on the workspace, community, and admin pages. npm package installations are not tracked by this website integration. Vercel and other infrastructure providers may retain operational logs. OCR/PDF dependencies and fonts are loaded from third-party CDNs; those providers may receive connection metadata such as IP addresses.

How information is used

Account data is used to authenticate you, deliver sign-in messages, enforce access and usage limits, operate the service, and troubleshoot faults. AI content is sent to the configured provider to perform the extraction or answer you request. PageSignal does not include a feature to sell your document contents or use them for advertising.

Retention and choices

You control whether to send documents to AI. Closing the tab clears the workspace's in-memory state; downloaded JSON files remain wherever you save them. Account, session, verification, and quota records persist in the database according to the operator's retention process. Automated account deletion and retention scheduling are not currently included. Signing out invalidates your application session; it does not delete your account or revoke permissions at the identity provider.

Requests and sensitive information

For account access or deletion requests, contact the deployment operator through the support channel to arrange private handling. Do not attach documents, identifiers, credentials, or private account information to a public GitHub issue. Before uploading information about other people, ensure you have the authority to process it and use a deployment suitable for your needs.

Third-party information: OpenAI privacy, Vercel privacy, Resend privacy.