How does the UK data protection act fare with this user data collection?

On Wed, 10 May 2023 at 13:05, Glenn Adams <gl...@skynav.com> wrote:

> Hi Jocelin,
>
> Please send me your Jira user ID and a valid (preferred) email address.
> You can reply privately to me if you wish.
>
> Regards,
> Glenn
>
> On Wed, May 10, 2023 at 3:18 AM Jocelin HEINEN (ext)
> <jocelin.heinen.exter...@atos.net.invalid> wrote:
>
>> Hi,
>>
>> I have created a Jira issue.
>> My GitHub username: *JoHein*
>>
>> Thank you
>>
>> ------------------------------
>> *De :* Glenn Adams <gl...@skynav.com>
>> *Envoyé :* dimanche 7 mai 2023 06:19
>> *À :* FOP Users <fop-users@xmlgraphics.apache.org>; FOP Developers <
>> fop-...@xmlgraphics.apache.org>; Batik Developers <
>> batik-...@xmlgraphics.apache.org>; XML Graphics Project <
>> gene...@xmlgraphics.apache.org>
>> *Objet :* Requesting your GitHub User Identifier - For Jira Migration
>>
>> Caution: External email. Do not open attachments or click links, unless
>> this email comes from a known sender and you know the content is safe.
>>
>> Hi All,
>>
>> If you haven't yet heard, we are migrating the XMLGraphics project's
>> issue tracking from Jira to GitHub.
>>
>> For the purpose of performing the migration from Jira to GitHub Issues, I
>> would like to have your GitHub User Identifier if you have previously
>> interacted with the XMLGraphics Jira Projects in any way, e.g., creating a
>> Jira Issue, commenting on a Jira Issue, adding an attachment to a Jira
>> Issue, etc.
>>
>> Your Identifier will be used to add you as an assignee or refer to you
>> via a *mention* in GitHub issues that are created from the migration
>> process.
>>
>> Please send your Identifier in response to this email at your earliest
>> convenience. For your reference, my GitHub User Identifier is skynavga.
>> If you don't have a GitHub Identifier, then you can create a GitHub account
>> to create one. Or, if you don't wish to create a GitHub account, you can
>> let me know that as well, in which case the migration process will not link
>> migrated issues to you.
>>
>> Also, if you wish to avoid responding publicly, please send your response
>> directly to me at <gad...@apache.org>.
>>
>> Kind regards,
>> Glenn
>>
>> Ce message et toutes les pièces jointes (ci-après le "message") sont
>> établis à l’intention exclusive des destinataires désignés. Il contient des
>> informations confidentielles et pouvant être protégé par le secret
>> professionnel. Si vous recevez ce message par erreur, merci d'en avertir
>> immédiatement l'expéditeur et de détruire le message. Toute utilisation de
>> ce message non conforme à sa destination, toute diffusion ou toute
>> publication, totale ou partielle, est interdite, sauf autorisation expresse
>> de l’émetteur. L'internet ne garantissant pas l'intégrité de ce message
>> lors de son acheminement, Atos (et ses filiales) décline(nt) toute
>> responsabilité au titre de son contenu. Bien que ce message ait fait
>> l’objet d’un traitement anti-virus lors de son envoi, l’émetteur ne peut
>> garantir l’absence totale de logiciels malveillants dans son contenu et ne
>> pourrait être tenu pour responsable des dommages engendrés par la
>> transmission de l’un d’eux.
>>
>> This message and any attachments (the "message") are intended solely for
>> the addressee(s). It contains confidential information, that may be
>> privileged. If you receive this message in error, please notify the sender
>> immediately and delete the message. Any use of the message in violation of
>> its purpose, any dissemination or disclosure, either wholly or partially is
>> strictly prohibited, unless it has been explicitly authorized by the
>> sender. As its integrity cannot be secured on the internet, Atos and its
>> subsidiaries decline any liability for the content of this message.
>> Although the sender endeavors to maintain a computer virus-free network,
>> the sender does not warrant that this transmission is virus-free and will
>> not be liable for any damages resulting from any virus transmitted.
>>
>

-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

Reply via email to