Unser Kernprinzip ist, dass du kontrollieren kannst, welche Informationen (wenn überhaupt) du in unserem System mitteilen willst. Wir nehmen Privatsphäre sehr ernst.

Um das System anbieten zu können, müssen wir einige Infos wissen: Name, Kontaktdaten, Teamname, Basisinformation, Events/Zeitplan, Orte und Teilnahmedaten. Wir speichern diese Informationen auf unserer Datenbank. Die Daten werden nicht an Dritte weiter gegeben.

Cookies

Wir sammeln nicht persönlich identifizierbare Informationen über die Besucher um das System zu managen, verbessern und zu verfolgen. Die nicht persönliche identifizierbare Informationen können an Dritte, um zielgerechtere Werbung und Services anzuzeigen, gegeben werden.

Wir speichern die Informationen in "Cookies". Ein Cookie ist eine kleine Informationseinheit über den User, die auf dem Benutzer-Computer gespeichert wird. Wir benutzen Session ID Cookies um die Personal Präferenzen und Session Daten zu speichern. Standardmäßig benutzen wir Persistent Cookies (dauerhafte Cookies) die deine Login ID (aber kein Passwort), für bequemere wiedereinloggen, speichern.

Bitte beachte, dass wir Werbepartner (dritte Partei) es erlauben können, dass sie ihre Cookies auf deinem Computer speichern. Mit der Nutzung von unserem System stimmst du hier zu. Diese Cookies werden keine persönliche Daten die du uns mitteilst, enthalten. Die Cookie-Nutzung von den Werbepartnern liegt unten die Policys von den Werbepartner, nicht unten unser Privacy Policy(Datenschutzrichtlinie).


Data saved about a user

Individual data
NameDisplayed on team pages to enable attendance information, on member listings and event attendance responses.
PasswordBy default, a random generated password. Always stored as salted and hashed.
Facebook idFor those users, who utilize Facebook login.
Team nameList of the user's teams.
Previous loginShown to team mates, so they know the user to be active and alive.
Email addressThe user's address for the service's e-mails. Along with the address we save a date and ip address from which the user confirmed their email address.
Previous sent emailMetadata about the last time the email address was functional. If the receiving server informs there's something wrong with the address, no more email will be sent.
Phone numberThe user's number for the service's SMS. Along with the number we save a timestamp and ip address from which the user confirmed their phone number. When sending SMS from the service, the phone number will be known by the sending telco operator.
Previous sent smsMetadata about the last time the number was functional. If the sms-gateway informs there's something wrong with the number, no more messages will be sent.
Service data
Other data you providedResponses, messages, comments, and files, and how you selected their viewability (only team members or everyone).
Profile photosIf you add a profile photo, it will be shown on the team's public member list.

Cookies

Our cookies, 1st party
_session_idAnonymous random idMaintain an HTTP-session during a visit.1 hour
ref_trackAnonymous id and referral idIdentify links sending incoming traffic for statistical analysis and for fixing expired or changed links.5 years
user_remember_[0-9]+User id and encrypted idIdentifies user login and lets the user continue to team's pages without logging in again.6 months
ad_[0-9a-z-]+Number ja timestampThe number of banner impressions per browser. The number is used to restrict ad display.1 week
Google Analytics, 3rd party
_gaAnonymous random idIdentify a browser across visits.2 years
_gidAnonymous random id.Identify a browser across visits.1 day
_gatRestrict requests to analytics.1 minute
Social media, 3rd party
a11y, sb, datr, c_user, xs, wd, act, fr, presenceMultiple Facebook cookies, c.f. Facebook cookiesOn pages that include an FB widget. Identify a browser across visits for tracking the user or ad campaigns.4 days—2 years
Advertisement, 3rd party. For settings, please see Your Online Choices
IDE, DSID, NID, TAID, T, S, __gads, __gac, .. Multiple Google cookies, c.f. Google cookiesOn pages with ads. Identify a browser across visits for tracking ad campaigns.1 day—1,5 years
C, cid, uid, .. Multiple Adform cookies, c.f. Adform cookiesOn pages that include Adform ads. Identify a browser across visits for tracking ad campaigns.1—2 months