Privacy Policy

Effective 5 September 2026

AWS Login Scheduler is a Chrome extension that signs in to the AWS console on a schedule you set. This policy describes exactly what it stores and what it does with it. The short version: everything stays on your own computer, and there is no server to send it to.

What the extension stores

For each AWS profile you create, it saves:

• the profile name you chose;
• the AWS account ID or account alias;
• the IAM username;
• the AWS destination to open, and a region where one applies;
• the schedule: days, time, timezone, and whether it is enabled;
• whether an existing AWS session should be preserved or replaced;
• the outcome of the most recent run — a status, a timestamp, and a short diagnostic trail.

Separately, it saves the credentials you enter:

• your AWS password;
• if you use TOTP multi-factor authentication, the authenticator secret and its parameters.

Where it is stored

In the extension's own local storage, on the device where you installed it. Nowhere else. It is not synced to your Google account, not backed up to any service operated by us, and not sent anywhere.

Credentials are stored unencrypted. They are not encrypted at rest. No web page and no other extension can read them, but any program running as your operating-system user can, and so can anyone with a copy of your Chrome profile directory or a disk backup. This is a deliberate, documented limitation — see Security for why it exists and what to do about it.

What is transmitted

Nothing. The extension has no backend. It sends no analytics, no telemetry, no crash reports and no usage statistics. It loads no code from a remote server; everything it runs ships inside the installed package.

The only network activity it causes is your browser navigating to signin.aws.amazon.com and console.aws.amazon.com to sign you in — the same requests your browser would make if you typed the address yourself. Your credentials go to Amazon, over HTTPS, and to nobody else. What Amazon then does with them is governed by the AWS Privacy Notice.

Multi-factor codes are generated on your device. If you set up an authenticator by uploading a QR image, that image is decoded locally and never uploaded.

Third parties

There are none. Your data is not sold, rented, transferred, or shared. It is not used for advertising, profiling, or to train any model. No third-party service receives it, because nothing leaves your device.

Retention and deletion

• Deleting a profile deletes its credentials along with it, immediately.
• Removing the authenticator from a profile deletes the stored TOTP secret.
• Uninstalling the extension deletes everything it saved. Chrome removes an extension's storage when the extension is removed; there is no residue to clean up and no copy held elsewhere.

Permissions, and why each one is requested

storage

To save your profiles and credentials on this device. This is the only place they exist.

alarms

To wake the extension at the times you scheduled. Chrome's alarm API is the only way an extension can run at a future time.

scripting

For one narrow case: re-inserting the extension's own page script into an AWS tab after a browser or extension reload has orphaned it. It is never used to inject code into any other site.

Access to signin.aws.amazon.com and console.aws.amazon.com

To fill the AWS sign-in form, confirm which account the resulting session belongs to, and open the destination you configured. These are the only sites the extension can read or act on. It cannot see any other tab.

The extension deliberately does not request the tabs permission, which would grant visibility into your browsing across all sites. It does not need it, so it does not ask.

Children

The extension is a tool for people who administer AWS accounts. It is not directed at children and collects nothing about them.

Changes to this policy

If the extension's data handling changes, this page changes with it and the effective date above is updated. Material changes will be described in the extension's release notes.

Contact

Questions about this policy, or about what the extension does with your data: REPLACE-ME@example.com.