Privacy policy
Last updated November 17, 2026
This policy says what Quotebarrow collects, why, where it is kept, who else handles it, and how long we keep it. Quotebarrow is run by Redwood Digital LLC, a limited liability company formed in Wyoming, 30 N Gould St, Ste N, Sheridan, WY 82801, USA ("we", "us"). Questions: support@quotebarrow.com.
Two groups of people use Quotebarrow: customers, the businesses that sign up and send proposals, and recipients, the clients who receive, read and sign them. For what's inside a proposal, the customer decides what goes in and who it goes to; we keep and process it to provide the service to them.
What we collect
From customers
- Account: your email address, your password (stored only as a one-way hash), whether your email is verified, and your sign-in sessions. If you turn on two-factor sign-in, the authenticator secret and your recovery codes. When we email you a service notice our terms promise (for example 30 days before a price or terms change), a record that we sent it and when, so no one gets it twice; it is deleted with your account.
- Teams: team names, who is a member and their role, and the email addresses you invite.
- Proposals: everything you put in them: text, prices, client details in merge fields (such as a client's name, company or address), images you upload (shrunk when you upload them, and saved again without the camera details, time and location that phone photos carry; we don't keep the original file), saved blocks, and each version you send.
- Your activity on proposals: steps you take (for example creating, sending, revising, withdrawing or countersigning) are recorded in the proposal's audit trail with the time, your email address (as the team member who took the step), your IP address and your browser's user-agent string.
- Your countersignature, where a proposal asks for one: the same details as a recipient's signature (below).
- Billing: your plan, subscription status, renewal date, any scheduled plan change or cancellation, and the reference numbers Paddle gives us. We never see or store your card or bank details: Paddle collects them (see "Who else handles your data").
From recipients
- Contact details the sender enters: your name and email address.
- Activity on the proposal link: when you first opened it and last viewed it, how long you spent on it and on each section, and whether you signed or declined (with any reason you give). The sender sees this activity.
- Audit trail: each step (for example opened, consented, signed, and withdrawing your consent to electronic records) is recorded with the time, your IP address and your browser's user-agent string, and the version of the e-signing notice you agreed to. These details appear on the signing certificate that is emailed with the final signed PDF to everyone the proposal was sent to, and to the sending business, and that the sending business can download from the proposal page. When a copy is emailed, or an attempt to email it fails, the proposal's records (not the signing certificate) also note the address it was for and, for an email that went, the message's identifiers (ours and the email provider's). When the signed PDFs are too large to attach, the email carries a private link to download them instead. If the proposal is later deleted, these notes stay with its audit trail (see "How long we keep it").
- Email delivery problems: if an email to you about a proposal bounces, or you mark it as spam, our email provider tells us. The proposal's records note the kind of problem and when, and the sender is told that the proposal wasn't delivered to you and why. We don't keep the provider's bounce message.
- Your signature: the name you sign with, any title and company you add, the typed or drawn signature itself, the options you selected, and a fingerprint (SHA-256) of the document you signed. These go into the signed PDF and its signing certificate, which are emailed to everyone the proposal was sent to and to the sending team. When you sign, a PDF of what you signed is also emailed to you at once.
From the free proposal generator
- Your answers to its questions (for example your business name, your client's name and your price lines). We keep the proposal for 14 days so its share link works, then delete it, unless you save it to an account.
- To enforce the daily limits, a keyed hash of your IP address (not the address itself), kept with the time of each proposal and PDF made, and with the free proposal itself.
From the business inquiry form
- What you type into the "Business: talk to us" form (your company, team size, the needs you choose, your email address and your message) is emailed to our support mailbox so we can reply. The app doesn't keep a copy in its database. The email is kept in our support mailbox, to answer your inquiry and as business correspondence, for 2 years after the last message, then deleted in our next yearly clean-out (so within 3 years of the last message), unless you ask us to delete it sooner at support@quotebarrow.com.
- To enforce the form's daily limits, a keyed hash of your IP address (not the address itself), kept with the time of each message sent, or tried and not sent because our email failed.
From everyone
- Server logs: the web server's log keeps each request, sign-in requests included, with its IP address and port, time, method, site name and page requested, the connection's protocol and encryption version, and the response code, size and time taken (no request headers, so no cookies, browser user agent, language or referring page), so a failed sign-in is in it with its IP address. The app's own log records each failed sign-in with only its time and a keyed hash of its IP address (IPv6 addresses by their /64 network), never the IP address itself or the email address. Private proposal and share link codes are removed from these logs.
- Cookies: only those the site needs to work: a session cookie that lasts up to 14 days (when you sign in, sign up, reset a password, confirm an email address or use the free generator), a security (CSRF) cookie for forms, and a short-lived cookie that carries on-screen messages between pages. We use no advertising cookies. When a team owner opens the Billing page, Paddle's script loads from Paddle's servers, so Paddle receives the owner's IP address and browser details; Paddle's checkout runs in Paddle's own frame and may set Paddle's own cookies.
- Sessions: the session cookie points to a session record in our database (so it is also in our backups). While you are signed in, it holds your account number and the email address you signed in with. While you sign up, reset a password or confirm an email address, it holds the email address you typed and the code we emailed, in clear, until the step is finished or the session ends. For the free generator, it holds your proposal's share link (see "How long we keep it").
- Security records: to slow down password guessing, recent attempts to sign in, sign up, reset a password, confirm an email address or enter a two-factor code are counted per IP address, per email address or per account, with the time of each attempt. Failed sign-ins are counted per IP address, and per email address together with the IP address it was typed from (IPv6 addresses by their /64 network), so a few wrong passwords that someone else types for your email address from a different IP address or network don't stop you signing in. Each email address also has a loose cap, from any IP address: after 50 failed sign-ins in one clock hour (UTC), signing in, or confirming your password while signed in, with that address pauses until the hour ends or its password is reset (this count holds a number for the hour, not the times). In these counts, addresses are stored only as keyed hashes (HMAC-SHA-256), never in clear. A daily job soon after midnight UTC deletes these counts once they expire, so each is kept for at most 25 hours, unless that job fails, which alerts us so we can run it again. Each failed sign-in is also written to the app's own log with a keyed hash of its IP address (not the address itself); the web server's log keeps the sign-in request with its IP address (see Server logs above).
- How you found us: We record how a team first found us (for example, a "Made with" link or a search page) and keep daily visit counts with no personal data. The link carries this, not a cookie. When a team signs up through the "Made with" link on another team's proposal page, PDF or Word file, we also record which team's link it was: the link carries a random code for that team, not a name or an email address, and we use it only to see how teams bring in other teams. We also keep daily counts of badge views and of invites sent and accepted, with no personal data.
- Analytics and error reports: apart from those counts, not in use yet. We plan to count page visits with Umami (which doesn't use cookies) and to send details of app errors (such as the page, browser and time) to GlitchTip. We'll update this policy before either is switched on.
Why we use it
- To run the service: sign-in, storing and sending proposals, showing senders when proposals are opened and signed, and making signed PDFs.
- To keep a record of each signature as evidence for both sides.
- To send the emails the service needs: sign-in codes, security notices to you (for example when your password, email addresses or two-factor sign-in change, with the time, IP address and browser of the change), proposals, notices to senders, and signed copies. We don't send marketing email from Quotebarrow without asking first.
- To bill paid plans (through Paddle), prevent abuse, keep the service secure and fix errors.
We don't sell personal information, don't share it for advertising across other businesses' sites, and don't use it for advertising.
Do Not Track: we don't track visitors across other websites, and our pages load no advertising or social-media trackers, so a browser's Do Not Track signal doesn't change what we collect.
Where it is kept
The app and its database run on a server we rent from OVHcloud in the United States. Images are stored in the same database. Backup copies are stored with Backblaze B2 in the United States. If you use Quotebarrow from outside the United States, your information is sent to and processed in the United States.
Who else handles your data
- Paddle.com is the Merchant of Record for all our orders. Paddle collects your name, email address, billing address, payment details and country to take payment, calculate tax, send receipts and handle refunds. Paddle's own privacy policy covers what it does with them.
- Postmark (ActiveCampaign) delivers our emails, so it handles recipients' email addresses and the content of the emails, including attached signed PDFs, and keeps a copy of each email, attachments included, for 45 days (Postmark's standard retention; we don't buy longer retention), then deletes it.
- OVHcloud hosts the server; Backblaze stores the backups.
- Umami and GlitchTip, once switched on (see above).
- The people a proposal is sent to, and the team that sent it, see that proposal and its activity and audit trail.
- We may share information if the law requires it, or to protect the service or someone's safety.
How long we keep it
- Proposals, their versions, audit trails, signatures and signed PDFs: until the team deletes the proposal or the team itself is deleted. Only a team owner can delete a proposal that anyone has signed, and recipients should keep the PDFs emailed to them. Copies already emailed stay with the people who received them.
- Signed records after deletion: when a proposal that anyone signed is deleted (on its own, or with its team or an account), we keep its audit trail for 6 years as evidence for both sides, then delete it. That record holds who it was sent to and who signed (names, email addresses, any title and company), the email address of each team member who created, sent, revised, withdrew or countersigned it, each step's time, IP address and browser, the consent versions, the options chosen, the fingerprints (SHA-256) of the documents, and the details of each step, including the address each copy was emailed to, or failed to reach, and the message's identifiers. It keeps the proposal's title, but not its content, any decline reason, the drawn signature or the signed PDF.
- Images: until the team deletes the image on its Images page, or deletes the last proposal or saved block that uses it, or the team itself is deleted. An image in a draft, in a version that was sent, or in a saved block can't be deleted on its own. A browser that showed a deleted image may keep its own copy for up to a day.
- Saved blocks: until the team deletes the block or the team itself is deleted.
- When you delete your account, your sign-in details are deleted, including your sign-in sessions on every device, any pending password reset or email confirmation for your addresses, and our admin tools' notes about your account, and so is every team where you are the only member, with all its data. A team you share with others stays with them, including proposals you made and your countersignatures on them. The audit trails of proposals you worked on keep your email address as the team member who took each step (and as the countersigner), so each record still shows who acted for the business; they are kept, and deleted, as the proposals and signed records above, even after your account is deleted.
- Team invitations: kept with the team, including expired ones, until the team deletes them or the team is deleted.
- Free generator proposals (with the keyed hash of the maker's IP address): 14 days, unless saved to an account; the share link stops working then, and a daily job deletes the proposal within a day after. Daily-limit records: 2 days, then deleted by the same daily job within a day after.
- Business inquiry form: the app keeps no copy of what you send in its database. The email stays in our support mailbox, to answer your inquiry and as business correspondence, for 2 years after the last message, then is deleted in our next yearly clean-out (so within 3 years of the last message), unless you ask us to delete it sooner at support@quotebarrow.com. The form's daily-limit records (the keyed hash of your IP address): 2 days, then deleted by a daily job within a day after.
- Security records of sign-in attempts (keyed hashes of IP and email addresses, with attempt times): at most 25 hours, unless the daily job that deletes them fails (see above). Failed sign-ins in the app's log, with keyed hashes of their IP addresses: as other server logs (below). Sign-in requests in the web server's log, with their IP addresses: as that log (below).
- Sessions (with the email address and any pending code they hold, and the free generator's share link): until the session expires, 14 days after it last changed, then a daily job soon after midnight UTC deletes it, so a session is kept for at most 15 days after its last change, unless that job fails, which alerts us so we can run it again. Signing out deletes the session at once.
- Support notes: when we change an account, team or email address in our admin tools (for example at your request), the change is logged with its time and the item's name (an email address is named by the address, a team by its name). Notes about your account, its email addresses and the teams deleted with it go when you delete your account; notes about a team that stays are kept with the team.
- Billing records: as long as Paddle and the law require.
- Backups: when something is deleted from the live service, its backup copies are deleted within 90 days. While we recover from a security incident, we may keep backup copies longer, so deleted data can stay in our backups past 90 days; we go back to the usual schedule within 30 days after the recovery ends.
- Server logs: a new web-server log file is started every day, and log files older than 30 days are deleted. Other server logs, including the app's log of failed sign-ins with keyed hashes of their IP addresses, are kept in a few files of limited size: the oldest file is deleted when a new one is started, so an entry is kept until its file is rotated out, which takes longer when the service is quiet.
Your choices
- Customers can export their team's proposals, delete any proposal, delete images and saved blocks they no longer use, and delete their account from inside the app.
- Anyone can email support@quotebarrow.com to ask what we hold about them, or to correct or delete it. We'll reply within 45 days. If you received a proposal, we may refer you to the business that sent it, since it decides what the proposal holds. A signed record may be kept where the law or the other party's rights require it.
Security
We use encrypted connections (HTTPS), store passwords only as hashes, offer two-factor sign-in, store only a hash of each private link code in our records (except the free generator's share link, which is also kept in your session record on our server until the session ends; see Sessions), and keep backups with a separate provider. No system is perfectly secure. If we learn of a breach that affects your personal information, we'll investigate promptly and tell affected customers, and other people where the law requires, without unreasonable delay and within any time the law sets.
Children
Quotebarrow is a business tool and isn't meant for anyone under 18.
Changes
We'll update the date at the top when this policy changes, and email customers before a change that matters.