Privacy Policy

SumSpot LLC · Last updated 30 September 2026

Who we are

SumSpot is published by SumSpot LLC. This policy covers the SumSpot app for iPhone, iPad and Mac, the SumSpot Safari extension, and this website. Questions, requests and complaints: [email protected].

When SumSpot sends a page

Once you enable the extension in Safari and grant it permission for a site, SumSpot runs on the pages you open on that site over HTTPS. On a page it has not summarized before, it sends the page for summarizing on its own, as the page loads. There is no button to press first.

Two things limit this:

• Safari’s own permissions. SumSpot only runs where you have allowed it. You control this per site, or for all sites, in Safari’s extension settings, and you can change it at any time.
• Pages already summarized. Summaries are cached on your device. Revisiting a page you have already summarized shows the stored copy without sending the page again.

Because it works this way, please assume that any page you open with SumSpot enabled will be sent — including pages you are signed in to, and pages that are not public. If a site holds anything you would not want copied to our server and to OpenAI, turn SumSpot off for that site.

What is sent, and to whom

To our server

For each page summarized, the extension sends the full page address (including anything after ? or #) and the visible text of the page body. Our server runs on Amazon Web Services in the US West (Oregon) region.

The same request carries your installation’s RevenueCat ID, so our server can check whether you have a subscription and count the free summaries you have used. Our server keeps the ID apart from the page: the stored summary does not include the ID, and the free-summary count does not include the page. The ID is never written to our diagnostic records, and it is not sent to PostHog with summary requests. See Subscriptions, and your installation’s ID.

There is one more case where an address reaches us without any page text. If summarizing fails and you tap “Try again”, SumSpot first asks our server whether it already has a summary for that address, so that a summary already generated is not paid for and generated twice. That request sends the page address and nothing else.

To OpenAI

Our server passes the page text to OpenAI’s API, which generates the summary and returns it. OpenAI receives the page text. It does not receive the page address.

As OpenAI’s policy stands in July 2026, text sent to it through the API is not used to train or improve its models unless the sender opts in to share it, which we have not. OpenAI does keep API inputs and outputs for up to 30 days to check for misuse of its service.

Both of those are OpenAI’s policies rather than promises we are in a position to make for them, and OpenAI can change them without changing anything about SumSpot. Its current terms are published in OpenAI’s own documentation.

Recorded with every request

Our server keeps a short diagnostic record of the requests it receives, so that when something breaks we can tell what broke. That record holds the kind of request, how much text it carried, and — for a summary — the domain of the page, such as example.com, and where your copy of SumSpot came from (see below). It does not hold the rest of the address, the page text, your IP address or your browser’s user-agent. These records are deleted after 14 days.

Which versions you are running

With each request, we note which version of SumSpot sent it and which version of the system it came from, such as iOS 18.0. How precise that is depends on what the request reports: Safari on iPhone and iPad gives the iOS version, the app gives only the major version, such as 18, and Safari on a Mac gives only its own version, not the version of macOS. We use these to tell whether a problem affects only some versions, and to see when people have updated. The operating system version comes from the user-agent your browser or the app already sends with every request: we keep only the version number and discard the rest, so the user-agent itself is never stored. Versions are recorded with the summary records sent to PostHog, described below, and with the counts when those carry no ID, and nowhere else.

Where your copy of SumSpot came from

With each request, we also note whether your copy of SumSpot came from the App Store, from TestFlight (Apple’s service for testing apps before release), or was built by a developer. That is all it records: one of those three, and nothing about you. We use it to keep testers’ activity out of the numbers, so that someone trying a test version is not counted as a new user. Unlike the versions above, it is kept on our server as well: with each of the counts described below, for 12 months, and on the diagnostic record of each summary request, for 14 days. It is also sent to PostHog with the summary records and with any count that carries no ID, but never with the copies of the counts that carry your installation’s RevenueCat ID.

To PostHog

We use PostHog, an analytics service, to chart how SumSpot is used. Our server sends PostHog a copy of each of the counts described in the next section, plus a technical record of each summary request: how much text it carried and how that text was taken from the page, which AI model answered, how long it took, how many tokens it used, whether it worked or why it did not, and whether the summary was saved. The page address, the page’s domain, the page text and the summary are never sent to PostHog.

These copies come from our server, not from your device. PostHog sees our server’s IP address, never yours. The app and the extension contain no PostHog code. Each summary record is given a new random ID when it is sent and carries nothing that identifies you or your device, so summary records cannot be gathered into a profile of you. The copies of the counts are different: once the app has been opened, they carry your installation’s RevenueCat ID, so we can see how people move from installing SumSpot to using it, such as how many people who open the app go on to get the extension working, and how many come back. Those copies never include a page address, a site, page text, the version of SumSpot or your operating system, or where your copy of SumSpot came from. PostHog stores all of these in the United States for 12 months.

Small requests that carry no page content

SumSpot sends a handful of requests that are not about any particular page. None of them contains an account or a page address, and none of them summarizes anything or generates any content. What they are for is counting: how many people get SumSpot working, and where people get stuck. Once the app has been opened, the counts carry your installation’s RevenueCat ID. The copies on our own server leave it out; the copies sent to PostHog keep it, so the counts from one installation can be put in order there. It is the same random ID described under Subscriptions, not your name, email or Apple Account.

• Settings check. About twice a day, a device without a subscription asks our server how many free summaries it should offer. The request contains no information about you or the page.
• Limit reached. When you run out of free summaries, we record that this happened, at most once per day per device, so we can tell how many people reach the limit.
• Extension is working. Once a day, on a day the extension runs on a page, we record that it ran — along with whether you have allowed SumSpot on every site or only on particular ones. Which of the two, never which sites.
• Extension ran for the first time. The first time the extension works in a browser, we record that once, with the same all-sites-or-some-sites note. This is how we tell how many people get through Safari’s setup at all.
• App was opened. Once a day, on a day you open the app, we record that it was opened and whether the extension has ever run on the device. This is sent by the app itself, so it happens whether or not you have enabled the extension.
• App was opened for the first time. The first time you open the app on a device, we record that once, and nothing else. Devices that already had SumSpot before this was added are not counted.

The settings check is not counted at all — it leaves only the 14-day diagnostic record described above. The five counts below it are kept for 12 months, on our server and in the copies sent to PostHog. All of them are sent whether or not you have a subscription. Clearing your browser data or reinstalling can make the “first time” ones happen again, because the only record that they already happened is the one kept on your device.

What we store, and for how long

Summaries stored from 30 July 2026 onwards are deleted automatically after twelve months, which is how far back we look when counting how SumSpot is used. Records stored before that date were made before we set that limit and do not expire on their own — but on 30 July 2026 we deleted the stored page text from every one of them. What is left is the page address, the summary we generated, and the date.

Subscriptions, and your installation’s ID

Subscriptions are sold through Apple. Apple handles the payment; we never see your card details, and Apple tells the app only whether a subscription is currently active.

We use RevenueCat, a subscription-management service, to keep track of subscription status. RevenueCat receives purchase and receipt information from Apple and gives your installation a random ID of its own. The ID is not your name, email or Apple Account. Reinstalling SumSpot usually gives you a new one.

We use that ID in three ways:

• To check your subscription. Each summary request carries the ID, and our server asks RevenueCat whether it has an active subscription. The answer is held in memory for a few minutes and not stored.
• To count free summaries. Without a subscription, our server counts your summary requests against the ID. The count is deleted 12 months after your last request.
• To record how you use SumSpot. The app adds these details to your RevenueCat record: whether the extension is set up, and when it last ran; how many free summaries you have used, and your limit; how many summaries you have opened, in total and with a subscription, and when you last opened one. Our server adds when it last summarized a page for you and how many free requests it has counted. These are counts and dates only. They never include a page address, a site, page text or a summary.

We use these details to tell people who never got the extension working apart from people who used it and stopped. We may also use them to decide which subscription offer the app shows you, for example one for people who have used all their free summaries. We do not use them for advertising or share them with anyone for advertising, and RevenueCat processes them for us, not for its own purposes.

The ID is not attached to the page addresses, page text or summaries we store, or to the summary records sent to PostHog. It is attached to the copies of the counts sent to PostHog, described under To PostHog.

This website

sumspot.app uses Google Analytics to count visits and see which pages people read. Google sets cookies and receives your IP address and page views in the process. This is separate from the app and the extension, and blocking it in your browser has no effect on how SumSpot works.

What we do not do

• We do not ask you to create an account, and we do not collect your name, email address or password.
• We do not sell or rent your information, and we do not share it for advertising.
• We do not show ads, and the extension contains no third-party advertising or analytics trackers. The counts described above go to our own server, which passes a copy to PostHog as described; nothing on your device sends anything to PostHog.
• We do not link your browsing across sites into a single record. The stored summaries carry no identifier for the person who requested them, and your installation’s RevenueCat record holds counts and dates, never a page or a site.

Your choices

• Stop sending pages. Turn SumSpot off for a site, or for all sites, in Safari’s extension settings. You can also remove the extension entirely.
• Clear what is on your device. Removing the extension clears its cached summaries and counters.
• Delete your installation’s record. Ask for this from the app: open Manage Subscription and contact support. The message carries your installation’s ID, so we can delete its RevenueCat record, its free-summary count and the copies of its counts held by PostHog without asking you anything else.
• Ask us to delete something. Write to [email protected]. Please be aware of a real limitation: because we store no identifier alongside a summary, we usually cannot tell which stored records came from you. If you send us the page addresses, we can find and delete those records. We cannot reliably locate “everything from this person”, because that link does not exist in our data.
• Data protection rights. Depending on where you live, you may have the right to access, correct, delete or export personal information, or to object to how it is processed. Write to the address above and we will do what we can within the limitation just described.

Children

SumSpot is not directed at children under 13, and we do not knowingly collect information from them.

Where your information goes

Our servers are in the United States, OpenAI processes page text in the United States, PostHog stores its analytics records in the United States, and RevenueCat stores subscription records in the United States. If you use SumSpot from elsewhere, the information described here is transferred to and stored in the United States.

Security

Traffic between the extension, our server and OpenAI is encrypted in transit. Stored data sits in Amazon Web Services with access restricted to us. No system is perfectly secure, and we would rather say so than imply otherwise.

Changes to this policy

If we change how SumSpot handles your information, we will update this page and change the date at the top. Significant changes will also be described in the app’s release notes.