AltSays Privacy Policy

DraftLast updated 2026-11-18. Not yet reviewed by a lawyer; highlighted parts are still to be filled in.

Effective date: 2026-11-18
Applies to: the AltSays Chrome extension and the AltSays service at api.altsays.com.

The short version:

  • AltSays sends only the image area you pick, plus a little text from around it, to make alt text. We don't keep the image or the text.
  • We never collect your browsing history, full web addresses, cookies, or anything you copied.
  • We keep daily usage counts tied to a one-way hash of a random install code and of your network address, not to you. They're deleted after the day ends. We never store your IP address.
  • We remember, for each install (hashed), the day it was first and last used, so new installs get a smaller daily allowance. That's deleted after 90 days without use.
  • We count totals, like how many images AltSays described each day and how many installs were active. These counts can't be linked to you, your images or the pages you visit.
  • If you choose to give us your email for feedback, you confirm it by email first, and we keep it until you unsubscribe. That's optional and off by default.
  • We never sell your data or use it for ads.

1. Who we are

AltSays is made by Shreyansh Banthia, operating as TiffinWorks (a registered Ontario business name, sole proprietorship), Toronto, Ontario, Canada. In this policy, "we" and "us" mean TiffinWorks.

Shreyansh Banthia is responsible for privacy at TiffinWorks and answers every privacy question personally.

  • Email: hello@tiffinworks.com
  • Mail: To be added: [PO BOX — TO BE ADDED], Toronto, Ontario, Canada

2. What we collect, and why

We collect as little as we can. Here is everything, feature by feature.

2.1 Making alt text (the main feature)

Nothing happens until you start it, by pressing the shortcut, clicking the toolbar icon, or choosing "Copy alt text" from the right-click menu. Then you click an image or drag a box.

On your device:
Chrome gives AltSays a screenshot of the visible part of the tab. AltSays cuts out just the area you picked, shrinks it (at most 768 pixels on the longest side), and throws the rest of the screenshot away. This all happens on your computer.

What is sent to our service (api.altsays.com):

WhatWhy
The cropped image of the area you pickedSo the AI can describe it
Up to 7 short bits of page text, each cut to 300 characters or less: the image's existing alt text or label, a nearby caption, the nearest heading above it, the text of a link or button around it, the host name of that link (like example.com), the page title, and the page's host nameSo the alt text fits how the image is used on the page
Whether the image is inside a link or buttonAlt text for links and buttons should say what they do
Short or long modeYour length setting
Your install token (see 2.2)To apply fair-use limits

We send the host name only, never the full web address. No page path, no search query, no URL parameters.

What happens to it: Our service checks the request, then passes the image and page text to our AI provider, Anthropic (the Claude API), which writes the alt text. The answer streams back to your browser and AltSays copies it to your clipboard.

We do not store the image, the page text, or the alt text. They are held in memory for that one request and then dropped. Anthropic's own retention is explained in section 5.

Please note: the image and page text are whatever is on your screen. If you pick a photo of a person, or a page title contains a name, that goes to the AI as part of the request. Only pick things you are allowed to share with a service like this. The AI is told not to guess who people are, or their age, race, gender or feelings, unless the page itself names them.

2.2 Install code, token and daily limits

