HOME / COMMUNITY Switch to knowledge base

Data Protection Compliance with GDPR


Hello there,

Just wanted to ask for an update on your GDPR compliance please? I notice that this conversation was some time ago and since we only have a few months to go I wanted to see how compliance was going with Quickfile. I’m sure many other users are thinking the same especially as we are all trying our best to meet this new law with our businesses.

Kind regards


Hi Sandra,

We are currently working in collaboration with a law firm to update our terms of service and privacy policy. We’ve also completed ~75% of the back-end changes to support the specific provisions within GDPR. We remain on track to have everything in place by 25th May.



In light of the upcoming GDPR changes I wonder if you could help with the following queries
Do you have a GDPR statement and what measures are in place for you to be compliant with GDPR by May 2018?
Where is the data we input stored?
Do you have a data protection officer?
Do you inform me when you transfer data?
What controls do you have in place to reduce risk? /What are your risk management processes?
Who can access the data that you hold?
Do you have security breach notifications in place?
Do you adhere to Binding Corporate Rules (BCRs)?
What measures are in place for you to be compliant with GDPR by May 2018?

I look forward to your reply.



Hello @opengenius

You should have seen a notification when you recently logged into your account regarding our updated policies which should address some of your queries.

I’ve also merged your posts into an existing thread for GDPR which hopefully answers some of your queries too. However, please do let us know if we can help further.

In case you haven’t yet seen the notification, you can find our updated Privacy Policy here:
Privacy Policy

(correct at time of posting)



I am sorry but I may have missed those notifications. Are they available to view now and if so where would I find them?

Many thanks



They appear when you log in you should see it. I don’t believe there is a way to bring it back up once you’ve acknowledged it, but for reference, this is what it looks like:


The two links go to the following pages:


Hi there,
Could we please get an update on how you’re doing with GDPR compliance? I’m most concerned about being able to pass on the rights that GDPR codifies (rights to erasure, portability, etc.) to my clients.
Many thanks,


Hi @Jenii_Lowe

Everything regarding this should be covered above or in the privacy policy (also linked above). But please don’t hesitate to let us know if you have any additional questions.


Thank you, but your privacy policy only informs users of their own rights to erasure, portability, etc that I would expect from any EU provider. I’m more curious as to what QF allows me to do if a client of mine wishes to exercise those rights? And how to perform those actions in QF? I know you’re GDPR compliant, but I need to make sure I am too in using QF - if that makes sense!


AIUI you aren’t prevented from holding normal accounting information in any way. The only issue that I can think of as a layman is with named contacts within a client organisation and, as long as you are only holding those that are required for the performance of your contract with them then there shouldn’t be an issue.

If that wasn’t the case you could have people demanding to have their unpaid invoices deleted. (I suspect that some chancer in this world will try though)

Memo to self - I still need to write my own privacy policy,


Hi @Jenii_Lowe

As @FolkLondon points out, with accounting records you’re actually required to keep these for a minimum of 6 years by HMRC (see here) so data like invoices (with client details) shouldn’t be deleted as such.

All data within your account is exportable to a .CSV format which is a common machine readable format and supported by many different packages (for portability). The client portal would also allow your clients to view the data you store related to them.

If the time comes that you wish to use a different package and delete your data from QuickFile, then upon request, we will delete any data held on your account.

However, if you are uncertain on any aspect of GDPR in regards to the data you hold, I would advise you to seek professional advise on this to ensure everything is correct.

I hope this helps!


I’ve checked the new updated policies as above but it talks about the data you hold as a Data Controller and I can’t find anything about you acting as a Data Processor.

I would understand that you are the Data Controller for the details you hold on our account with you, but where I enter my client details onto your software I am the Controller and Quickfile is the Processor. Do you have a Controller to Processor Data Processing Addendum to your main TCs and Cs.

As a controller who uses a processor we need that in place with you to ensure that we are adhering to the new legislation. Sorry if I’m misunderstanding this.
Thank you.


Hi @Alison

