Privacy policy
Last updated 16 November 2026
Ashum is run by convertlyft AI Developing Services CO. L.L.C S.O.C, a company in the United Arab Emirates. This page says what information the website at ashum.ai and the Ashum API collect, what it is used for, who receives it and how, how it is protected, and how to have it removed. Questions: support@convertlyft.com.
1. What we collect
Reading without an account. You can read Ashum without giving us anything. If you choose sections for the daily report page, the choice is kept in a cookie in your browser. The marker that shows which stories are new since your last visit is kept in your browser only and is never sent to us.
An account. Your email address. If you sign in with Google, the name on your Google account and Google’s reference for it. The sections and send time you choose for the daily report email, whether you want it, and when the last one was sent. When the account was made, when you last signed in, and whether it has added funds.
Alerts. The words, the DFM company, or the exchange rate or gold price and the line you ask us to watch for, when each alert was made and last emailed, which of a company’s disclosures its alert has already sent you, and the figure a price alert last saw.
The API. The names you give your keys, the first characters of each key, a fingerprint of each key (not the key itself), and when each key was made, last used and revoked. A revoked key stays on this list. How many requests each key and account made, and how many requests the account holds.
Payments. You type your card details on Stripe’s page, not ours. We never see or store them. We keep Stripe’s reference for you as a customer, the reference of each payment, and how many requests it bought.
Stopping abuse. We count requests for a short time by internet address (IP address): searches on the site, the page’s own check for new stories, the figures behind the charts, CSV files downloaded, sign-in links asked for, Google sign-ins started, and attempts with a wrong API key. Sign-in links asked for are also counted by the email address typed, whether or not it has an account. For an account we count the keys made, alerts added and payments started in an hour. These counts are deleted after two days.
How the site is used. We use Convertlyft, an analytics service run by the same company, to see how people use ashum.ai.
- It records the pages opened and their addresses (a search on the site is part of the page address, so it includes the words searched for), where a visit came from, clicks and scrolling, the kind of browser and device, page speed and errors. It records visits so that they can be replayed.
- It is also told when someone makes an account (with Google or an email link, and how many report sections they chose first), chooses report sections without an account, adds an alert (on words, on a company or on a price), makes an API key (and whether it is the account’s first), sends the form to add funds (with the amount), or completes a payment (its amount in dollars and a scrambled reference to it, not the payment’s own reference); and when an example API request is copied, a widget’s code is copied (with which widget) or the currency converter is first used (with the currency). None of these carries an email address, an account or a key.
- Recordings hide what is typed into fields. Your email address where the account pages show it, a newly created API key, and the sample request that carries that key are masked.
- To recognise the same browser from one visit to the next, it keeps identifiers in your browser (they are listed under Cookies). It uses your IP address briefly to filter out automated traffic and to work out an approximate location, and does not store it.
More detail is in Convertlyft’s privacy policy.
2. What we use it for
- To sign you in and keep your account.
- To send our emails: sign-in links, alerts, and the daily report. A new account starts with the daily report switched on; you can switch it off at any time.
- To run the API: check keys, count requests against your balance, and take payments.
- To protect the service from abuse.
- To understand how the site is used so we can improve it.
We do not sell your information, and we do not use it for advertising.
3. Who receives it, and how
We pass information only to the companies that run parts of the service for us, and only what each needs. It travels over encrypted connections.
- Vercel hosts the website and the API. Every request passes through it.
- Supabase holds the database, in Mumbai, India. It also runs the search by meaning, so the words of a search are sent to it.
- Stripe takes payments. When you start a payment we give Stripe your email address, your name and the number of your Ashum account, so the payment can be tied to it. When you delete your account we have Stripe delete its customer record for you; Stripe keeps its own records of payments.
- Resend delivers our emails. It receives your email address and the email itself.
- Zoho hosts our mailbox. It receives the emails you send to support@convertlyft.com.
- Google, only if you choose to sign in with Google. Google tells us your email address and name; we send Google nothing else about you.
- Convertlyft receives the usage information described under What we collect.
These companies may process information in other countries. We do not give your information to anyone else, unless the law requires us to.
4. How it is protected
- The site and the API are served only over encrypted connections (HTTPS), and so is every connection to the database.
- API keys are stored only as fingerprints, so a copy of the database could not be used to call the API. A key is shown only when you create it.
- Card details never reach our servers.
- A sign-in link works once and stops working after 20 minutes. The cookie that keeps you signed in is signed, so it cannot be forged, and cannot be read by scripts on the page.
- The database refuses anonymous access, and the website connects to it with an account that can do only what the site needs.
- Guessing of API keys is limited by address. A sign-in link is signed, so one cannot be made up.
No service can promise perfect security.
5. How long we keep it
- Account information, alerts and API keys: until you delete the account.
- Request counts by key, account, internet address and typed email address: two days.
- Our record of your payments: until you delete the account. Stripe keeps its own records of payments.
- After an account is deleted: a fingerprint of its email address, not the address itself. It cannot be turned back into the address. We keep it so that the same address is not given trial requests a second time.
6. Cookies
ashum_sessionkeeps you signed in, for 30 days.lf_sectionsremembers the sections you chose for the daily report page, for a year.- Short-lived cookies carry you through signing in: for 15 minutes or less, the address you typed into the sign-in form, the page you were going to, and a one-time check for Google sign-in; for an hour, a price alert you set before signing in, until you confirm it. Another shows a newly created API key, for two minutes. Another, for two minutes, carries the name of a step just completed, such as an account made or an alert added, to the next page, which passes it to Convertlyft and deletes it. After a payment, your browser’s own storage keeps its scrambled reference, so that it is passed on only once.
- Convertlyft sets three:
cvl_visitorrecognises the same browser on a later visit, for a year;cvl_ftremembers where your first visit came from, for a year;cvl_sidmarks the current visit, for a day. It keeps a copy of the first two in the browser’s own storage.
We set no advertising cookies.
7. Your choices
- Stop the daily report email or an alert with the link in any of those emails, or on your account page.
- Revoke an API key on your account page at any time.
- Delete your account on your account page. It is removed at once, with its alerts, API keys and our record of its payments.
- Ask for a copy of the information we hold about you, or for a correction: write to support@convertlyft.com from the email address of the account.
8. Changes
We will update this page when what we collect or who receives it changes. The date at the top shows the latest version.