LapseWatch

Privacy Policy

The short version

If you use the Chrome extension and do not sign in, the reminders you create exist only on your own computer. We cannot see them, and there is no server that could. The extension makes no network requests at all in that mode, and that is a principle we do not intend to change.

The website and the LINE bot are different. Neither has local storage to use, so a list created there is stored on our server. See Three ways to use it below.

Signing in is optional and free (email reminders cost nothing). When you do sign in, the only things sent to us are your email address and a session credential. The one exception is push reminders, which you switch on yourself: to send you an email or a LINE message at the right moment, our server has to know when to send it and what date the item expires. Even then, the source URL and the page content never leave your computer.

1. Single purpose

To help you record and be reminded of expiry dates for subscriptions, trials and other services.

2. What we collect

• Extension, not signed in: nothing. No data is sent to us or to any third party. No analytics, no ad tracking, no remote logging of any kind. This is not only a promise — the only outbound code in the extension is the licence check and the push upload, and neither runs until you sign in. For a user who has never signed in, the extension issues no requests at all.
• After you sign in, your email address and a session credential are sent to our server to identify your account and confirm your licence status.
• Using the website or LINE, the list you record is stored on our server, because those two entry points have no local storage.

3. Analytics on this website

This section is about the site lapsewatch.smallworks.app, not the extension. The statement above that there are no analytics refers to the extension, and that is still true. Keep the two separate.

This website uses Cloudflare Web Analytics to count how many people arrive and which page they came from. We need to know which content actually helps people; otherwise we are deciding by feel.

It does not:

• set cookies
• fingerprint your browser
• build a cross-site profile of you, or sell your browsing behaviour to anyone

What it records is page-level: how many times a page was viewed, the referring site, the rough device type. None of it maps back to you as a person, and we have no way to learn “which pages did this individual read”.

The signed-in list page carries no analytics at all. That is your personal screen, and “who looked at their own subscription list, and when” is information nobody needs. For the same reason, that page is not indexed by search engines.

4. What the extension reads from a page

Only at the moment you click the LapseWatch icon, and only on the tab you are looking at. Then:

• It extracts only fragments 200 characters either side of keywords such as “trial”, “expires”, “renews”, “next billing”. The full page never enters the processing path.
• Before any text reaches the parser, it masks card numbers and last four digits, email addresses, phone numbers, tax and national ID numbers, addresses, and names appearing after labels such as “Recipient:” or in greetings. Masking is one-way — the original text is not retained anywhere.
• It never reads input, textarea or select elements, forms, password fields, card fields, hidden content or iframes, and it does not read cookies or site local storage.
• It never scans other tabs in the background, never reads your history, and does nothing at all when you have not clicked.
• When recording the source page it keeps only the domain and path — query parameters and fragments are discarded, because checkout URLs frequently carry an email address or a name in them.

5. What is stored locally

Only after you press “Create reminder”, and only:

• the service name you typed or confirmed
• the expiry date you confirmed, and your time zone
• the domain and path of the source page (no query string)
• reminder state (notified, cancelled, calendar link generated)

This lives in the browser's local storage (chrome.storage.local). It is not synced to your Google account and does not leave this computer.

6. Permissions

Every permission the extension declares, and why it needs it:

• activeTab — read the page you are looking at. Granted only at the instant you click the LapseWatch icon, for that one tab, once. No click, no permission; close the window and it is gone. This is also why the install screen does not say “read your data on all websites”.
• scripting — run the date-finding code. Sends the date-finding code into the page you just clicked on. It runs inside the page and returns only masked fragments; page content is not sent anywhere.
• storage — keep reminders on your computer. Stores the reminders you confirmed. Local only, never synced, never uploaded. You can delete all of it at once from the settings page.
• alarms — wake up at the right time. Schedules local alarms before the expiry date. They live in the browser and touch no server.
• notifications — show the reminder. Shows a desktop notification containing only the service name you typed and the expiry date.
• identity — sign in with Google or LINE (only when you do). Used when you press “Sign in with Google” or “Sign in with LINE” to open the provider's login screen and bring the result back. We receive only your email address — not your name, avatar or contacts. It is never used if you do not sign in, does not run in the background, and reads none of your account data; Chrome opens a login window at the moment you press the button and that is all.

The extension does not declare tabs, history, cookies, webRequest or persistent access to any site, and requests no Google OAuth scopes.

7. Google Calendar

“Add to Google Calendar” produces a pre-filled calendar URL that you open yourself. The extension cannot create a calendar event for you and has no permission to do so — you press save on Google's page. Once you click, your browser goes to Google and that connection is covered by Google's privacy policy. We send Google nothing; the URL contains the service name and date you can see on screen.