To keep AltSays free and stop abuse, each request has to carry a token.

  • When you install AltSays, it makes a random install code (a UUID). It is not linked to your name, email, Google account or device.
  • AltSays sends this code to our service once. The service signs it and sends back a token. The token contains the install code and the time it was issued. Both are saved in Chrome's storage on your device.
  • On our side, we do not save the install code or the token in the clear. Instead we make a keyed one-way hash of the install code (a hash mixed with a secret key, so it can't be turned back into the code or matched by anyone without the key).
  • For that hash we keep a count of requests for today (UTC), and the number of times the install asked for a new token today. This lets us apply the daily limit. The limit depends on how new the install is: currently 20 images a day for the first 3 days, 60 a day until day 14, and 150 a day after that.
  • To know how new an install is, we keep, for that same hash, the date it was first seen and the last day it was used. This record is deleted automatically after 90 days without use. (If you come back after that, AltSays treats you as a new install.)
  • Daily counts are deleted automatically after the day ends (UTC).

We also keep, with no link to any user:

  • an estimate of today's total AI cost, so the service can pause if it goes over our daily budget;
  • an "out of funds" flag with the time it started and a count of turned-away requests, used when our prepaid AI balance runs out;
  • daily totals (see 2.4).

2.4 Daily totals

We count totals, like how many images AltSays described each day and how many installs were active. These counts can't be linked to you, your images or the pages you visit.

Each total is just a date, a name and a number, for example "18 November: 412 images described as *informative*". We count, per day (UTC):

  • images described, by type (informative, functional, text, complex, decorative, redundant, group);
  • how many installs used AltSays that day, and how many new installs signed up;
  • errors and limit messages, by kind (for example "too many requests").

To count active installs, our service adds one the first time an install makes a request that day. It doesn't keep a list of which installs were active.

The totals never include images, alt text, page text, web addresses or site names, IP addresses, browser details, install codes or tokens, or anything else that could point to you. We use them to see how AltSays is doing and to describe it in grant applications and reports, for example "AltSays described 2,000 images this month". We may share these totals, but they're not about anyone.

2.3 Your IP address

Your browser can't reach any website without sending an IP address, so our host (Cloudflare) sees it. We use it only for rate limits, to stop one network from using up the free service. We never use the full address itself: we take the network part (your IPv4 address, or for IPv6 the /64 and the wider /48 network) and turn it into a keyed one-way hash (mixed with a secret key).

  • For that hash we keep counts for the current UTC day only (images requested and new installs registered from that network). They are deleted automatically after the day ends.
  • Short-term counts (for example, at most 10 requests a minute) are kept in memory only.
  • We never write your IP address to storage or logs.

Cloudflare may also process IP addresses and basic request data to run and protect its network. See section 5.

2.5 Logs

We have turned off Cloudflare's stored Workers Logs for our service. Our code writes only these fields when it writes a log line at all: time, the short token hash, the result status, how long it took, the AI model name, and the number of AI input and output tokens used. These lines are only visible if we are actively watching live (for debugging); they are not saved by us.

We never log images, page text, alt text, your email address, your IP address, request headers or tokens.

2.6 Settings on your device

AltSays saves a few things in Chrome's local storage, on your computer only: your install code and token, short/long mode, the "mark decorative images" setting, your preferred format for long descriptions, display preferences (theme, toast position and whether the result closes by itself), whether the intro has been seen, and whether the service is currently out of funds. We can't see these. They are deleted when you remove AltSays.

2.7 Optional feedback emails

Draft note: [NOTE: this feature is built but not switched on yet. Publish this section when it goes live.]

AltSays may ask: "Email me occasionally to ask for feedback on AltSays." The box is unticked by default. If you tick it and enter your email, we store:

  • your email address (in lower case),
  • the purpose (feedback),
  • the date and time you agreed,
  • which version of the consent wording you saw, and a fingerprint (hash) of that exact wording,
  • where you signed up (for example, the intro screen) and the AltSays version,
  • a one-time confirmation code (the confirmation link works for 7 days),
  • the date and time you confirmed,
  • a random unsubscribe code, and
  • the date you unsubscribed, if you do.

Double opt-in. After you sign up, we send one email asking you to confirm. Nothing else is sent until you click the link in that email. If you don't confirm, you won't hear from us.

We use your email only to occasionally ask for feedback on AltSays. Every email comes from Shreyansh Banthia, includes our contact details and mailing address, and has a working unsubscribe link. The link opens a page with an Unsubscribe button; press it and you're unsubscribed (the button is there so an email scanner opening the link can't unsubscribe you by mistake). You can also just email us.

We don't store your IP address, install code or browser details with your email. Your IP is only used, as a keyed hash in memory, to limit sign-ups to 5 per hour, and is not stored.

This is separate from the Substack newsletter. If you follow our link to Substack and subscribe there, Substack collects your email under its own privacy policy. We don't send your email to Substack, and signing up on Substack doesn't sign you up here (or the other way round).

2.8 Emails you send us

