Last updated: November 12, 2026
Presail ("we", "us") operates the Presail website, application, scanner, monitoring, site widget, testing links, prompt library and related services (the "Service"). We are the controller of the account, billing and usage data described in this policy. Where you use a testing round to collect feedback from people you invite, you are the controller of that feedback and we act as your processor — see Section 7 of our Terms.
Privacy contact: privacy@presailapp.com. This mailbox is monitored and reviewed on each business day. Postal address: available on request from the same address; if we appoint an EU or UK representative, its postal details are published in this section. Security reports go to security@presail.app, and abuse reports to abuse@presailapp.com.
How fast we answer: we acknowledge a data request within 10 business days and respond in full within 30 calendar days. Where the law we answer under allows longer (California allows 45 calendar days), we use that period and tell you if we need an extension and why.
This policy covers our website and application, the scanner, scheduled monitoring, the site widget, testing links, our prompt library and community features, and our MCP server. It does not cover the third-party sites and applications you scan, or third-party services you connect — those are governed by their own policies.
Every category we hold is listed below. If we add a new one, we add it here before we start collecting it.
| Category | What it includes | Where it comes from |
|---|---|---|
| Account details | Email address, name, hashed password (handled by our authentication provider), sign-in method, two-factor settings and remembered devices, phone number if you opt into SMS alerts, email preferences, onboarding answers, and account status. | You, when you register and use settings |
| Payment details | Your plan or one-time scan pack, the amount and currency charged, the Stripe checkout session and customer identifier, invoice and credit-balance records. We never receive or store your full card number — it goes directly to Stripe. | You, via Stripe |
| Device and usage data | Pages viewed, features used, errors, and approximate technical information such as browser type, device type, operating system, screen size and referring link, plus an approximate location derived from IP address. | Your browser, automatically |
| Cookies and similar technologies | The cookies and browser-storage keys listed by name, purpose and lifetime in our Cookie Policy. | Your browser, automatically |
| Apps and scan data | The URLs, names, types, descriptions and client labels of applications you connect; the findings, scores, check results, notes and annotations produced; scan history, trend data, monitoring state and alerts. | You, and our scanner |
| Connected-account data | If you connect a Google account (Workspace, Sheets or Gmail) or GitHub: what is needed to show and operate the connection, such as your email address or GitHub username, plus the OAuth tokens that let the feature act on your behalf. | Google or GitHub, only when you connect |
| Content you publish | Prompts and prompt packs you submit, your author profile (display name, bio, avatar), votes, saved items, follows, and reviews. | You |
| Testing-round feedback | Feedback submitted by people you invite: a category, a description of what they were doing, an optional rating, and optionally their name and email address. | People you invite |
| Support, contact and applications | Messages through our contact form, support requests and conversations, and — if you apply for a role — your name, contact details, portfolio link, interests, availability, experience and answers. | You |
| Security and audit logs | Events with your account ID, IP address and timestamp: scan requests and the authorisation you give, blocked scan attempts, failed sign-ins, plan and rate-limit events, administrative actions, subscription changes and account deletion. Written by our servers; not editable from the app. | Our servers, automatically |
| AI inputs and outputs | For AI-assisted features, the content sent to a model — fetched page markup, scan findings, prompt or profile text submitted for screening — and the result we return and store with the related record. | You, and the pages you ask us to analyse |
| Push notification data | A subscription record per device: the push endpoint, the encryption keys your browser generates, a short device label, whether the device is still active, and when a notification was last delivered. | Your browser, only if you enable notifications |
Each purpose below has a stated legal basis. Where we rely on consent you can withdraw it at any time without affecting the lawfulness of what we did before you withdrew, and withdrawing never costs you access to anything that does not depend on that consent.
| Purpose | Data used | Legal basis |
|---|---|---|
| Service delivery — scanning, reports, monitoring, alerts, widgets, testing rounds, exports and integrations | Account details, apps and scan data, connected-account data, AI inputs and outputs | Performance of a contract (Art. 6(1)(b) GDPR) |
| Payment and billing — charging, invoicing, credit balances, refunds, tax records | Payment details, account details | Performance of a contract; legal obligation for tax and accounting records |
| Fraud prevention and abuse prevention — detecting unauthorised scanning, rate-limit abuse, payment fraud and attacks | Security and audit logs, device and usage data, payment details | Legitimate interests (protecting the Service, our users and third-party sites); substantiated legal obligation where applicable |
| Security and incident response — investigating incidents, securing accounts, maintaining audit trails | Security and audit logs, account details | Legitimate interests; legal obligation |
| Service messages — security alerts, scan summaries, digests, reports, receipts and account notices | Account details, apps and scan data | Performance of a contract; legitimate interests for security notices |
| Product analytics — understanding which features are used and where the app breaks | Device and usage data, cookies and storage | Consent (Art. 6(1)(a) GDPR), collected through our consent banner and never set before you accept |
| Optional marketing email | Account details, email preferences | Consent; legitimate interests (soft opt-in) for existing customers where law permits, always with an unsubscribe link |
| AI-assisted analysis you ask for | AI inputs and outputs | Performance of a contract; consent for optional features |
| Recruitment | Support, contact and application data | Legitimate interests in assessing applications; consent where required |
| Legal claims, compliance and responding to lawful requests | Any category relevant to the request | Legal obligation; legitimate interests in establishing or defending legal claims |
We do not sell your personal data, we do not share it for cross-context behavioural advertising, we do not run advertising pixels, and we do not use your content to train AI models ourselves. We do not use your data for automated decisions that produce legal or similarly significant effects — our scores and findings are informational and are always reviewed by a person before you act on them.
We use three kinds of cookies and browser storage, and every individual key is listed by name, purpose and lifetime in our Cookie Policy.
Consent and withdrawal. Optional analytics is off until you accept it in the consent banner shown on your first visit, and your choice is stored with a timestamp before any analytics event is sent. You can change your mind at any time by using the switch on our Do Not Sell or Share page, by clearing this site's browser storage and reloading the banner, or by sending a Global Privacy Control signal from your browser, which we honour automatically. Rejecting optional analytics does not affect your account, your scans, your plan or access to any feature. For how long each cookie lasts and what it does, see the Cookie Policy.
We share personal data only with the processors below, only what each one needs, and under written data-protection terms. There are no data brokers, advertising networks or cross-site trackers among them, and we do not sell data to anyone.
| Recipient | What they receive | Why |
|---|---|---|
| Base44 | All application data: account records, apps and scans, alerts, storage, logs, and the emails we send on our behalf through its email infrastructure. | Hosting, database, authentication and email delivery — it runs the platform the Service is built on |
| Stripe | Card and payment method details, billing email, plan or pack, amounts, invoices and fraud signals. | Payment processing, invoicing, subscription management and fraud prevention. We never see or store your full card number |
| AI model providers, reached through Base44's integrations (currently models from OpenAI, Google and Anthropic) | Only the content needed for the task: fetched page markup, scan findings, or the prompt or profile text you submitted. | Generating the analysis or fix you asked for. Never your password, payment details or account credentials |
| Google (Workspace, Sheets, Gmail) | Only the account identifiers and content needed for the features you enable — writing a report to a spreadsheet you choose, or emailing a summary to your own inbox. | Only if you connect a Google account |
| GitHub | Your GitHub username and the public repositories you ask us to scan. | Only if you connect GitHub |
| Browser push services (operated by Apple, Google and Mozilla) | An encrypted notification payload and the device endpoint. The payload is encrypted so the push service cannot read it. | Delivering the notifications you enable to your device |
| Analytics, through Base44 | Usage events from your browser, once you have consented. | Understanding product usage and fixing breakage |
| Professional advisers, authorities, and parties to a corporate transaction | Only what is necessary for the specific purpose: legal and accounting advice, a lawful request, or a merger, acquisition or sale of assets (with notice to you). | Compliance, legal claims, or a change of ownership |
Google user data. When you connect a Google account, we use Google user data only to provide the features you enable — writing a report to a spreadsheet you select and sending a scan summary to your own Gmail. We do not sell Google user data, use it for advertising, or let anyone read it, and we do not transfer it to third parties except as needed to provide those features, to comply with the law, or as part of a merger or acquisition. Our handling of Google user data complies with the Google API Services User Data Policy, including its Limited Use requirements. You can revoke our access at any time from your Google account's permissions page, or by disconnecting the integration in Presail.
Content you publish — prompts, author profiles and approved reviews — is public by design and visible to anyone who visits Presail. Do not include personal or confidential information in it. Testing rounds: the feedback people submit belongs to you; we store and show it to you, and to authorised Presail administrators only for support and abuse handling.
Retention is set by category, not by convenience. When a period ends, the data is deleted or anonymised, unless we must keep it longer to meet a legal obligation or to establish or defend a legal claim — in which case it is kept only for that purpose and then deleted.
| Category | How long we keep it |
|---|---|
| Account details | While your account is active. On deletion, identifying fields are anonymised within 30 days. |
| Apps, scan results, history, alerts and reports | For the life of your account, so you can track changes over time. Deleted with your account. |
| Payment records, invoices and credit purchases | 7 years after the transaction, to meet tax, accounting and dispute obligations. |
| Security and audit logs | 24 months. On account deletion, IP addresses are removed from your historical entries and the event trail is kept without identifying details. |
| Support conversations and contact messages | 24 months after the last reply in the conversation. |
| Cookies and browser storage | The lifetime stated for each key in our Cookie Policy — from 7 days up to 12 months for the consent record. |
| Analytics events | 14 months, then deleted or aggregated so they no longer relate to a person. |
| Push notification subscriptions | Until you turn notifications off, remove the device, or 12 months pass with no delivery. |
| Content you publish | Until you delete it or your account is deleted. |
| Testing-round feedback | Until you close the round, or until your account is deleted. |
| Job applications | 12 months from submission, unless you ask us to delete them sooner. |
| Backup copies | Up to 35 days after deletion, after which they are overwritten. |
When you delete your account we cancel any active subscription, delete your connected apps, scan history, alerts and published reviews, anonymise your profile (clearing your name, phone, preferences and payment-customer link), delete the OAuth connections you made, your device push subscriptions, report branding and custom frameworks, and remove IP addresses from your historical audit entries. The audit event trail itself — that an event occurred, with its type and timestamp — is retained with your identifying details removed, because it is what lets us investigate abuse and meet legal obligations. Deletion is immediate and irreversible.
Data is encrypted in transit with TLS and protected at rest by our hosting provider. Row-level security rules scope your apps, scans, alerts, testing rounds and widget data to your account, so another user cannot read or change them by calling the API directly. Scores and findings are written only by our servers, so they cannot be forged from a client. Two-factor authentication is available, destructive actions require a recent two-factor verification, and sensitive endpoints are authenticated, rate limited and recorded in a security audit log. No system is perfectly secure, so we design on the assumption that any single control can fail — see the breach notification commitment in Section 13.
Depending on where you live, you have some or all of the rights below. We give you the tools to exercise most of them yourself, and we never charge you for a request or treat you differently for making one.
| Right | How to exercise it | Our response time |
|---|---|---|
| Access — a copy of what we hold about you | Email privacy@presailapp.com, or export scan data from the dashboard | Acknowledged in 10 business days, answered within 30 days (45 for California) |
| Correct — fix inaccurate data | Settings, profile and notification pages, or email us | Immediately, for self-service changes; within 30 days for a request |
| Export — receive it in a portable format | Export scan data to a spreadsheet from the dashboard, or ask us for a JSON copy | Within 30 days |
| Delete — erase your data | Settings → delete account (requires a recent two-factor verification), or email us | Immediately for self-service; within 30 days for a request |
| Restrict or object to processing | Email privacy@presailapp.com | Within 30 days |
| Withdraw consent | The consent banner, the Do Not Sell or Share switch, the unsubscribe link in any email, or disconnect an integration | Immediately |
| Complain | Email us first so we can fix it; you may also complain to your local supervisory authority at any time | We reply within 30 days |
Before we act on a request we may need to verify you are the account holder, usually by confirming control of the account email; we ask for no more than that. If someone is making the request for you as an authorised agent, we ask for your written permission and may still contact you directly to confirm.
If you are a California resident, the California Consumer Privacy Act as amended by the CPRA gives you the rights below. The categories we collect, the sources, the business purposes and the recipients are set out in Sections 3, 4, 6 and 7 of this policy.
Global Privacy Control. We honour the Global Privacy Control (GPC) signal as a valid request to opt out of sale and sharing. When your browser sends it, optional analytics stays off and no analytics event is recorded, without you doing anything on this site. We treat it as applying to this browser only, because we cannot link a browser signal to an account we have not verified.
To exercise a right, email privacy@presailapp.com. We confirm receipt within 10 business days and respond within 45 calendar days, with an extension of a further 45 days where reasonably necessary and notified to you. You may use an authorised agent; we may require proof of that authorisation and will still verify your identity directly.
Your data may be processed in countries other than your own, including by providers in the United States. Where required, we rely on standard contractual clauses and equivalent safeguards for those transfers, and we will give you a copy of the relevant safeguards on request to privacy@presailapp.com.
Presail is a business tool and is not directed to children. You must be at least 16 years old to create an account or use the Service. We do not knowingly collect personal information from anyone under 16, we do not sell or share it, and we do not target advertising to children.
If we learn that an account belongs to someone under 16 — through a report, a request, or our own review — we close the account and delete its personal information, including scan data and any content published, within 30 days of verifying that fact, and we notify the account holder's email on record. If you believe a child has given us personal information, email privacy@presailapp.com and we will act on it the same way, without requiring you to prove anything beyond a credible basis for the report.
If we become aware of a personal data breach, we contain it first, then assess its scope, the categories of data and the people affected, and the likely risk to them. We treat "become aware" as the moment we have a reasonable degree of certainty that a security incident has led to compromised personal data.
We may update this policy as the Service changes. Material changes — a new category of data, a new purpose, a new recipient, or a longer retention period — are notified by email and by a notice in the app at least 30 days before they take effect, and the date at the top of this page always shows the current version. Earlier versions are available on request.
Privacy questions, data requests and complaints: privacy@presailapp.com. Security researchers may report vulnerabilities responsibly to security@presail.app or via the details published at /.well-known/security.txt. Abuse of the Service or of a scanned site: abuse@presailapp.com. Our cookies are listed in the Cookie Policy, and the rules of using Presail are in the Terms of Service.
© 2026 Presail. All rights reserved.
We use analytics to improve Presail. You can accept or reject non-essential tracking. Cookie policy · Privacy policy · Do not sell or share.