Legal
Privacy Policy
1. Who we are
Quillnest is provided by [COMPANY LEGAL NAME], a company registered in England and Wales under company number [COMPANY NUMBER], whose registered office is at [REGISTERED ADDRESS]. We are registered with the Information Commissioner’s Office (ICO) under number [ICO REGISTRATION NUMBER].
For any question about this policy or your personal data, write to [CONTACT EMAIL, e.g. privacy@usequillnest.com].
Our main framework is the UK GDPR and the Data Protection Act 2018. Where we offer the Service to people in the European Economic Area, the EU GDPR also applies, and our EU representative is [EU REPRESENTATIVE, if required].
2. Our two roles: controller and processor
Quillnest is used by businesses, usually studios and agencies (our “Customers”), who invite their own team and their clients (“End Clients”) to work on projects together.
- We are the controller of the data we need to run our own business: sign-up and account details, billing records, the emails we send about your account, and security and service logs.
- We are a processor for the content our Customers and their End Clients put into Quillnest: project files, messages, approvals, agreements and signatures, and the personal data in them. We process it only on the Customer’s instructions, under the data processing terms in our Terms of Service. The Customer is the controller.
If you are an End Client and want to exercise your rights over project content, please contact the business that invited you. We will help them respond.
3. What we collect
| Category | Examples | Where it comes from |
|---|---|---|
| Account details | Name, email address, username (the name clients see), job title, time zone, role, password (stored only as a one-way hash) | You, when you sign up or accept an invite; your organisation’s admins |
| Organisation and workspace details | Company name, plan and trial dates; each workspace’s name, colour, logo, welcome message and reply-to address | The Customer |
| Project content | Files and their earlier versions, chat messages and mentions, deliverables, approval requests and answers, notes | Customers, their teams and End Clients |
| Agreement and signature records | Typed name, email address, time of signing, IP address, browser (user agent), and a hash of the exact terms accepted | The End Client who signs |
| Notifications and digests | Notifications in the app, the daily digest, approval reminders and the records of what was sent | Generated by the Service |
| Audit and activity records | Who created, edited, activated or deactivated an account or changed a role; project activity | Generated by the Service |
| Security and technical data | IP address, used to rate-limit sign-in and other requests and to protect the Service; browser and device details in server logs | Your browser |
| Billing data (once billing starts) | Plan, invoices, payment status. Card details would be handled by a payment provider, not stored by us | You and our payment provider |
| Correspondence | Emails you send us and our replies | You |
4. Why we use it, and our lawful bases
Where we are the controller, we rely on the following lawful bases under Article 6 of the UK GDPR:
| Purpose | Lawful basis |
|---|---|
| Creating and running your account, confirming your email address, providing the Service and support | Performance of a contract |
| Sending service emails: confirmations, invites, approvals, reminders, digests and notices about your account | Performance of a contract |
| Keeping the Service secure: rate limiting, preventing abuse and fraud, investigating incidents, keeping audit records | Legitimate interests (protecting our users and the Service) |
| Billing, accounting and tax records (once billing starts) | Performance of a contract; legal obligation |
| Improving the Service using aggregate, non-identifying information | Legitimate interests |
| Complying with the law, responding to lawful requests, and establishing or defending legal claims | Legal obligation; legitimate interests |
We do not currently send marketing emails. If we start, we will only do so as the Privacy and Electronic Communications Regulations 2003 (PECR) allow, and every message will let you opt out.
Where we act as a processor, the Customer decides the purposes and lawful bases. For example, a Customer may use Quillnest’s keyword alerts to flag client messages containing words such as “refund” for its owners to review.
5. Electronic signature records
When an End Client accepts a Customer’s terms in Quillnest, we record their typed name, email address, the time, their IP address, their browser’s user agent and a hash of the exact text accepted. This creates an audit trail that shows who agreed to what, and when. We email the signer a copy. We hold these records as the Customer’s processor, and the Customer can download the record for its own files.
6. Emails we send
We send transactional emails through our email provider (see section 8). A client’s invite and agreement emails are sent in the name of the Customer’s brand and its team member, so that the client recognises who they are working with. Replies go to the address the Customer chooses.
8. Who we share it with
We do not sell personal data. We share it only with the service providers (sub-processors) that help us run Quillnest, under written contracts that require them to protect it, and where the law requires us to.
| Provider | What they do | Where |
|---|---|---|
| Railway Corporation | Hosting of the application, database (PostgreSQL) and cache (Redis) | [REGION: confirm, US or EU] |
| Tigris Data (t3.storageapi.dev) | Storage of uploaded files and their versions | [REGION: confirm] |
| Resend | Sending transactional email | [REGION: confirm, US or EU] |
| Google (Google Fonts) | Serving web fonts; receives visitors’ IP addresses | [REGION: confirm] |
| Cloudflare (cdnjs) | Serving JavaScript libraries on some app pages; receives visitors’ IP addresses | [REGION: confirm] |
We may also share data with professional advisers, with a buyer of all or part of our business (who would have to respect this policy), or with authorities where the law requires it.
9. International transfers
Some of our providers may process data outside the UK and EEA, including in the United States. Where they do, we protect the transfer with UK adequacy regulations (including the UK Extension to the EU–US Data Privacy Framework where the provider is certified), the UK International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses, and, for EU data, the EU Standard Contractual Clauses. You can ask us for a copy of the relevant safeguards.
10. How long we keep it
- Sign-ups whose email address is never confirmed are deleted after 7 days.
- Invites are deleted 30 days after they expire or are used.
- Uploads that were started but never finished are deleted after one day.
- Account and project data is kept while the organisation’s account is open. After it closes, we delete it within [RETENTION AFTER CLOSURE, e.g. 30 days], as set out in our Terms of Service, and backups are overwritten within [BACKUP RETENTION, e.g. 35 days].
- Electronic signature records are kept for as long as the Customer keeps the agreement in Quillnest, and in any case for [SIGNATURE RECORD RETENTION, e.g. 6 years after signing] unless the Customer asks us to delete them earlier.
- Billing and accounting records are kept for 6 years, as UK tax law requires.
11. Security
We use encryption in transit (HTTPS), secure and HTTP-only session cookies, hashed passwords, rate limits on sign-in and other sensitive actions, and access rules that keep each organisation, workspace and project apart. Files are served through signed links that expire. No system is perfectly secure, but if a breach affects your data we will tell you, and the ICO, as the law requires.
12. Your rights
Under the UK GDPR (and the EU GDPR where it applies) you have the right to: access your personal data; have it corrected; have it erased; restrict or object to our processing; data portability; and, where we rely on consent, withdraw it at any time.
To exercise a right, write to [CONTACT EMAIL, e.g. privacy@usequillnest.com]. We will reply within one month, which we may extend by two months for complex requests. We may need to confirm your identity first. If your request concerns project content held for a Customer, we will pass it to that Customer.
You can complain to the Information Commissioner’s Office at ico.org.uk, or, in the EEA, to your local data protection authority. We would be grateful for the chance to resolve your concern first.
13. Automated decisions
We do not make decisions about you based solely on automated processing that have legal or similarly significant effects. Features such as keyword alerts and digests only bring items to a person’s attention.
14. Children
Quillnest is a business service and is not intended for anyone under 18. We do not knowingly collect children’s personal data.
15. Changes and contact
We will update this policy when our practices change, and show the date at the top. If a change is significant, we will tell account owners by email.
Contact: [CONTACT EMAIL, e.g. privacy@usequillnest.com] · [COMPANY LEGAL NAME], [REGISTERED ADDRESS].