If you email us at hello@tiffinworks.com (for example with the "Email Shreyansh" button shown when AltSays is out of funds, or for support), we receive your email address, name if you include it, and whatever you write. We use it only to reply and to fix problems. See section 6 for how long we keep it.

2.9 Chrome Web Store

You install AltSays through Google's Chrome Web Store. Google handles that under its own privacy policy. Google may show us summary numbers, such as how many people have installed AltSays, and any public reviews. We get no personal details about who installed it.

The AltSays intro has links to Substack and LinkedIn. Nothing is sent to them unless you click. If you do, you are on their site and under their policies.

2.11 If you choose to support AltSays

If you choose to support AltSays, payment is handled by Stripe, Inc. on Stripe's own checkout page; altsays.com and the extension never see your card details. Stripe shares with me your name, email, country, amount and a partial card description so I can keep tax records and issue refunds. I keep these records for six years as Canadian tax law requires, and never sell them or use them for marketing. Stripe's processing is governed by its privacy policy (https://stripe.com/privacy). Contributions are voluntary payments to TiffinWorks, a sole proprietorship. They are not charitable donations and are not tax-deductible.

3. What we never collect

  • Your browsing history or the list of sites you visit
  • Full web addresses (paths, queries, parameters). We send host names only.
  • Cookies. AltSays doesn't set or read cookies.
  • Your clipboard. AltSays only writes alt text to it; it never reads it.
  • Anything on the page you didn't pick: the rest of the screenshot, form fields, passwords, keystrokes
  • Your name, Google account, or any account (AltSays has no accounts). The only exception is if you choose to support AltSays through Stripe (see 2.11).
  • Analytics that follow you, tracking pixels or ad IDs. (The daily totals in 2.4 are counts, not tracking.)

And we never store the images or page text you send, never sell personal information, and never use it for advertising.

Canada (PIPEDA): We rely on your consent.

  • For alt text, you give it when you start AltSays and pick an image. That action is the request. This policy and the Chrome Web Store listing explain what is sent.
  • For feedback emails, we ask for express consent with an unticked box, as Canada's Anti-Spam Legislation (CASL) requires. We keep a record of that consent.
  • You can withdraw consent at any time: stop using AltSays or uninstall it, and unsubscribe from emails.

EU and UK (GDPR / UK GDPR), if they apply to you:

  • Making alt text: to provide the service you asked for (contract).
  • Daily counts, install first-seen and last-seen days, and network-based rate limits: our legitimate interest in preventing abuse and keeping a free service running.
  • Feedback emails: your consent.
  • Replying to your emails: our legitimate interest in answering you.
  • Records of a voluntary payment, if you choose to support AltSays: our legal obligation to keep tax records.

5. Who processes data for us, and where

We use a small number of service providers. They may only use the data to provide their service to us, under their terms.

ProviderWhat they doWhat they get
Cloudflare, Inc. (USA)Hosts api.altsays.com: Workers (the service code), Durable Objects (daily counts and install records), D1 (feedback email list and daily totals), Email Routing (alert emails to us)Every request to our service, including your IP address; the hashed daily counts and install records; the feedback email list; the daily totals
Anthropic, PBC (USA), Claude APIWrites the alt textThe cropped image, the page text listed in 2.1, and our fixed instructions. Not your IP address, install code or token.
Google LLC (USA)Chrome Web StoreInstall and review data, under Google's own policy
Stripe, Inc. (USA)Processes voluntary payments if you choose to support AltSays, on Stripe's own checkout page (Stripe privacy policy)Your card details (we never see them), name, email, country and amount. Stripe shares with us your name, email, country, amount and a partial card description.
To be added: [EMAIL PROVIDER — TO BE ADDED]Our email inboxEmails you send us
To be added: [EMAIL SENDING SERVICE — TO BE ADDED]Sends feedback emails (only when that feature is live)Your email address and unsubscribe link

Anthropic's data use. We use Anthropic's commercial API. According to Anthropic:

So while we don't store your images, Anthropic may hold them for up to 30 days (longer in the cases above) before deleting them.

Where your data goes. We are in Canada, but our providers process data in the United States and, for Cloudflare, possibly in other countries where its network runs. That means your data may be subject to the laws of those countries, and their courts and authorities may be able to access it. We choose providers with strong security and contract terms. If you are in the EU or UK, transfers rely on the providers' standard contractual clauses or other safeguards in their data processing terms.

6. How long we keep things

DataHow long
Image and page text you pickNot stored by us. Held in memory for one request. (Anthropic: see section 5.)
Alt text we generateNot stored by us.
Daily counts per hashed install code and per hashed network addressThe current UTC day. Deleted automatically after it ends.
First-seen date and last-seen day per hashed install codeDeleted automatically after 90 days without use.
Short-term (per-minute) rate-limit countsMemory only. Never stored.
Your IP addressNever stored by us.
Today's cost estimate, out-of-funds flagCost estimate: current day. Flag: until funds are restored. Neither is about you.
Daily totals (2.4)Kept for as long as AltSays runs. They are anonymous totals, not about you, and they show how AltSays is used over time.
Settings, install code, token on your deviceUntil you uninstall AltSays.
Feedback email (if you opted in)If you never confirm: To be confirmed: [unconfirmed sign-up retention — TO BE CONFIRMED]. If you confirm: until you unsubscribe. After that, we keep your email, consent record and unsubscribe date for To be confirmed: [3 years — TO BE CONFIRMED] as proof of consent and to make sure we never email you again, then delete them. Ask us and we'll delete them sooner, unless the law requires us to keep them.
Emails you send usUp to To be confirmed: [2 years — TO BE CONFIRMED] after our last reply, then deleted.
Payment records, if you choose to support AltSaysSix years, as Canadian tax law requires.

7. Security

  • All traffic to our service uses HTTPS.
  • Tokens are signed with a secret key, so they can't be forged.
  • Counters use keyed one-way hashes, never install codes or IP addresses in the clear.
  • API keys and secrets are stored as encrypted secrets in Cloudflare, never in the extension.
  • AltSays asks Chrome for as few permissions as possible. It only runs on a page when you start it, and only talks to api.altsays.com.
  • Only Shreyansh Banthia has access to our service and data.

No system is perfectly secure. If a breach of our safeguards creates a real risk of significant harm to you, we will tell you and the Office of the Privacy Commissioner of Canada, as the law requires.

8. Your rights

You can ask us to:

  • tell you what personal information we have about you, and give you a copy;
  • correct it;
  • delete it;
  • stop using it, or withdraw your consent.

Email hello@tiffinworks.com. We'll reply within 30 days. We may ask you to confirm it's you (for example, by replying from the email address in question).

Good to know: for alt text, we don't keep anything that identifies you, so there's usually nothing to give back or delete. Uninstalling AltSays removes everything on your device. For feedback emails, we can find your record by your email address.

Complaints. Please contact us first and we'll try to fix it. You can also complain to:

  • the Office of the Privacy Commissioner of Canada: priv.gc.ca, 1-800-282-1376;
  • in Quebec, the Commission d'accès à l'information du Québec: cai.gouv.qc.ca;
  • in the EU, your local data protection authority; in the UK, the Information Commissioner's Office: ico.org.uk.

If GDPR or UK GDPR applies to you, you also have the right to restrict or object to processing and to data portability.

9. Children

AltSays is a tool for people who publish content on the web. It is not meant for children under 13 (or under 16 in the EU and UK), and we don't knowingly collect their personal information. If you think a child has given us their email, contact us and we'll delete it.

10. Chrome Web Store User Data Policy

The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

In plain words: we use the data AltSays handles only to make alt text and keep the service running. We don't sell it, don't use it for ads or credit decisions, and don't let people read it except to provide support you ask for, for security, or where the law requires.

11. Changes to this policy

If we change this policy, we'll update the date at the top and post the new version at https://altsays.com/privacy/. If a change affects how we use information we already have, or adds a new use, we'll tell you clearly (for example, in the extension or by email if you opted in) and ask for consent again where the law requires.

12. Contact

Shreyansh Banthia, TiffinWorks
To be added: [PO BOX — TO BE ADDED], Toronto, Ontario, Canada
hello@tiffinworks.com