8. Three ways to use it, three different data paths

LapseWatch has three entry points and they are materially different. Covering them with one paragraph would make you think you have more protection than you do, so here they are separately:

If you arrive by adding the LINE bot as a friend, we do not know who you are. We receive a user identifier from LINE (a string of letters and digits) so we know where to send messages. We cannot see your LINE display name, your photo or any of your conversations. We ask for an email address only when you pay, because a receipt needs one.

Shared lists — the one place another person sees your data

The paid tier lets you invite up to 5 people to the same list. This is the only feature where your data is visible to another person, so:

• What they see: the service names, amounts, charge dates, notes and the “who pays” field on your list. They do not see your account data beyond your email address, your payment records, or the separate list kept in your browser extension.
• It is one-way. People you invite see your list; you do not see theirs unless they invite you too.
• You can revoke it at any time. Remove someone and they lose access immediately — we delete the sharing record rather than flag it inactive. Any pending reminders they had scheduled for that list are removed too.
• Members switch their own reminders on; the default is off. Adding someone to a list does not start messaging them. That would be harassment, not a reminder. Once they opt in, what they receive follows their own push settings (channel, whether service names are shown), not yours.
• “Who pays” is a free-text field. The name you type there (“Mum”, say) is visible to every member of the list, and it may be a third person's data. Use whatever the two of you understand — not a full name, phone number or anything else identifying. This field never appears in any push or reminder message; it is only on the screen you open yourselves.

9. Paid features and your account

Prices are on Plans and pricing. Here is what leaves your computer once you sign in or buy:

• No account is needed if you do not sign in. “No signup, no sign-in, no network” applies to the extension-without-signing-in path and is a principle we do not intend to change. Signing in is something you choose to do; before that, the extension issues no requests. Signing in is itself free — email reminders are not a paid feature.
• Only two things are sent for licensing: your email address (to sign in and identify the account) and a session credential (to confirm licence status).
• Source URLs and page content never leave your computer — whether or not you have paid, whether or not push is on. Our server does not even have a column to put them in.

Push reminders (off by default; you switch them on)

Once signed in you can have reminders delivered by email, and by LINE as well. This is the only feature that lets reminder data leave your computer, and it is off by default. If you do not turn it on, none of the following happens.

• What is uploaded: when each reminder should be sent, and the expiry date of that item. The server needs the time to fire at the right moment, and the date so the message can say something is expiring on the 25th. Without the date the notification could only say “you have 1 item expiring”, which says nothing. No URL, no amount, no text from the page is uploaded.
• Service names are a separate switch, also off by default. Leave it off and a push says “you have 2 items expiring”; you open the extension to see which. Our server does not hold those names either.
• Using LINE requires you to link it yourself: get a six-digit code in settings, add the official account as a friend, send it the code. We keep only the user identifier LINE gives us, so we know where to send messages; we cannot see your LINE name, photo or conversations. You can unlink in settings or simply block the account — either stops push immediately.
• Turning push off deletes the pending schedules on the server. Continuing to notify you after you switched it off would be us breaking our own promise.
• Desktop notifications are unaffected. Push is an extra layer, not a replacement — even if the email lands in spam, the reminder still appears on your computer.

We never touch your card details. Payment is handled entirely by ECPay; all we receive is whether the order was paid. That transaction is covered by ECPay's privacy policy.

10. Retention and deletion

Your reminders (on your own computer)

• Kept until you delete them. We hold no copy, paid or not.
• “Clear all data” in settings deletes every reminder and schedule at once. This cannot be undone.
• Removing the extension makes the browser delete its local storage with it.

Your account (only if you bought the paid tier)

• Contains your email address, licence record and payment records; kept until you ask us to delete it.
• Email us to have it deleted and we remove the licence and payment records with it. Reminders on your computer are unaffected — they simply revert to the free tier's reminder timings.
• Order numbers and amounts in payment records may need to be retained for a period under tax and accounting rules. That data contains no reminder content.

Shared lists (paid tier only)

• An invitation link is visible only at the moment it is generated; our database keeps a hash, and it expires after 7 days.
• When a member is removed or leaves, the sharing record is deleted outright, not flagged inactive, and any reminders they had scheduled for that list are cleared too.
• Deleting an account removes both the shares they created and the shares they belonged to.

11. Children's privacy

This extension is not directed at children under 13.

12. Changes to this policy

If a future version changes how data is handled, we will update this page and say so inside the extension. We will not change how your data is handled without telling you.

13. Contact

For anything privacy-related, email alan930604@gmail.com.