Privacy Policy
This Privacy Policy explains how UpGate handles personal information when you use the website at upgate.online, including accounts, trials, subscriptions, APIs, dashboards, pilots, support, and the news and information products. It also explains how a person who is only named in a news item is different from a customer. The English page is https://upgate.online/privacy-policy and the Persian page is https://upgate.online/fa/privacy-policy. They describe the same practices.
1. Scope
This policy covers visitors, people who write to us, and customers who open an account or use an API key. It also describes news processing, because public reporting can name individuals who are not customers.
It does not control third-party sites, publishers, payment pages, or sign-in services that you choose to open. Those services have their own notices.
The Terms and Conditions are a separate agreement about use of the service. They say that UpGate keeps user information confidential and discloses it where law requires. This policy is the fuller description of the operational handling of personal information, including the providers that run the service. We do not publish your account contact details as a public directory, and we do not sell them as a marketing list.
2. Who operates the service
The service is operated under the name UpGate, the service provider named in the Terms and Conditions. This website does not publish a registered company name, company number, or registered-office address. The contact region printed in the footer is UAE · MENA. That label is a published contact region. It is not a statement that every server or record is located there.
Where a privacy law uses the words “data controller” or an equivalent term, privacy requests about this service can be sent to the operator at the contacts in section 19. We do not name a separate privacy office, because the website does not publish one.
3. Categories of personal information
What we hold depends on what you use. We may hold: your name, email address, phone number, and company or publication name when a form asks for them (including trial signup, checkout, and pilot or demo requests); account credentials, with the password stored using Django’s password hashing rather than as plain text; API keys issued to the account; display preferences you set, such as language, timezone, calendar, and digit style; and a country code saved at first signup from the Cloudflare CF-IPCountry header when that header is present. That country code is not updated on later logins.
If you sign in with Google or GitHub, we store the provider, the provider account identifier, the email address returned for that sign-in, and the link data needed to recognize the account.
For a subscription we store the plan, order references, whether and when the terms were accepted, and the payment status and references returned for that order. Checkout forms on this site collect contact details. Card or wallet details, where a payment method collects them, are collected by the payment provider. The payment record can include the provider payload returned for that transaction.
API request logs can include the request IP address and user agent. Trial signup uses the request IP address and email as short-lived rate-limit counters: the IP counter is kept for one hour and the email counter for 24 hours.
We also process the content of messages you send to [email protected] or type into the website chat on pages where that chat is shown.
News items are a different category. They can contain names, organizations, and events because the source reported them. They are not your account profile. Section 6 and section 15 explain that material.
Account forms do not ask for special-category information such as health data or biometrics. A news source may still mention sensitive topics. That comes from the source, not from an account form.
4. Sources and how information is collected
You give us information when you submit a form, create or update an account, pay, or write to us.
The browser and the network path supply technical data, including cookies and, when the request includes it, the Cloudflare country header.
Google or GitHub supply the sign-in identifiers if you choose those options. A payment provider supplies the status of a payment you start.
News is collected from RSS feeds, from publisher or site APIs, and from web pages collected by scrapers. Which sources run, and how many items are taken, changes over time. Support for a collection method does not mean every source is fetched every day, or that every item is enriched.
Further text and fields are then produced by UpGate’s own processing, described in section 6. UpGate also publishes its own website and blog editorial. That original writing is separate from third-party source items.
5. Purposes
We use account and contact information to open and run trials, accounts, subscriptions, dashboards, and API access; to send service email from [email protected]; to authenticate you; to keep API keys confidential to the account; and to answer support, pilot, and demo requests.
We use technical data to remember your language and cookie choice, to keep signed-in sessions, to rate-limit abuse, and to investigate misuse.
On the marketing pages that are included in our own analytics (the home page, about, docs, terms, login, and checkout), the site sends the page path to UpGate. The server turns the request IP address and user agent into a daily hash for a unique-visitor count. Those analytics tables store the path, the counts, and the hash. They do not store the raw IP address.
If you choose “Accept all”, we also use Google Analytics 4 and Mixpanel to understand how the site is used. Section 10 describes that choice.
We process news in order to produce the information products customers subscribe to, including API outputs, platform views, and historical datasets where the plan includes a backfill window. The length of that window is the one stated for the plan. It is not the same for every subscription.
6. AI-assisted processing and enrichment
UpGate is an information service for fintech and financial media. A news record can contain up to three different kinds of material, and they are not interchangeable.
Third-party source content is the item collected from a publisher or other source by RSS, API, or web collection. UpGate does not claim ownership of that source content and does not claim an unrestricted right to redistribute it. A customer’s right to use service outputs is the right described in the Terms and Conditions and the subscription.
UpGate-generated content is text UpGate writes itself, including website and blog editorial, and text produced when an item is reconstructed for the product.
Structured information is fields produced from an item. Where the pipeline produces them, those fields can include entities, events, a classification, a sentiment label, and a FactSheet. A FactSheet, when one is produced and accepted by the product schema, can include a core event, an event status, actors, mentioned entities, what happened, time and place, source claims, interpretations, signals, and a split between context taken from the source and context added by the system. Sentiment, when stored, is a label such as positive, neutral, or negative. A stored default is not proof that a person reviewed that item or that every enrichment step ran.
Not every record contains every field. Some items stay close to the source. Some are reconstructed. Some receive a FactSheet. Some receive classification or sentiment. An empty, default, or missing field means that output was not produced for that record.
Model-assisted steps can be incomplete or wrong. They are processing aids. They are not a promise that an entity, event, fact, or sentiment label is correct. Your account password and API key are not inputs to news reconstruction.
7. Legal bases
Customers and visitors are in more than one country. This policy does not claim that any one statute, including the EU or UK GDPR or a US state privacy law, applies to every visitor. It does not claim a certification, a registration, or a regulator relationship that the website does not publish.
Where the law that applies to a particular activity requires a legal basis, UpGate uses the basis that fits that activity: performing a contract with you, or taking steps you ask for before a contract, for accounts, trials, subscriptions, and API access; your consent, for optional analytics and session replay, which you can refuse or withdraw; a legal obligation, where a law that actually applies requires a record to be kept or disclosed; and legitimate interests, where that ground exists, in securing the service, preventing abuse, answering a request you made, and turning publicly available news into information products for business customers.
If the law that applies to you does not use those categories, the information is still used only for the purposes in this policy, and we honor the rights that law actually gives you.
8. Commercial data products and sharing
Customers receive structured news and related outputs through the API, dashboards, and other platform services on their plan. Those outputs can include historical items where the plan includes them. They can name people, companies, and events because the underlying news does. Delivering that product is the service the customer pays for.
That delivery is not a sale of our customers’ account contact details. We do not sell or rent your name, email, phone number, or company as a marketing list.
We share personal information with the providers in section 9 so they can perform the role described there, with advisers or authorities when we need to comply with law or protect the service, and with a buyer or successor in the case described in section 17.
9. Third-party service providers
Payment methods implemented in the service are Zarinpal, Paymento, and TheyPaid. A method is used only when it is enabled for that checkout. The provider then receives what it needs to start and confirm the payment.
Google and GitHub receive the sign-in flow if you choose them, and we receive the identifiers described in section 3.
Google Analytics 4 and Mixpanel receive usage data only after you choose “Accept all”. Mixpanel traffic from this site is sent to Mixpanel’s EU ingestion endpoint. The Mixpanel setup omits designated sensitive fields and strips query parameters such as tokens, passwords, and API keys from recorded URLs. Email address, phone number, and name are not sent to Mixpanel as profile traits. Session replay can run for a consented session. The site code currently samples those consented sessions at 100 percent. That figure is the current setting, not a promise that the setting will never change.
Google Analytics 4 is configured with IP anonymization in the site tag.
Botpress provides the website chat widget on the pages where that widget is loaded. The chat is loaded from Botpress’s content network.
An email delivery service sends service and support messages from [email protected]. The website does not publish the name of that provider.
Infrastructure providers host and protect the service. Where a request includes the Cloudflare country header, that header is the source of the signup country code described above.
Each provider’s own notice describes processing it performs for its own purposes.
10. Cookies and analytics
Essential cookies are used without the optional consent banner. The lang cookie stores the selected language and is kept for up to one year. A session cookie keeps you signed in. It is HttpOnly and SameSite=Lax, it is marked Secure when the server is not in debug mode, and its configured lifetime is 7 days. A CSRF cookie, where the authenticated app sets one, uses the same Secure and SameSite settings.
The upgate_consent cookie stores the policy version, your choice (essential only, or all), and the time of the choice. It is kept for about six months. It is sent with SameSite=Lax and, on HTTPS, with Secure.
Optional Google Analytics 4 and Mixpanel, including session replay, load only after “Accept all”. “Reject non-essential” leaves them off. You can change the choice from Cookie settings in the footer, which opens the cookie section of the Terms and Conditions, or by deleting upgate_consent and returning to the site.
The first-party page counts described in section 5 are separate from those optional tools and are not switched off by rejecting non-essential cookies. They cover the marketing paths listed there.
11. Retention
We do not publish one retention period for every record. There is no single timetable on this website.
Account and subscription records are kept while the account or subscription is active, and afterwards for as long as we need them to finish the contract, handle a dispute, or meet a bookkeeping or legal duty that applies to that record. This policy does not state a fixed number of years for those records.
The consent cookie lasts about six months. The trial rate-limit counters expire after one hour (IP) and 24 hours (email). The session cookie lifetime is 7 days. API logs that store an IP address and user agent are operational and security logs. This policy does not state a fixed number of days for those logs.
News datasets, including historical items, are product records. They can remain part of the information service after a customer account closes. Closing an account does not, by itself, delete a news item collected from a public source or a structured output produced from it.
12. Security
The public site is served over HTTPS. Passwords are stored with Django’s password hashing, not as plain text. API keys are confidential credentials for the account holder. The Terms require you not to share them. Session cookies are HttpOnly. Consent and session cookies use SameSite=Lax, and Secure when the connection and server mode provide it.
These are the controls this policy can describe from the service as it is built. This policy does not claim an external security certification, a penetration-test report, or a specific encryption-at-rest product. Those are not published on the website.
13. International transfers
The service is offered in more than one country. Processing can take place outside your country, including where a payment provider, analytics provider, sign-in provider, email provider, or infrastructure provider is located.
The published contact region is UAE · MENA. The published phone numbers use a +44 country code. When optional analytics is on, Mixpanel data from this site is sent to an EU ingestion endpoint. We do not identify one country as the location of every server or record.
Where a law that applies to a particular transfer requires a safeguard, we use the safeguard that law requires for that transfer. We do not claim that a named transfer tool, such as a standard contractual clause, is in place with every provider.
14. Your rights
Depending on where you live, the law may give you the right to access, correct, delete, or receive a copy of personal information, to object to or restrict certain processing, to withdraw consent, or to complain to a regulator. We will honor the rights that the law applying to your request actually gives you. This policy does not add those rights in a country whose law does not provide them.
Email a request to [email protected]. We may ask for what we need to confirm that the request is yours and to find the records. We may refuse or limit a request where the law allows it, including where a record must be kept, where the request would reveal someone else’s information, where we cannot authenticate it, or where the material is third-party news we do not have a right or a practical ability to erase.
We will answer within the time the applicable law requires, and otherwise within a reasonable time. We do not publish a response deadline of our own.
You can withdraw optional analytics consent at any time from Cookie settings without closing the account. Withdrawal does not undo processing that already happened, and it does not turn off essential cookies or the first-party page counts in section 5.
15. Public news and people named in it
News items often name individuals. Processing that material is part of the information service. It does not open a customer account for the person named, and the service is not a consumer-reporting or people-search product.
Source text remains the publisher’s content. We do not offer to rewrite a third party’s article, and we do not claim a right to force the publisher to delete it.
Reconstruction and structured fields that UpGate produced are UpGate outputs. If a field we produced is wrong, email [email protected] with the item and what is wrong. We will review the record we control. We do not promise that every field exists on that record, or that a correction removes the underlying source report. Copies already delivered to a customer, or kept in a historical dataset, may remain.
16. Children
Accounts, trials, and paid plans are meant for businesses and for adults using the website. Signup forms do not ask for a date of birth, and we do not run an age check. We do not knowingly open an account for a child.
If you believe a child has given us account information, email [email protected]. We will review it and, where the information is an account we opened, delete that account information.
A news product may still mention a child because a public source did. That is source reporting, not an account opened for the child.
17. Business transfers
If the business is sold, merged, reorganized, or its assets are transferred, customer and service records can pass to the successor as part of that transaction. The successor should keep this policy or tell you about a replacement. This section does not mean that a transaction is underway.
18. Changes to this policy
We will post changes on this page and change the effective date. The date above is the publication date of this version. Where a law requires a specific notice or a fresh consent before a change applies to you, we will follow that requirement. Other changes apply to processing after the published date. The Terms treat a notice on the website as a valid notice.
19. Privacy contact
Email: [email protected]
CEO: [email protected]
English policy: https://upgate.online/privacy-policy
Persian policy: https://upgate.online/fa/privacy-policy
WhatsApp and phone: +44 7536 661774 (@UpGateOnline)
Telegram: +44 77 1639 8756 (@UpGateContact)
Cookie choices are also described in the Terms and Conditions, at /terms#cookies and /fa/terms#cookies.
Effective date: 18 November 2026