Privacy information
What we process and why.
Last updated: 17 November 2026.
Who is responsible
The data controller is Axel Ryttberg Grönqvist in Sweden, the sole owner and operator of TrendFalcon. Questions and requests: contact@trendfalcon.se. No login is needed to make a request.
Information and purposes
- Private account and sessions: email address, account ID, sign-in sessions and password-reset requests support access to the private workspace. Basis: legitimate interest in operating and securing the service (GDPR Article 6(1)(f)).
- Workspace notes and watchlists: information entered by authorised users supports their research. Basis: legitimate interest.
- Contact emails: your address and message are used to answer enquiries and handle requests. Basis: legitimate interest, or a legal obligation when handling privacy requests (Article 6(1)(c)).
- Early-access list: if you join it on one of our pages, your email address and the time you joined are stored, only to tell you about early access. Basis: your consent (Article 6(1)(a)), which you can withdraw at any time by emailing us.
- Hosting and security logs: providers may process IP addresses, request details and timestamps to deliver and protect the service. Basis: legitimate interest.
- Waitlist abuse prevention: To prevent abuse of the waitlist, we keep a hashed form of your network address for up to 3 hours. It is not linked to your email address. Basis: legitimate interest.
- Aggregate trend observations: Wikipedia article pageviews, search terms, Pinterest keywords and interest histories, hashtag names, ranks and counts support trend research. If a term identifies a person, it can still be personal data despite being public or appearing in an aggregate feed. Such information is handled under legitimate interest in trend research.
Business contacts and customers
We may contact businesses about our research service, and businesses may contact us. This section covers the personal data of people at those businesses: a named contact at a prospective customer and, if a business becomes a customer, the contact person and billing details of that customer. It does not cover visitors who only read this site.
What we process. If we contact a business, or a business contacts us: the company name, the contact person's name, work email address, work phone number or business profile, job role, where we found the contact, the date of first contact, any reply, and whether the person has asked us to stop. If a business becomes a customer: the same, plus order details, invoices and payment records.
Where it comes from. From the person or the company itself (a reply, an order, a form), or from public business sources such as the company's own website, public company registers and public business profiles. We do not buy contact lists and we do not collect contact details automatically.
Why, and on what basis, if and when it applies.
- To contact a business about our research service and to follow up on the reply: legitimate interest (GDPR Article 6(1)(f)). We balance this against your interests, contact only business addresses and say how to stop.
- To make an agreement with a business and deliver the research file: performance of a contract (Article 6(1)(b)).
- To keep invoices and accounting records: legal obligation (Article 6(1)(c)), under the Swedish Bookkeeping Act.
First contact. Any first message we send says who we are, why we write, where we found the contact details and how to stop further contact. You can object to this use at any time, without giving a reason. We then stop at once and keep only the company name and the date of your objection so that you are not contacted again.
How long we keep it. We delete a prospect's personal details 12 months after the last contact, unless the person becomes a customer. If a business becomes a customer, invoices and accounting records are kept for seven years, as the law requires. If you object, we keep only the company name and the date of the objection.
No automated decisions. We do not use this data for automated decisions about you or for profiling.
Your rights. You can request access, correction, deletion or restriction, object to processing based on legitimate interest, and ask for a copy of your data where the law gives you that right. Email contact@trendfalcon.se. Requests are handled by hand, normally within one month. You can also complain to the Swedish Authority for Privacy Protection (IMY), www.imy.se.
The public demo and browser storage
The demo requires no account. Saved example items are stored locally in your browser, separately from private research records. They are not sent to the workspace. You can remove them by unsaving the items or clearing this site's browser storage. Clearing storage also removes local preferences and sign-in state.
The private workspace uses browser storage for sessions and screen preferences. The site's own code does not add advertising or analytics cookies. Remote fonts require requests to Google, which can receive your IP address and request information.
Service providers
- Lovable hosts the website and backend. Supabase provides the workspace database and authentication services.
- STRATO provides the contact mailbox.
- Public trend data is collected on our UpCloud server and stored in Supabase.
- Google Fonts receives requests for the fonts used on the public pages and demo.
- Google provides the YouTube API Services used to read public video information (see below).
We do not sell personal data or share it with advertisers. Demo ideas are prewritten; using the demo does not send your shortlist to an AI provider.
YouTube API Services
TrendFalcon uses YouTube API Services. Google's use of information is described in the Google Privacy Policy. Through the YouTube API we read public video information: titles, descriptions, links and counters. We do not collect information about viewers or about YouTube users' accounts, and we do not ask visitors to connect a YouTube account. YouTube-derived data is kept for at most 28 days from the time it was observed; see "What is stored and for how long" below.
Storage locations and transfers
The exact hosting regions of the collection server and workspace database have not yet been confirmed for this notice. Providers or their subprocessors may process data outside the EU/EEA. Provider locations and transfer arrangements are still being reviewed; we do not claim that all processing stays in the EU or that this review is complete.
What is stored and for how long
- Account (email address, account ID, sign-in sessions): kept while the account exists and removed by the operator on request.
- Early-access list (email address, time joined): kept until you ask to be removed or the list is no longer needed, then deleted by the operator.
- Notes and watchlists: kept until the author or the operator removes them, or the workspace is deleted.
- Collected trend evidence (the source, the title, search term or hashtag, a link, counts and ranks, the market or language it applies to, when it was observed, and the receipt that records each collection): kept for as long as the workspace exists, so that histories can be compared over time. No automatic deletion has been configured for these yet.
- YouTube-derived data (video titles, descriptions, links and counters obtained through the YouTube API, and records derived from them, such as receipts and topics named after a video title): kept for at most 28 days from the time it was observed. YouTube information is not offered in the public demo. We are verifying deletion controls before making it available to customers.
- Upload credentials: only a one-way hash of each upload key is stored in the database, never the key itself.
- Collection server: its queue of delivered upload batches is cleared 7 days after delivery. Other working files there, such as settings, access-token caches and manual exports, stay until the operator removes them. The operator's own computer may hold the same kinds of working files, including local YouTube working copies, which are deleted by hand once they pass 28 days.
- Hosting and security logs, and provider backups: kept by the providers under their own schedules, which we have not verified.
Retention and deletion
Apart from the 28-day limit for YouTube-derived data and the limit of up to 3 hours for the hashed network address kept to prevent abuse of the waitlist, no fixed retention schedule or automatic deletion has been configured for records in the workspace database; other records are removed manually by the operator, including when handling an applicable deletion request. Copies may also exist on the collection server and in provider backups. We are reviewing retention by data category; this page does not promise immediate removal from backups or a retention period that has not been implemented.
Your rights
You can request access, correction, deletion or restriction, object to processing based on legitimate interest, and request portability where applicable. Email contact@trendfalcon.se. Requests are handled manually, normally within one month. You may also complain to the Swedish Authority for Privacy Protection, IMY.