1. What we collect
When you use NudgeHost, we collect:
- Account data: email address, optional name, hashed password, and the time you agreed to our terms and privacy policy at sign-up.
- Uploaded files: the content you upload for hosting, plus metadata like filename, size, and upload time.
- Connected apps: if you connect Linear, the name and ID of your Linear workspace, your Linear user ID, and the access keys Linear gives NudgeHost, which we store encrypted. For each link you send to Linear, we record the issue it went to. If you connect Basecamp, the IDs and names of the Basecamp accounts your login can reach, your Basecamp ID, and the access keys Basecamp gives NudgeHost, which we store encrypted. For each link you send to Basecamp, we record the project and the Docs & Files entry it went to. If you connect Notion, the name and ID of your Notion workspace, the ID Notion gives NudgeHost's connection, the database your links go to, and the access keys Notion gives NudgeHost, which we store encrypted. For each link added to Notion, we record its row there. If you add NudgeHost from Notion's side, the access keys are kept encrypted on our servers for up to ten minutes while we ask you to confirm, and deleted if you don't. If you make a key for the NudgeHost app in Attio, we store it as we store any API key, as a hash.
- Usage analytics: a record of each time a link is opened, with the time and the country it was opened from. We don't keep visitors' IP addresses, browser details or the page that sent them with these records. For a PDF read in NudgeHost's PDF viewer, the record also notes which pages were shown and for how many seconds. It holds no name, email address, IP address or browser details, and it's deleted with the open after 12 months. When someone opens a link the free plan has ended, we count the try by day and country only, with nothing about who tried it, and the count is deleted with the link.
- Payment data: handled by Stripe. We never see or store your card number; we receive a token and the billing email. When you start a checkout, we record where on the site you started it, the plan and billing period you chose, and whether the payment went through. We also record each time a plan limit stops an upload or a change, and the paid plan you picked before signing up, and we only ever read these as counts.
2. How we use your data
We use your data to:
- run the service (host files, generate links, render your dashboard)
- send the emails described below
- improve the product based on aggregated usage patterns
- comply with legal obligations
We do not sell your data, share it with advertisers, or use uploaded files to train AI models.
Emails about your account. Every account gets these:
- a welcome email when you sign up, and up to two more in your first week to help you get started
- an email the first time one of your links is opened, never more than one a day
- a reminder two days before a link on the free plan ends, an email the day it ends, an email the day before its file is deleted, and an email when your free plan fills, never more than one a day
- a thank-you when you buy a plan, and an email when a plan is cancelled or ends
- notices about your custom domains, security alerts and breach notices
- receipts and payment emails, which Stripe sends for us
You can turn off first-open emails and link reminders in Email settings on your dashboard, or from the link at the bottom of every email. Sign-in codes, billing emails, and notices about your plan, custom domains and account security keep arriving while you have an account.
Product news. About once a month we may email news about new features and our paid plans. If you start buying a plan and leave the checkout before paying, we may send you one reminder about that plan, at most once in 30 days. The sign-up form offers a box to say no to these, and we record your answer and when you gave it. Accounts made before the form offered that box, and accounts whose sign-up screen never showed it, don't get product news unless they turn it on in Email settings. Every product news email has an unsubscribe link that works in one click. When you unsubscribe, we keep your address on a list that blocks product news, so nothing adds you back by mistake.
We send emails about your account because they're part of the service you signed up for. We send product news because it's in our legitimate interest to tell customers about the service, and you can object at any time. Our emails carry no tracking pixels, and we don't record whether you open them or click their links. Links in our emails carry tags that tell Google Analytics a visit came from an email and from which one, with no name or email address. Replies to our emails go to support@nudgehost.com.
When a new account uses a company email address, we add the domain to a daily internal list so we can offer help to teams. The list never includes file names or contents.
3. Cookies and analytics
We use Google Analytics 4 to see which pages people open and which actions they take, such as signing up or starting a checkout. Google sets cookies in your browser to do that. The events we send carry no filenames, link slugs, email addresses, or account identifiers.
When you buy a paid plan, or move up to a bigger one, our server tells Google Analytics about the purchase once Stripe confirms the payment. It sends the plan, the billing period, the amount, the currency and Stripe's reference for that payment. It also sends the random identifiers Google Analytics set in your browser's cookies, so the purchase counts toward the visit that led to it. We store those identifiers at Stripe to carry them to our server. For a new plan they are kept on the checkout and on your subscription. For a move to Studio they are kept on your subscription. We don't remove them. The purchase event carries no name, email address, card details or account identifier.
If a payment is refunded, our server tells Google Analytics about the refund too, with the same reference and amount and nothing that identifies you.
We also use Microsoft Clarity, which records browsing sessions and builds heatmaps so we can see where a page is confusing people. It sets its own cookies.
Neither of them runs on the pages where hosted files are viewed. Measurement covers our marketing pages, the pricing page, and the signed-in dashboard. Session recording runs only for visitors who aren't signed in, on our marketing pages and the pricing page. It never runs on a link's own page, so a recording never contains the contents of a file somebody shared with you. File names and links shown on our own pages are masked.
We don't run ad-tracking pixels (Meta, TikTok, Twitter, LinkedIn). Alongside the Google Analytics and Clarity cookies, nudgehost.com sets cookies to keep you signed in and to remember for 12 hours which password-protected links you have opened, so you don't have to enter the password again.
If you choose a file, paste text or use a tool before you sign in, your browser keeps it in its own storage until your account is made, for up to a day. The file isn't sent to NudgeHost before then, and the browser's copy is deleted once the file is uploaded. Uploads made without an account before 29 October 2026 set a cookie called nh_anon, which holds a random code and lets those uploads move into an account made in the same browser. A browser that has it keeps it until it expires, a year after it was set. To limit abuse, we keep a hash of your IP address for up to two days, which counts uploads from your network and wrong password attempts on protected links.
4. Third-party services
NudgeHost runs on a small set of trusted services:
- Vercel: hosting for the website and the file viewer. Every request to NudgeHost passes through Vercel, which sees visitors' IP addresses and uses them to work out the country of each open.
- Cloudflare: file storage and bot protection. Visitors' browsers load most hosted files directly from Cloudflare's storage, so Cloudflare sees their IP addresses.
- Stripe: payment processing for paid plans. Stripe holds your card data, not us.
- Clerk: authentication and account management. Clerk sends the sign-in codes and security emails for your account.
- Resend: sends NudgeHost's emails. Resend receives your email address and each email we send you, and records whether it was delivered, bounced or reported as spam. If an address bounces or reports an email as spam, Resend stops sending to it.
- Google Analytics: site usage measurement, as above.
- Microsoft Clarity: session recording and heatmaps on the pages described above, never on the pages where hosted files are viewed.
- Sentry: error monitoring, in Sentry's EU region. When something breaks in your browser or on our servers, Sentry gets a report with the error, the page or request involved, and your browser and device type. A report from our servers can also name your account ID and the link, file name or domain involved. We send Sentry timings for a sample of requests too. No report includes a password, text you paste or share, or the contents of a file. Reports from your browser reach Sentry from your IP address, and Sentry is set not to store visitors' IP addresses. Reports from our servers leave it out. Sentry has a session replay feature of its own and we keep it turned off, so Clarity is the only thing recording sessions.
Each of these has its own privacy practices. We pick partners that hold themselves to GDPR standards.
Apps you connect. If you connect Linear from your dashboard, NudgeHost sends Linear the details of each link you choose to send: the file's name, type and size, the link's address, the day you sent it, and when the link ends, with any title and note you type for a new issue. Linear receives nothing until you send a link, and nothing about links you don't send. When a link you sent is replaced, deleted or ends, we update those details on the issue. Linear is a service you chose rather than one NudgeHost uses to run the site, so it handles that information under its own privacy policy. Disconnecting Linear, or deleting your account, deletes our access keys and asks Linear to revoke them.
If you connect Basecamp from your dashboard, Basecamp's approval screen asks whether NudgeHost may have access to your Basecamp accounts. It names no narrower permission, so approving it lets NudgeHost reach everything your Basecamp login can. NudgeHost uses that access only to list your Basecamp accounts and projects, and to add a link to a project's Docs & Files when you choose Send to Basecamp. The entry holds the link's address and the title and note you type. Basecamp receives nothing until you send a link, and nothing about links you don't send. Basecamp is a service you chose, so 37signals handles that information under its own privacy policy. Disconnecting Basecamp, or deleting your account, deletes our access keys at once.
If you connect Notion from your dashboard and choose a database, NudgeHost adds a row to it for each new link you make, including links made through the API or with Claude, and for older links you add yourself. The row holds the file's name, type and size, the link's address, when it was made, when it ends, and whether it is active, ended or deleted. When a link is replaced, deleted or ends, we update its row. With automatic adding switched off, Notion receives only those updates and the links you add yourself. NudgeHost never reads your Notion members or their email addresses. Notion is a service you chose, so it handles that information under its own privacy policy. Disconnecting Notion, or deleting your account, deletes our access keys and asks Notion to revoke them. Rows already in your database stay there.
If you use the NudgeHost app in Attio, it runs on Attio's servers and reaches NudgeHost with a key you make for it in Connected apps. NudgeHost receives only the files you choose to share from a record, as with any other upload, and stores nothing about your Attio workspace, records or people. When someone in your workspace opens a record, the app reads the opens of the links shared there from NudgeHost and shows them in Attio. On Free and Lite that is the count, and on Pro and Studio also the time and country of each open. Attio is a service you chose, so it handles that information under its own privacy policy. Deleting the key, or deleting your account, stops the app reaching NudgeHost.
AI assistants. You can use NudgeHost from an AI assistant such as ChatGPT or Claude. To connect one, you sign in to your NudgeHost account and approve it, and the assistant then holds an access token for your account. The approval screen lists what the assistant asks for. Signing in gives it your NudgeHost account ID, plus any other account details it asks for and you approve, such as your name or email address. Some assistants use an API key you make in your dashboard instead. NudgeHost receives only what the assistant sends for the task you ask for. That is the file name and text you ask it to publish, a file's name, type and size before the assistant uploads it, any link name you ask for, and how many links to list. We store what it publishes as we store any upload. In return the assistant gets the link's address and file name, a temporary address to send a file to when it uploads one, and when it lists your links, each link's address, file name and size and whether it has a password or an end date. ChatGPT also sends an anonymous user ID, your language and an approximate location with each request, and NudgeHost doesn't read or keep them. The assistant's provider handles your conversation under its own privacy policy. Removing NudgeHost in the assistant's settings stops it using your account, and deleting your NudgeHost account ends every assistant's access.
5. Data retention
- Active accounts: we keep your data while your account is active.
- Linear connection: kept until you disconnect Linear or Linear ends our access, when the access keys are deleted at once. The record of which issues a link went to is deleted with the link.
- Basecamp connection: kept until you disconnect Basecamp or Basecamp stops accepting our access, when the access keys are deleted at once. The record of which project a link went to is deleted with the link.
- Notion connection: kept until you disconnect Notion or Notion ends our access, when the access keys are deleted at once. The record of each link's row is deleted with the link, or with the connection when you disconnect. Access from a request started in Notion that you don't confirm is deleted after ten minutes, and we ask Notion to revoke it.
- Links on the free plan: on accounts made from 12 November 2026, a free link stops working 7 days after upload, and on accounts made from 29 October to 12 November 2026, 14 days after upload. Its file is deleted 7 days after that unless the account moves to a paid plan in that time. The 12 November 2026 changes took effect at 18:15 UTC that day.
- Links over a plan's limit: when a paid plan started from 12 November 2026 ends or moves to a smaller one, the links over the new plan's limit stop working 7 days later, and the newest links up to the limit keep working. On an account made from 29 October 2026 that moves to the free plan, every link stops then. On Free and Lite, the files of links that stopped are deleted 7 days after that, unless the account upgrades in that time.
- Deleting an account: you can delete your account yourself under Manage account in the account menu, or email support@nudgehost.com and we'll delete it for you. Its links stop working straight away, we stop sending it email, its API keys and any app signed in to it lose access, any custom domain is released and any paid plan is cancelled. Its email address is removed from the account at once. Its files, their earlier versions and their open records are kept for 30 days and then deleted, with the rest of the account. A deleted link's name is never given to anyone else.
- Accounts closed after a breach of our terms: when an account we blocked, or one holding a file we removed for breaking our terms, is deleted, we keep its files and email address for 30 days as evidence and send it no email. After that we delete them with the rest of the account, as for any other deleted account.
- What outlasts a deleted account: billing records, backups and the list of unsubscribed or bounced addresses are kept as this list says, and Stripe keeps payment records as the law requires it to. Error reports in Sentry and delivery records in Resend are deleted on those services' own schedules.
- Backups: we hold encrypted backups for up to 90 days for disaster recovery.
- Billing records: retained for 6 years as required by UK tax law.
- Analytics: a link's total open count is kept with the link. The record of each individual open is deleted after 12 months.
- Email records: we keep a record of which emails we sent you and when, while your account is open. The list of addresses that unsubscribed or bounced is kept after an account closes, so those addresses are never emailed again.
6. Your rights under UK GDPR
If you're in the UK or EU, you have the right to:
- Access the personal data we hold about you
- Correct inaccurate data
- Delete your account and the personal data we hold (right to be forgotten)
- Export your data in a portable format
- Object to marketing at any time. Turning off Product news in Email settings, or using the unsubscribe link in any product news email, takes effect straight away.
- Withdraw consent at any time where we rely on consent
To exercise any of these, email support@nudgehost.com. We'll respond within 30 days.
7. Children's privacy
NudgeHost isn't directed at children under 13. If we find we've collected data from someone under 13, we'll delete it. If you believe a child under 13 has signed up, please email us.
8. International transfers
NudgeHost is operated from the United Kingdom. Some of our service providers (Cloudflare, Stripe, Microsoft, Resend) operate globally. Data transfers outside the UK are protected by Standard Contractual Clauses or equivalent safeguards.
9. Security
We encrypt data in transit (TLS) and at rest. Passwords are hashed with bcrypt. We restrict internal access to user data and audit it regularly. No system is perfectly secure; we'll notify affected users within 72 hours of any confirmed breach involving personal data.
10. Changes to this policy
We may update this policy. Material changes are flagged by email to active accounts at least 14 days before they take effect.
11. Contact and supervisory authority
NudgeHost is run by Mark Boreland, a sole trader in the UK.
Privacy questions: support@nudgehost.com.
If you're in the UK and aren't satisfied with our response, you have the right to lodge a complaint with the Information Commissioner's Office (ICO), the UK's supervisory authority for data protection. Visit ico.org.uk for details.