Privacy

Predictly is operated by a private individual, not a company. That individual is the controller for the personal data described here and can be reached at predictly.contact@gmail.com, which is the address for every privacy question and every request to exercise the rights below.

Asking for a forecast requires a free account, created with Google or with an email address and password. The account is how Predictly keeps the service to real people and how your saved forecasts stay yours.

Signing in does not mean everything you ask is kept against your name. A forecast is stored in your account only if you choose to save it; nothing is saved to your account automatically.

Account data

Your email address, and either a password — stored by the sign-in service as a hash, never in readable form — or an identifier from Google if you sign in that way, plus the language the site is shown to you in. Used to provide your account. Basis: performance of the contract.

Saved forecasts

For each forecast you choose to save: the question, the answer, the confidence level, an internal calibration figure, the written forecast and reasoning, the factors on each side, the resolution note, and the time. Linked to your account and visible only to you. Basis: performance of the contract.

Questions you ask

Sent to the language model that answers them. So that the same question gets the same answer, the question and its forecast are also kept in a shared cache that is not linked to you or to any account; a cached answer is reused for a few hours and replaced when the question is asked again. Basis: performance of the contract.

Technical data

Ordinary connection data such as IP address, browser type and timestamps, processed by the hosting platform when it serves a page, and error details where the platform reports them. Basis: legitimate interest in running and securing the service.

Predictly uses no analytics service, no advertising, no tracking pixels and no behavioural profiling, and does not use your questions or forecasts to train AI models.

A saved forecast is stored against your account and can be traced back to you. If you ask something you would not want associated with your email address, do not save it — or delete it afterwards, which you can do yourself at any time.

Predictly requests only the information Google’s standard sign-in provides: your email address and basic profile identifiers. It does not request access to Gmail, Drive, Contacts, Calendar or any other Google service. Google’s own handling of your sign-in is governed by Google’s privacy policy.

The request sent to the language model contains your question, today’s date, and a short category hint if one was supplied.

• It does not include your account identifier, email address, session token or IP address. The request is made from Predictly's server, not from your browser.
• It does not include previous questions or saved history. Each request stands alone.
• To research your question, Predictly's server sends search terms describing the event (the teams, company or subject involved — not your account or your exact wording) to Google News and to Wikipedia's API, and asks Google's Gemini API to search Google for current reporting. Gemini handles requests under Google's own terms; Predictly cannot verify what Google does with them.
• The credential used to reach the model stays on the server and is never sent to your browser.

A result lists the articles used. Following a link takes your browser to that site, and its own privacy policy applies there.

If your question itself contains personal information, that text is sent to the model, because the question is what is being answered.

Predictly has no public forecast pages, profiles or feed. The Share button copies the forecast text to your clipboard or opens your device’s share sheet. Nothing about your account is included, and where the text goes next is your choice.

Predictly uses no analytics or advertising trackers. It keeps the following in your browser, all strictly necessary for the service to work as you asked:

Language

One cookie that remembers which language the site is shown in, so every page — including the one you return to after signing in with Google — opens in it. Kept for a year.

Sign-in session

A session token in local storage so you stay signed in. It is removed when you sign out.

Scroll position

A single session-storage entry that remembers where you were on a page, so going back returns you to the same place. It contains no identifier and is cleared when you close the tab.

Pending question

A session-storage entry set while a question waits for you to sign in, so it can be picked up afterwards. Cleared as soon as the question runs, or when you close the tab.

Because these are strictly necessary for a service you requested, no consent banner is shown. If non-essential tracking is ever added, your consent will be asked for before it loads. Choosing Continue with Google takes you to Google’s own site, where Google’s cookies apply.

These services process data on Predictly’s behalf or as part of the platform it runs on. None of them receives your data for marketing purposes.

Several of these services are based outside the European Economic Area, including in the United States, so your data may be processed there. These providers set out their transfer safeguards in their own data-processing terms — for example, Lovable’s Data Processing Agreement.

• Saved forecasts: until you delete them or delete your account. There is no automatic expiry.
• Account data: until you delete your account.
• The shared cache: each entry holds a question and its forecast, linked to no account, and is replaced when the same question is asked again. The hosting and AI providers may keep request logs under their own retention policies.
• Technical and error logs: kept by the hosting platform under its own retention policy.

Passwords are stored as hashes. Traffic is served over HTTPS. Saved forecasts are protected at the database level: every read and write is checked against the account in a verified sign-in token, so one account cannot reach another’s forecasts. No system is perfect, and this describes the measures in place rather than a guarantee.

You can ask for access to your data, correction, erasure, restriction of processing and portability, and you can object to processing based on legitimate interests. Depending on where you live, local law may give you similar rights; the same address handles those requests.

On the Your forecasts page you can delete any saved forecast or all of them at once. To delete the account itself, write to predictly.contact@gmail.com; it will be removed, with everything in it, within one month. Other requests go to the same address and are answered within one month.

If you are in the European Union you can complain to your data protection authority — in France, the CNIL (cnil.fr).

Predictly is intended for people aged 16 and over, as set out in the Terms.

If the way Predictly handles data changes, this page will be updated and the date at the top will change. If anything here does not match how the product behaves, please tell us at predictly.contact@gmail.com.