[TYPO3-ect] partner management extension
Dr. Ronald P. Steiner
Ronald.Steiner at googlemail.com
Sat Aug 16 22:38:01 CEST 2008
Hi Bernd,
thanks for your comment. Can you recommend any link that explains the
details of this law and how to deal with it?
As far as I observe most companies store the data of their customers. So
when you order again, they already have your address, bank account, know
what you bought in previous orders and if you payed the bill. - is this
illegal according to German law?
greetings
Ron
bernd wilke schrieb:
> on Sat, 16 Aug 2008 13:03:58 +0200, Dr. Ronald P. Steiner wrote:
>
>> Hi Oliver,
>>
>> thanks for your tip.
>> If I see correctly the remove duplicates option of "dublefinder" only
>> adds the categories of all entries to the one preserved, but not the
>> other information to this person.
>> In my case there might be quite a lot of information to the person
>> stored in tt_address. Then the person signs in for fe_users. Now all the
>> information already stored in tt_address for this person has to be
>> transfered / associated to / with fe_users. ... what if the person
>> cancels his fe_users account?
>> Necessary would be a more automatic procedure. There should be a way to
>> avoid double entries from the start and not always check for duplicates
>> and then remove them.
>
> you might keep in mind the local laws.
> in germany (nice to talk in english between germans ;-) ) you are not
> allowed to mix/merge the different datarecords until the user gives you
> explicit allowance. And for newsletter-subscription a minimum of data has
> to be sufficient. Therefore a newsletter subscription must be possible
> with only an email-address and you are not allowed to check about
> additional data (name, city, preferences, ...) from other data. [1]
>
> that might be a little less comfort for login-users, but enables a
> clearer separation. your example: deleting a login, but staying in the
> newsletter.
>
> you might mix these records in one table (fe_user) having unique email-
> addresses (additional index key) storing the records for login and pure
> newsletter in differnt pages. then you have to define behaviour on
> deleting login-records.
> But keep in mind about 'deleted' records: records deleted within TYPO3
> are not deleted in mySQL. In this way a 'deleted' record can block a new
> subscription as an email-address is present alas no active record is
> available. Again the german laws: you are not allowed to hold these data.
> these Records have to be deleted completely, so no reconstruction is
> possible. [1]
>
> BTW: in the same way no google-analytics (or similar) is allowed as long
> as the user is not informed in a noticable way about the complete storing
> [1]
>
>
> [1] does anybody really care about these laws?
>
> bernd
More information about the TYPO3-team-extension-coordination
mailing list