data breach

[NotAllThere]

Are you tempted to do that without a solicitor?

If so, you might get asked all the same questions you have been asked here plus a lot more.

They might want a meeting just to give you a slapped wrist.

Or they might be on a fishing trip - anything you say could make matters worse.

If it's just to beat him up a bit and put the frighteners on him, then dragging a solicitor along is likely to prolong the agony. From the limited information so far supplied, I would
1. Seek legal advice
2. Meet with them to seek to resolve without going legal bearing in mind information arising from 1)

[LondonManc]

If it's just to beat him up a bit and put the frighteners on him, then dragging a solicitor along is likely to prolong the agony. From the limited information so far supplied, I would
1. Seek legal advice
2. Meet with them to seek to resolve without going legal bearing in mind information arising from 1)

For me it all depends on the documentation that he has sent and whether they want to set an example or not, especially in the light of other leaks.

[BrilloPad]

If it's just to beat him up a bit and put the frighteners on him, then dragging a solicitor along is likely to prolong the agony. From the limited information so far supplied, I would
1. Seek legal advice
2. Meet with them to seek to resolve without going legal bearing in mind information arising from 1)

I agree with all that. That question is do they want to give him a slapped wrist or do they want blood?

You've got to ask yourself if you feel lucky....

[NotAllThere]

Perhaps he's already met with the and the penance was to admit all on CUK... but surely no-one would be that cruel.

[psychocandy]

Dunno. I'd be tempted to go along and listen first. Try not to say too much or admit too much and be sorry. If the meeting starts going pear shaped you can always leave and say sorry I think I need legal representation.

BUT depends what was emailed and the environment. If its just some crap project dox that mean nothing to anyone else its a lot different to a system design doc from a defence project.

Im thinking if its low level stuff the client might be wanting to ensure this is all it was, have a bit of a rant etc. If so, then just say sorry and it might be the end of it.

Surely if you take a legal person along it immediately ups the stakes.

[VillageContractor]

I agree with all that. That question is do they want to give him a slapped wrist or do they want blood?

You've got to ask yourself if you feel lucky....

You have no idea what they want to do so surely the safest option would be to take a solicitor.

If they want to take you to court you risk making it worse by not being properly prepared.

Depending on the company, industry and type of data you stole will help make that decision.

If it was me I wouldn't have done it in in the first place and would have had insurance, but hey that's just me

[BrilloPad]

Perhaps he's already met with the and the penance was to admit all on CUK... but surely no-one would be that cruel.

Then the thread would have been started in general. I hope you would not be cruel enough to move it.....

[LondonManc]

Dunno. I'd be tempted to go along and listen first. Try not to say too much or admit too much and be sorry. If the meeting starts going pear shaped you can always leave and say sorry I think I need legal representation.

BUT depends what was emailed and the environment. If its just some crap project dox that mean nothing to anyone else its a lot different to a system design doc from a defence project.

Im thinking if its low level stuff the client might be wanting to ensure this is all it was, have a bit of a rant etc. If so, then just say sorry and it might be the end of it.

Surely if you take a legal person along it immediately ups the stakes.

Do you really think the client don't know what's been sent?

If it's project templates, then the OP's a bit dim for not simply seeing what's available on the web.

If it's coding/methodology then odds are it's intellectual property, which leads to corporate theft charges. Again, while it's not weapons secrets, you're potentially putting jobs at risk at your previous client if they are sent to a competitor.

If it's design documents rather than out and out code, then the same still applies.

[BrilloPad]

You have no idea what they want to do so surely the safest option would be to take a solicitor.

If they want to take you to court you risk making it worse by not being properly prepared.

Depending on the company, industry and type of data you stole will help make that decision.

If it was me I wouldn't have done it in in the first place and would have had insurance, but hey that's just me

The bit in bold is key.

Personally I would get legal advice first. Then go along, apologize, make it clear it has been deleted and that I had learnt my lesson.

I would consider going with a friend to take notes. Well, I would if I had any friends....

[WTFH]

Surely if you take a legal person along it immediately ups the stakes.

Yes it does, which is why you should take legal advice before meeting.

The OP needs to get someone to review the email/letter he has been sent, to look at the wording of his contract and to discuss exactly what information he took. AFTER that legal discussion, he will then be in a better place to decide what to do next.
Going to the client first then coming out looking for legal help, well he's then relying on remembering exactly what he said to them, what they said to him, etc.

A legal expert may look at the information and tell him to go in, say he's sorry and leave it at that. They may tell him he needs to suggest options that will keep the client happy. They will try to fill him in on the seriousness of the matter and perhaps bring a sense of perspective to the situation, something that none of us on here can do because we do not have all the details.

Being bullish or laisez-faire when it comes to legal problems can make it more difficult down the line, and while the response to naïveté on CUK may be harsh words and mickey taking, that's all they are. In the real world, the response to naïveté may not be as light.