---
title: "proposal.here Privacy Policy"
description: "What personal information proposal.here collects from workspace users, proposal recipients and website visitors, how AI drafting uses it, who processes it, how long it is kept and the rights you have."
url: https://proposal.here/privacy
markdown: https://proposal.here/privacy.md
effective: 2026-11-14
---

# proposal.here Privacy Policy

Effective November 14, 2026 (version 2026-11-14).

## 1. Who we are

proposal.here is operated by **AiSDR Inc.** ("**AiSDR**", "**we**", "**us**"), a Delaware corporation at 2261 Market Street, San Francisco, CA 94114, United States. AiSDR also operates the AiSDR sales-development product at [aisdr.com](https://aisdr.com), which has its own privacy policy; this policy covers proposal.here only.

For privacy questions or requests, email [team@proposal.here](mailto:team@proposal.here) or write to the address above.

## 2. Who this policy covers

This policy applies to the proposal.here website, web application and APIs, and to the proposal and agreement pages the Service publishes (together, the "**Service**"). It describes our practices for four groups of people:

- **Workspace users** — people who create or join a company workspace;
- **Proposal recipients** — people who open a proposal or agreement link that a workspace shared with them;
- **People in customer content** — prospects, call participants, CRM contacts and signatories whose details appear in the calls, CRM records, proposals and agreements a workspace brings into the Service; and
- **Website visitors** — people who read the public pages, blog and samples.

**Our role.** For workspace accounts, billing, the website and the security of the Service, we decide how and why personal information is processed (we are the "controller" or "business"). For the content a workspace brings in or generates, including recipient engagement and the details of its prospects, the workspace's company decides; we process that information on its instructions as its "processor" or "service provider". If you are a recipient or a prospect, the company that sent you the proposal is responsible for that information; contact them with questions or requests, and we will help them respond. The section "Your rights and choices" explains how.

## 3. Information we collect

**Account and profile.** When you sign in through our authentication provider (Clerk) we receive your name, email address, profile picture and the sign-in method you used (email and password, or a provider such as Google). We store your role in your workspace, when you joined and when you agreed to our Terms.

**Workspace details you provide.** Company name and website, logo and brand settings (colours, fonts and logo, which the Service can extract from your public website), industry and description, email domains allowed to join, price book entries, FAQs and knowledge files or links, proposal prompt instructions and section settings, and the legal details you enter for agreements (legal entity, address, signatory and governing law).

**Content from connected tools.** If your workspace connects a tool, we access only what the feature needs:

- *Fathom* — your call list and, for the call you choose, its transcript, summary and participants;
- *HubSpot* — the deals, companies and contacts you pick for a proposal;
- *Stripe (your account)* — we create payment links in your account and store the link address and status;
- *Dropbox Sign or BoldSign* — we send the agreement document with the signer's name and email and store the request identifier and signing status.

Connection credentials (API keys and tokens) are encrypted with an application key before they are stored, are never displayed again and are deleted when you disconnect the tool.

**Proposals and agreements.** Transcripts you paste or import, generated drafts and your edits, pricing, the prospect company's name, website and logo, the names and email addresses of prospect contacts, cover details, agreement text, exported files, and the status history of each document.

**Engagement data about recipients.** When someone opens a published proposal, the page stores a random identifier in that person's browser (local storage) and reports which sections were viewed and approximately how long they were on screen. If the recipient accepts or declines, we record that action and the name and email address they enter. We do not record IP addresses or device fingerprints for engagement tracking, and we do not combine this data across different senders' proposals.

**Billing.** For paid workspaces we store the plan, number of seats, billing interval and the identifiers Stripe assigns to your customer and subscription records. Card details, billing address and tax identifiers are entered directly with Stripe; we never see full card numbers.

**Usage and technical data.** Our application logs record the request path, status, timing and a request identifier, but not your IP address; our hosting provider processes IP addresses transiently to deliver and protect the Service. We record each AI drafting action (type, time, workspace and user) to apply plan allowances and detect abuse, and we keep error reports to fix problems. For the public pages of our website (not the workspace or published proposals) we count, per day and page, how many times the page was loaded by a person's browser, by a search-engine crawler and by an AI assistant, using the browser identification string each request carries; only the daily totals are kept, with no cookies, identifiers or IP addresses.

**How you found us.** When you create an account we store, once, the page on our website you first arrived at, the page you were on before signing up, the address of the site that linked you to us if your browser sent one (for example a search engine, an AI assistant or a social network) and any campaign tags ("utm_" parameters) contained in the link. We use this to learn which pages and channels bring new customers. It is tied to your account, is never combined with data from other websites, and is not shared with anyone. Identifiers contained in proposal or invitation links are removed before anything is stored.

**Communications.** Emails you send us, support conversations (including questions sent through the in-app help form) and anything you submit through "Share your wins". When we email you, our email provider records whether the message was delivered, bounced or marked as spam so that we stop sending to addresses that do not want or cannot receive mail.

**What we do not collect.** We do not collect precise location, biometric data or payment card numbers, and we do not use third-party analytics, advertising pixels or session-recording tools on the Service.

## 4. How we use information

| Purpose | Examples | Legal basis (where GDPR or UK GDPR applies) |
| --- | --- | --- |
| Provide the Service | Running your workspace, drafting proposals and agreements from your inputs, publishing pages, showing engagement, sending agreements through your e-signature provider | Performance of our contract with you; for content you bring in, your instructions as controller |
| Billing and account administration | Checkout, invoices, seat changes, renewal and payment-failure notices, tax compliance | Contract; legal obligation |
| Security and abuse prevention | Authentication, workspace isolation, applying plan allowances, investigating misuse, protecting recipients from malicious links | Legitimate interests in keeping the Service safe; legal obligation |
| Service communications | Notices about changes to the Service or these documents, security alerts, responses to your requests | Contract; legitimate interests |
| Product notifications | Telling the author when a prospect first opens a proposal, accepts or declines it, or when an agreement is signed; team invitations | Contract; each notification type can be turned off in Settings → Notifications |
| Getting-started emails | A short series of emails from our founder during a workspace's first weeks about how to use the Service | Legitimate interests; every message has a one-click unsubscribe and the series can be turned off in Settings → Notifications |
| Improving the Service | Aggregated statistics (for example median time to a first draft), reviewing failed generations to fix defects | Legitimate interests; we use de-identified data wherever possible |
| Legal compliance and enforcement | Responding to lawful requests, enforcing our Terms, establishing or defending legal claims | Legal obligation; legitimate interests |
| Customer stories | Publishing a quote or story about your workspace | Your consent (the "Share your wins" opt-in), which you can withdraw at any time |

We do not send marketing emails to workspace users or recipients without consent, we do not make decisions with legal or similarly significant effects about individuals by automated means, and we do not sell personal information or share it for cross-context behavioural advertising. Recipients of proposals never receive email from us.

**Support.** Messages to our support address or through the in-app help form are first read by an automated assistant that answers common how-to questions from our published help notes and the plan and usage facts of your own workspace. It cannot change anything on your account. Anything it cannot answer with confidence, and every question about billing, security, legal matters, bugs or account changes, is passed to a person who replies to you by email. Support conversations are kept for as long as your account exists and for up to 30 days afterwards.

## 5. How AI drafting uses your content

Drafting is performed by large language models operated by **OpenAI** (proposal drafts, section rewrites, prompt suggestions, brand extraction, summaries and legal-entity research) and **Anthropic** (contract templates and agreements). Requests are sent through the AI gateway of our hosting provider, Replit, to those providers.

A request contains only what the task needs: the transcript or CRM excerpt, your brand and knowledge settings, pricing, legal details and the current proposal or agreement text. The providers process it to return the draft. **We do not use your content to train AI models, and the providers handle it under API terms that do not permit them to train their models on it.**

AI output is produced from your inputs and may be inaccurate; our Terms of Use require you to review it before you send it. Our staff do not read your drafts except when you ask for support, when we investigate abuse or a failure, or when the law requires it.

## 6. Who we share information with

**Service providers (sub-processors).** We use the following companies to run the Service. Each receives only the information needed for its function and is bound by contract to protect it.

| Provider | Function | Location |
| --- | --- | --- |
| Replit, Inc. | Hosting, database, file storage and AI gateway (infrastructure on Google Cloud Platform) | United States |
| Clerk, Inc. | Sign-in, session cookies, verification and account emails | United States |
| OpenAI | AI drafting (see "How AI drafting uses your content") and the first-line reading of support messages (see "Support") | United States |
| Anthropic, PBC | AI drafting of contract templates and agreements | United States |
| Stripe, Inc. | Subscription checkout, invoices, payment methods and the billing portal for our own plans | United States |
| Exa Labs, Inc. | Web search used when researching a company's legal entity; queries contain company names and websites only | United States |
| Google LLC (Google Fonts) | Font files loaded by the browser when a page or proposal uses a web font; Google receives the browser's IP address | United States |
| AgentMail, Inc. | Sending our notification, onboarding, invitation and support emails, and receiving email sent to our support address | United States |
| Smartlead.ai | Mailbox warm-up: exchanges automated test emails with our support mailbox to keep delivery reliable; to do so it connects to that mailbox and can read the messages it holds | United States |

**Your connected tools.** When your workspace connects Fathom, HubSpot, Stripe, Dropbox Sign or BoldSign, information moves between the Service and that provider on your instructions and under your own agreement with it. We are not responsible for those providers' privacy practices.

**Recipients of your proposals.** A published proposal shows recipients your company name and logo, the proposal content and the contact details you include in it.

**Other disclosures.** We may share information with professional advisers under confidentiality; with authorities or courts when required by law or to protect rights, safety and the integrity of the Service (we notify the affected workspace beforehand where legally permitted); and with a successor in a merger, acquisition or sale of assets, who must honour this policy. Aggregated statistics that cannot identify anyone (such as the number of proposals drafted) may be published.

## 7. Cookies and local storage

The Service uses only cookies and browser storage that are necessary for it to work:

- **Authentication cookies** set by Clerk keep you signed in and protect your session.
- **Preference storage** remembers interface choices such as whether the sidebar is collapsed.
- **Proposal visitor identifier** — a random value stored in the browser of a person who opens a published proposal, so that repeat visits from the same browser are counted once. It contains no personal details and is not shared across senders.
- **First-visit memory** — the first page you opened on our website, the page you were on before signing up, the referring address and any campaign tags in the link, kept in your browser for up to 180 days or until you create an account, when it is reported to us once and removed (see "How you found us" above). It contains no personal details.

We do not use analytics, advertising or social-media cookies, and we do not respond differently to "Do Not Track" signals because we do not track visitors across sites. You can clear or block cookies and site data in your browser; blocking authentication cookies prevents signing in. If we add analytics in the future we will update this policy and request consent where the law requires it.

## 8. International transfers

We are based in the United States and our service providers process information there. If you are in the European Economic Area, the United Kingdom or Switzerland, your information is transferred under the European Commission's Standard Contractual Clauses and the UK Addendum, together with supplementary measures such as encryption. The data processing addendum we offer to workspaces includes these terms; request it from [team@proposal.here](mailto:team@proposal.here).

## 9. How long we keep information

| Information | Retention |
| --- | --- |
| Account and workspace data | For as long as the workspace exists; deleted within 30 days after the workspace is closed |
| Proposals, agreements, knowledge files and other workspace content | Until you delete them or close the workspace; items you delete are removed from live systems immediately |
| Recipient engagement data | For as long as the related proposal exists |
| Connected-tool credentials | Until you disconnect the tool or replace the connection |
| AI usage records | 13 months, to apply monthly allowances and investigate abuse |
| Application logs and error reports | 30 days |
| Billing records and invoices | 7 years, as required by tax and accounting law |
| Backups | Encrypted backups rotate within 28 days; deleted data disappears from them on that schedule |

We may keep information longer where needed to comply with a legal obligation, resolve disputes or enforce our agreements, and we keep de-identified statistics indefinitely.

## 10. Security

We protect information with measures appropriate to the risk: encryption in transit (TLS 1.2 or higher) and at rest (AES-256) on our hosting platform, additional application-level encryption of connected-tool credentials, strict separation between workspaces, role-based access inside each workspace, least-privilege access for our staff, logging and monitoring, and infrastructure providers that hold independent security attestations (SOC 2 Type 2). Payment details never touch our servers.

Published proposal links are unlisted but can be opened by anyone who has the address; share them only with intended recipients and unpublish when they are no longer needed. No method of transmission or storage is completely secure, so we cannot guarantee absolute security. If a personal data breach affects your information we will notify you without undue delay and, where we act as your processor, in time for you to meet your own notification duties.

## 11. Your rights and choices

**Everyone.** Depending on where you live you may have the right to access the personal information we hold about you, to correct or delete it, to receive a copy in a portable format, to restrict or object to certain processing, to withdraw consent you gave, and to not be discriminated against for exercising these rights. Under the GDPR and UK GDPR you may also complain to your local data protection authority; under the California Consumer Privacy Act you may exercise the rights to know, delete, correct and opt out of sale or sharing (we do not sell or share personal information), and you may appoint an authorised agent.

**How to exercise them.** Email [team@proposal.here](mailto:team@proposal.here) from the address associated with your account, or write to the address above. We will verify your identity, respond within 30 days (45 days where California law applies) and tell you if we need more time. If we decline a request we will explain why and how to appeal.

**Workspace users.** You can update your name and sign-in details in your account settings, and owners and admins can edit or delete workspace content, disconnect tools, remove members, change the "Share your wins" opt-in and cancel subscriptions in the application. To close a workspace entirely, the owner emails [team@proposal.here](mailto:team@proposal.here).

**Recipients and prospects.** The company that shared a proposal or agreement with you controls that information. Please direct requests to them; if you are not sure who that is, email us with the proposal link and we will forward your request and assist them in responding.

## 12. Children

The Service is for business use by adults. It is not directed to anyone under 18, and we do not knowingly collect information from children. If you believe a child has provided us with personal information, email [team@proposal.here](mailto:team@proposal.here) and we will delete it.

## 13. Changes to this policy

We will update this policy when our practices or the law change. The date at the top shows when the current version took effect. For material changes we will give at least 15 days' notice by email to workspace owners or inside the application before the change applies, and we will ask workspace users to acknowledge the updated documents the next time they sign in.

## 14. Contact

AiSDR Inc.
2261 Market Street, San Francisco, CA 94114, United States

Privacy requests, support and legal notices: [team@proposal.here](mailto:team@proposal.here)

---

Canonical HTML: https://proposal.here/privacy · Terms of Use: https://proposal.here/terms.md
