Privacy choices
Appsail uses essential storage for sign-in, security, and theme preferences. With your permission, we also measure feed impressions, feed clicks, and referral attribution.
You can change these settings any time on the cookies page .
Privacy notice
Appsail is a builder-to-builder product testing platform. This notice covers the data we process to run the service, the optional analytics choices available to builders, and the providers that help us deliver the product.
Last updated: 3/18/2026
Appsail acts as the controller for the account, community, testing, and billing data needed to run Appsail.
Builders can already edit profile data, manage cookie choices, export their data, and delete their account from inside the product.
If you need help with a privacy request that is not self-service yet, start on the Help page .
Appsail processes account, project, testing, chat, notification, and credit data so builders can sign in, publish projects, receive feedback, communicate, and manage their account.
Session metadata, verification records, and rate-limit signals help protect accounts, reduce abuse, and keep the platform stable.
Appsail only measures feed impressions and feed clicks when analytics consent is enabled. These optional events help us understand how builders discover projects.
Appsail still stores testing, feedback, comment interaction, and credit records as part of the core product history needed to run projects, prevent abuse, and keep balances accurate.
Credit purchases, checkout sessions, payment confirmation, and transaction reconciliation.
Payment processing may involve transfers outside the EEA subject to Stripe contractual safeguards.
Data categories: account email, payment identifiers, purchase amounts, checkout metadata.
Optional OAuth sign-in and GitHub handle verification.
GitHub may process personal data outside the EEA when social login or handle verification is used.
Data categories: GitHub account identifier, public GitHub profile data, OAuth tokens.
Transactional authentication email delivery.
Email delivery may involve international transfers depending on the sending infrastructure in use.
Data categories: email address, verification and password reset email contents.
Project media, uploads, and other hosted file assets.
Storage location depends on the configured bucket provider and must be reviewed before EU launch.
Data categories: uploaded media, file metadata, storage object keys.
URL auto-fill and website content extraction for project submission.
Only invoked when a builder explicitly requests auto-fill during project creation or editing.
Data categories: submitted URL, public page content extracted from the submitted URL.
Optional location auto-detect in account settings.
Only invoked when a signed-in user chooses the auto-detect action.
Data categories: IP address, approximate location lookup response.
Font asset delivery for the public web UI.
Requests are made by the browser when the app loads shared font assets.
Data categories: IP address, user agent, font asset requests.
Expired sessions are deleted.
Expired verification rows are deleted.
Throttle records are deleted after the window and cooling-off period are no longer relevant.
Old notifications are deleted after the retention window.
Old analytics events are deleted or de-identified after the retention window.
Old chat content is deleted after the retention window unless a legal hold applies.
Deleted comment bodies are purged after a short recovery window.
Raw scraped page content is cleared from older projects.
Abandoned uploads are removed from object storage.
Pending or expired local payment records are deleted after the retention window.
Use Settings and the Cookies page to manage your data, choices, and account. If you need follow-up help, start on the Help page .
When a builder requests auto-fill during project creation or editing, Appsail sends the submitted URL to scraping infrastructure and may fetch the target website directly to extract public metadata, images, and page text.
The location auto-detect button in Settings makes a one-off request to ipapi.co using the current IP address. It is optional and only runs when selected by the user.