Privacy Policy: changes from version 0.0-placeholder to 1.0.0
Summary of the changes
First approved version. Puraderi AB approved the text. It is draft 0.7.0 without the draft notice, and the backups are stored at Backblaze in the Netherlands, with another provider than the hosting; servers and storage are in Germany only.
135 passages added, 1 removed and 1 changed.
Privacy Policy[removed: (placeholder)]
[added: 1. About this policy]
[added: 1.1 Who the policy applies to]
[added: This policy explains how we process personal data when you]
[added: 1. use a Kungora account for an organisation;]
[added: 2. visit kungora.com or a newsroom in the service, on our domain or on an organisation’s own domain;]
[added: 3. follow a newsroom or subscribe to news;]
[added: 4. have a journalist account;]
[added: 5. report content or complain about a decision on content; or]
[added: 6. contact us, for example to exercise your rights under the General Data Protection Regulation.]
[added: 1.2 Contacts and journalists]
[added: If you are on an organisation’s contact list, receive email from an organisation through the service, are a press contact or are named in a publication, specific information is in the Privacy Notice for Contacts and Journalists /legal/privacy-contacts-journalists.]
[added: 1.3 When an organisation is responsible]
[added: When organisations use the service for their own contact lists and sends, we process the data on their behalf, as a processor. The organisation is then the controller, and its privacy policy applies to that processing.]
[added: 2. Controller and data protection officer]
[added: The controller is Puraderi AB, organisation number 559435-0257, c/o Primepack, Orrekulla Industrigata 55B, 425 36 Hisings Kärra (“we”, “us”). Our data protection officer can be reached at dpo@kungora.com. Write there if you have questions about how we process personal data or want to exercise your rights.]
[added: 3. Personal data we process]
[added: 3.1 Users of organisation accounts]
[added: Name, email address, password (stored only as a salted hash), two-factor authentication details and passkeys, chosen language, role and which organisation you belong to. We also record which terms you have accepted, when and from which IP address, verification evidence linking the organisation to a domain, notification settings and what is done with the account, for example sign-ins, publications, exports and changed settings. If you authorise an import of your organisation’s content from another service, we record your email address and a shortened IP address as evidence of the authorisation.]
[added: 3.2 Visitors]
[added: We use no cookies on the public website or in the newsrooms and store no IP address in the visitor statistics. To count visits, we form a hash of the IP address and the browser’s identification, and a hash of the network part of the IP address without the browser’s identification, each together with a random value that changes every day and is deleted the day after. After that, the hashes cannot be linked to anyone. The hash of the network part is used so that a referring website is named only when visitors from several networks came from it. We also record which page was shown, where the visitor came from (as a category and a domain), the type of device and the country. The statistics are not sent if your browser signals that you do not want to be tracked (Do Not Track or Global Privacy Control). Our servers write an access log in which the IP address is shortened before anything is stored. When unusually many visits to a newsroom come from one network in a day, the application log records that network (the shortened IP address), not the full address. Video and audio players that organisations embed from other providers are described in clause 6.6.]
[added: 3.3 Followers and subscribers]
[added: Email address, name if you give it, language, whether you have said you are a journalist and, if so, which outlet, what you follow or subscribe to and how often you want email. As proof of your consent we record which text you accepted, when you signed up and confirmed, a shortened IP address and the browser’s identification. We also record which emails we have sent you and whether they were delivered.]
[added: 3.4 Journalist accounts]
[added: In addition to the data in clauses 3.1 and 3.3: the outlet you work for, title, beats, regions, languages and whether your email address is issued by an employer or is private.]
[added: 3.5 Notices and complaints]
[added: If you report content: your name and email address (except for anonymous reports of child sexual abuse material), your explanation, the address of the content, the reason and whether you report as a trusted flagger. If you complain about a decision: your explanation and which decision the complaint concerns.]
[added: If you often submit manifestly unfounded notices, we record the warning we give you and, if it continues, our decision not to process notices from your email address for a set period: the notice it concerns, what was manifestly unfounded, when, and until when (Digital Services Act, article 23(2); see the Content Policy /legal/content-policy#c-10-7). We email you both.]
[added: 3.6 Contact with us]
[added: When you email us or exercise your rights: what you write, your email address and the data needed to check your identity and answer the request.]
[added: 3.7 People in published content]
[added: Press contacts, quoted people and others named in publications are covered by the Privacy Notice for Contacts and Journalists /legal/privacy-contacts-journalists.]
[added: 3.8 Requests for access to an organisation's account]
[added: If you try to register an organisation that already has an account and ask for access: the name and email address you typed (or, if you are signed in, your account's own), the organisation and what became of the request. We send the name and address to the account's owner and administrators, who invite you or dismiss the request. We have not checked that you own the address or belong to the organisation. When support changes the email address of an account for its user, we also keep the new address and a hash of the confirmation link, and who asked.]
[added: 4. Why we process the data and on what basis]
| [added: Purpose] | [added: Data] | [added: Legal basis] |
|---|---|---|
| [added: Providing the service to the organisation you represent: account, sign-in, publishing, email] | [added: 3.1] | [added: Legitimate interest: performing the agreement with the organisation] |
| [added: Showing that terms have been accepted] | [added: 3.1] | [added: Legitimate interest: being able to show what was agreed] |
| [added: Verifying organisations and preventing fraud and misuse] | [added: 3.1] | [added: Legitimate interest] |
| [added: Sending messages about the service, for example security notices and changed terms] | [added: 3.1, 3.4] | [added: Legitimate interest; for journalist accounts, contract] |
| [added: Counting visits and showing statistics without cookies] | [added: 3.2] | [added: Legitimate interest] |
| [added: Sending publications from newsrooms you follow and news you subscribe to] | [added: 3.3] | [added: Consent] |
| [added: Showing the organisation you follow who follows it] | [added: 3.3] | [added: Legitimate interest, see clause 5.1] |
| [added: Being able to show that you consented and when you stopped] | [added: 3.3] | [added: Legitimate interest and legal obligation] |
| [added: Journalist account: follows, saved searches and alerts] | [added: 3.4] | [added: Contract] |
| [added: Handling notices and complaints under the Digital Services Act] | [added: 3.5] | [added: Legal obligation] |
| [added: Warning, and for a period not processing notices from, people who often submit manifestly unfounded notices] | [added: 3.5] | [added: Legal obligation] |
| [added: Informing the police of suspected serious crimes] | [added: 3.5] | [added: Legal obligation] |
| [added: Answering questions and handling requests under the General Data Protection Regulation] | [added: 3.6] | [added: Legal obligation; otherwise legitimate interest] |
| [added: Respecting unsubscribes and erasure in the future] | [added: 3.3, 3.6] | [added: Legal obligation and legitimate interest] |
| [added: Passing on a request for access to the account's owner and administrators, and changing an account's email address when support helps its user] | [added: 3.8] | [added: Legitimate interest: helping people reach an account they are entitled to] |
| [added: Information security, troubleshooting and the audit log] | [added: 3.1, 3.2] | [added: Legitimate interest and legal obligation] |
| [added: Establishing, exercising or defending legal claims] | [added: All] | [added: Legitimate interest] |
[added: Where we rely on legitimate interest, we have carried out a balancing test. You can get a summary of it by emailing dpo@kungora.com.]
[added: 5. What organisations see about you]
[added: 5.1 Followers]
[added: When you follow a newsroom, the organisation that owns it sees your name, your email address, your language and whether you have said you are a journalist. We tell you this when you sign up. The organisation may use the data only to understand and manage its audience in the service, under our Customer Terms /legal/customer-terms#c-11-3. You can stop following at any time.]
[added: 5.2 Subscribers and statistics]
[added: If you subscribe to news about a subject, a region or a search, the organisations see only totals, not who you are. Visitor statistics are shown to organisations in aggregate, with the visitor’s country as the most detailed location.]
[added: 5.3 Opens and clicks]
[added: For followers and subscribers we report only totals of opens and clicks. Organisations can see opens and clicks per recipient only for their own contacts, and the email footer then says so.]
[added: 6. Who we disclose data to]
[added: 6.1 Processors]
[added: We use suppliers for hosting, storage and email delivery. They process the data on our behalf and under our instructions. The current list is on the Sub-processors /legal/subprocessors page.]
[added: 6.2 Organisations in the service]
[added: Followers are shown to the organisation they follow, see clause 5.1. People who report content are not identified to the organisation whose content is reported, unless the law requires otherwise.]
[added: 6.3 Group companies and company data]
[added: Published content and data about organisations are used in a company-information service that we or a group company operate. Data about you under clause 3 is not part of what is provided there. If we want to change that in the future, we will tell you in advance.]
[added: 6.4 Authorities and courts]
[added: We disclose data when required by law or by a decision of an authority, for example to the Swedish Police Authority if we suspect a crime that threatens someone’s life or safety.]
[added: 6.5 On a transfer of the business]
[added: If our business is transferred in whole or in part, the data may be transferred to the new owner, who then becomes responsible on the same terms.]
[added: 6.6 Embedded players]
[added: If a publication contains a video or audio player from YouTube, Vimeo, Dailymotion or SoundCloud, your browser loads nothing from that provider when the page is shown. You see a panel with a play button that we show ourselves instead. Only when you click the button does your browser load the player from the provider. The provider then receives your IP address and details about your browser, and may store or read information in your browser under its own terms. If you do not click, the provider receives nothing. See clause 5.1 of the Cookie Policy /legal/cookie-policy#c-5-1.]
[added: 7. Transfers outside the EU and EEA]
[added: Our servers and storage are at Hetzner in Germany. Encrypted backups are stored at Backblaze in the Netherlands, provided by Backblaze, Inc. in the United States, which is certified under the EU-U.S. Data Privacy Framework. Email is sent through Amazon Simple Email Service in the AWS Stockholm region (eu-north-1), provided by Amazon Web Services EMEA SARL in Luxembourg. Because the supplier belongs to a US group, data may become accessible from the United States, for example during support or at the request of US authorities. For this we have entered into the European Commission’s standard contractual clauses (Implementing Decision (EU) 2021/914) and assessed the risks of the transfer. You can get a copy of the safeguards by emailing dpo@kungora.com.]
[added: 8. How long we keep the data]
| [added: Data] | [added: How long] |
|---|---|
| [added: User account] | [added: As long as the account exists. When the organisation’s account has been closed, user data is deleted after 30 days.] |
| [added: Sign-ins (IP address and browser)] | [added: Deleted when you sign out; otherwise 30 days after the sign-in expired (a sign-in lasts at most 7 days after its last use)] |
| [added: Acceptances of terms] | [added: As long as the agreement applies and thereafter for as long as claims can be made against us, at most ten years. After you have deleted your account, linked only to a hash of your email address (9.4).] |
| [added: Verification evidence and answers from the Companies Registration Office] | [added: 12 months, or longer while the verification it supports is in force (for example the proof of a domain that is still verified, or the document the organisation's verification rests on). The proof of a verified domain is renewed every month.] |
| [added: Evidence that you authorised an import of content (email address and shortened IP address)] | [added: 3 years after the authorisation] |
| [added: Audit log] | [added: 12 months] |
| [added: Backups] | [added: 30 days] |
| [added: Server access log and application log, with shortened IP address] | [added: 14 days] |
| [added: Individual page views in the visitor statistics, without IP address] | [added: 30 days, then only aggregated statistics. The day’s random value is deleted the day after.] |
| [added: Visitor country for the newsroom’s visitor map] | [added: The last 1,000 visits, at most 30 days] |
| [added: Unconfirmed follows and subscriptions] | [added: 7 days] |
| [added: Follows and subscriptions] | [added: As long as they continue] |
| [added: Ended follows and subscriptions, with proof of consent] | [added: 3 years after they ended. Deleted earlier if you delete your data or your account (9.4).] |
| [added: Records of delivered emails and digests] | [added: 13 months] |
| [added: Opens and clicks per email] | [added: 13 months, then only totals] |
| [added: Sign-in links to the email preferences] | [added: At most one day; a sign-in lasts at most one hour at a time] |
| [added: Files from “Download my data”] | [added: 7 days] |
| [added: Suppression list of unsubscribed and erased addresses, as a hash only] | [added: Until further notice, so that the address is not contacted again] |
| [added: Journalist profile] | [added: As long as the journalist account exists] |
| [added: Notifiers’ names, email addresses and explanations] | [added: 12 months after the decision on the notice, then anonymised; the email address in the notice on which we based a decision not to process notices from that address is kept until the decision ends, at most six months longer] |
| [added: Warnings to and decisions not to process notices from notifiers] | [added: 12 months] |
| [added: Explanations in complaints] | [added: 12 months after the decision on the complaint, then anonymised] |
| [added: Statements of reasons for our decisions on content (the facts and the name of what the decision was about)] | [added: 18 months after the decision, then the facts and the name are removed; the kind of decision, the ground and the dates stay for our transparency reports] |
| [added: Results of our automated checks of content] | [added: 24 months, for our yearly transparency report; for drafts only the rule and the reason are kept, not what matched] |
| [added: Records of requests under the General Data Protection Regulation (your address only as a hash)] | [added: 12 months after the request was closed; our email correspondence with you is kept as stated for emails to us] |
| [added: Emails to us (support, Digital Services Act, security and data protection)] | [added: 24 months after the last message in the conversation; emails asking to unsubscribe 30 days after the unsubscribe has been applied] |
| [added: Exports you requested under the General Data Protection Regulation] | [added: 30 days] |
| [added: Requests for access to an organisation's account (name and email address as typed)] | [added: 30 days after the request, answered or not; deleted at once if you erase your data (9.4)] |
| [added: New email address and link hash when support changes an account's address] | [added: 30 days after the request] |
[added: Data needed to establish, exercise or defend legal claims, or that we must keep by law, is kept longer where required.]
[added: 9. Your rights]
[added: 9.1 The rights]
[added: You have the right to]
[added: 1. know what data we hold about you and get a copy (access);]
[added: 2. have inaccurate data rectified;]
[added: 3. have data erased when it is no longer needed or when you withdraw consent or object;]
[added: 4. ask for processing to be restricted;]
[added: 5. receive data you have given us in a machine-readable format (data portability);]
[added: 6. object to processing based on legitimate interest, and always to direct marketing; and]
[added: 7. withdraw a consent at any time, without affecting processing that took place before.]
[added: 9.2 How to exercise the rights]
[added: Followers and subscribers can stop following, change subscriptions, download their data and erase it themselves through the “Email preferences” link in every email. Users of organisation accounts and journalists can change their details and delete their account themselves in the account settings. Deleting the account also erases the data about your email address, as “Email preferences” does (9.4). If you are the owner of an organisation’s account, first transfer the ownership or close the organisation’s account. In other cases, or if you prefer, email dpo@kungora.com.]
[added: 9.3 Handling]
[added: We answer within one month. If the request is complex or we receive many requests, the period may be extended by two further months; we then tell you within the first month. We may need to check your identity, usually by asking you to confirm through the email address the request concerns. It is free of charge.]
[added: 9.4 After erasure]
[added: When we erase your email address, we keep a hash of it on our suppression list so that the address cannot be added and contacted again by mistake. The hash cannot be turned back into the address. If you later create a new account with the same address and confirm it, the hash is removed when you first follow a newsroom or save a search with that account, since that is a new choice of your own. After that, organisations can again add the address to their own contact lists, under their own responsibility as described in 9.5, because the block no longer exists; a hash that still has a records hold waiting stays until the hold is released. When you delete your account, we also keep your acceptances of our terms, linked only to that hash, for as long as stated in 8; the records of your follows and saved searches, and of the consents you gave for them, are deleted with them, as are requests for access that you made with the address (3.8).]
[added: 9.5 Data organisations are responsible for]
[added: If the request concerns data an organisation is responsible for, for example its contact lists, we forward the request to the organisations concerned. They are the controllers of their lists and answer the request themselves, and we help them do so.]
[added: 10. Automated decisions]
[added: We make no decisions based solely on automated processing that have legal effects for you or similarly significantly affect you. Automated checks of content may hold a publication for review; a person then decides. They may also stop a publication that matches a blocking rule, for example a link through a URL shortener; the organisation can then change the content or ask us to review the block.]
[added: 11. Security]
[added: We protect the data with technical and organisational measures described in our Security Policy /legal/security-policy.]
[added: 12. Cookies]
[added: We only use cookies that are necessary for you to sign in and manage your email preferences, see the Cookie Policy /cookies.]
[added: 13. Complaints]
[added: If you think we process your personal data incorrectly, you can contact us at dpo@kungora.com. You also have the right to lodge a complaint with the Swedish Authority for Privacy Protection (Integritetsskyddsmyndigheten, IMY), Box 8114, 104 20 Stockholm, Sweden, www.imy.se https://www.imy.se.]
[added: 14. Changes]
[removed: This is a placeholder for development and testing. It is not a legal text and does not form an agreement. The final text is published as a new version before launch.]
[added: We may change the policy. The current version is always on this page together with earlier versions. For significant changes we notify you in advance by email or in the service.]