As we are acting as your Data Controller we have an obligation to inform you how we collect, store and process your personal data in line with GDPR. Our privacy policy does not extend any specific rights or remedies to your client and therefore we do not include any addendum to our privacy policy that addresses this question.

Typically what you would do here is publish a list of your own sub-processors, where QuickFile would feature. We have our own list of sub-processors here, although I don’t believe this is a strict requirement under GDPR, it does help to better inform customers on where data is stored and processed.

We will also be providing additional tools to help you comply with any exercising of rights posed by your customers under GDPR. Although as my colleague has mentioned, due to the types of documents we process on your behalf (e.g. invoices and financial transaction) the scope for requesting erasure is trumped by your obligation to retain financial records for tax purposes.

Another thing to note is that when clients are removed from QuickFile, the associated contacts (name, email, telephone number) are physically deleted. We will also be providing some additional tools to allow export of personal data from the client control panel.

I hope that answers your question, but please get back to us if you have any doubts.


Thank you everybody for your responses cc: @QFSupport

@FolkLondon - I know I’m probably going overboard in worrying about this, one would think that keeping essential accounting stuff comes under “legitimate use”. I did crack a smile at your hypothetical chancer though! Hopefully nobody’s going to try that!

Great question @Alison, and great response @Glenn. Please keep us updated as to the additional tools you’re planning!


Hi wondered if you could assist us with how we are to comply with GDPR


Hello @Asmaa

I’ve moved your post to the existing thread for this. All the information you require should be above in regards to QuickFile to help you determine how you would need to comply yourself.

If you have any questions about QuickFile’s side of things, please don’t hesitate to ask.


Forgive me if I have missed it, but is there a way in which those with access to their records (typically when an invoice is raised our customers can look at their account) can see the Quickfile privacy policy? Alternatively, is there a straightforward way in which we can email the privacy policy to our customers as a single mailshot using the resources within Quickfile?


Hi @JonC

There’s no email function within QuickFile for your clients, but you could export your client list and use a tool such as MailChimp or similar.

All our policies are available through our community forum, and linked from our main website (https://www.quickfile.co.uk).

I’ve posted a link above to the privacy policy, but for your convenience, you can find it here.


Hi Glen
Because we are a Data Controller who uses a Data Processor (you guys) the GDPR states that we must have a Controller to Processor agreement in place with you.

The below is from the ICO website. It means that each of your customers as the Data Controller must ask you to sign a Data Processing agreement - that could mean that you have 1000’s of differently worded contracts to go through. I work for a payment gateway and we are a processor for many controllers to that end we’ve put together the Data Processing Agreement as a “self-serve” document that all our customers can sign and return to us. It’s their responsibility but we are making compliance easy for them. A sub-processor is different - if you are using Sub-processors to process our data we, as the Controllers, need to agree to that sub-processing so you would lay it all out in the agreement too.

So that was the type of contract that I was looking for. Do you think that’s something you might put together or have maybe already? See below extract from the ICO. - Many thanks.

Whenever a controller uses a processor it needs to have a written contract in place.

The contract is important so that both parties understand their responsibilities and liabilities.

The GDPR sets out what needs to be included in the contract.

Controllers are liable for their compliance with the GDPR and must only appoint processors who can provide ‘sufficient guarantees’ that the requirements of the GDPR will be met and the rights of data subjects protected.

Processors must only act on the documented instructions of a controller. They will however have some direct responsibilities under the GDPR and may be subject to fines or other sanctions if they don’t comply.

The checklist of what the agreement must legally contain can be found here.


All the terms relating to our GDPR compliance are contained within our current privacy policy. Some companies have filed an addendum to their existing privacy statements, i.e. where they are operating in different jurisdictions and wish to append specific data processing terms affecting their customers based in Europe. We have instead completely rewritten our privacy policy from scratch to adhere to GDPR.

There is no requirement (to my knowledge) for a privacy statement to be signed, as long as the customer provides consent in a clear affirmative act.