How NativeRadar handles personal data.
1. What NativeRadar is
NativeRadar is a business service that records promotional articles published on news portals in Bosnia and Herzegovina and reports on them to publishers, agencies and advertisers. The operator named above is the data controller for the personal data described in this notice.
2. Personal data we process
Users of the service (people at client organisations and the operator's staff):
- Name, business email address, organisation and role
- A personal access link, stored only as a one-way hash, with its issue and expiry dates
- Access and activity records: time of access, pages used, questions asked to the analysis assistant, exports made
- IP address and browser information, recorded by our hosting providers in their standard access logs
Published content. NativeRadar reads publicly available articles on news portals. An article may contain the name of a journalist, a company representative or another person who appears in the text. We record the article's address, headline, text, publication time and the advertiser and brand behind it. We do not build profiles of individuals and we do not search for people. The data is organised by portal, advertiser, brand and category.
Business contacts. Names and business emails of people we deal with at publishers, agencies and advertisers, for the purpose of the business relationship.
3. Why and on what basis
| Purpose | Legal basis |
|---|---|
| Giving users access to the service and keeping it secure | Performance of the contract with the client organisation, and our legitimate interest in security |
| Recording promotional articles and reporting on the market | Legitimate interest in providing an independent market record. The articles are already public |
| Access and activity logs | Legitimate interest in security, support and billing |
| Business contact records | Legitimate interest in managing the relationship |
Where the Law on Personal Data Protection of Bosnia and Herzegovina or the EU General Data Protection Regulation applies to a person, the bases above are used in the sense of that law.
4. Who processes the data for us
- Supabase (database, authentication and server functions), hosted in the European Union
- Cloudflare (web hosting and content delivery)
- Google (fonts on public pages, and the AI model behind the analysis assistant, which receives the question and aggregated figures, never user identities)
- Email delivery providers, when we send service messages
These providers act under data processing agreements and process data only on our instructions. We do not sell personal data and we do not share it with advertisers or publishers in a form that identifies a user.
5. Where the data is kept and for how long
| Data | Retention |
|---|---|
| User account and access link | For the duration of the client relationship, then 90 days |
| Access and activity logs | 12 months |
| Recorded articles and reports | As long as the service operates. They form the market record |
| Business contact records | For the duration of the relationship, then 24 months |
Data is stored in the European Union. It is encrypted in transit and at rest. Access inside the service is limited by role, and every client sees only its own view of the market.
6. Your rights
You can ask us to confirm whether we hold personal data about you, to receive a copy, to correct it, to delete it, to restrict its use, or to object to processing based on our legitimate interest. Write to [PRIVACY EMAIL]. We answer within 30 days. If you think we handled your data wrongly, you can complain to the Personal Data Protection Agency of Bosnia and Herzegovina (azlp.ba) or, for people in the EU, to your national supervisory authority.
7. Cookies
NativeRadar uses no advertising or analytics cookies. The dashboard keeps a session token in your browser so that you stay signed in. It is removed when you sign out. Public pages set no cookies.
8. Changes
We will publish any material change to this notice on this page and, for users of the service, by a notice inside the dashboard at least 14 days before it takes effect.