# Browser storage and host logs

- Page: https://swiftcodelookup.com/browser-storage-and-host-logs/
- Read on: 2026-10-24

A BIC, an IBAN or a pasted column of codes is tested by JavaScript running in the open tab. Those characters are never uploaded, logged or forwarded, so no one behind swiftcodelookup.com reads them.

## Names kept in localStorage

The site sets no cookies of its own. Whatever it keeps goes into localStorage on this device, under the names in the table. A code typed into a checker is only kept after you press Save or tap an empty memory slot.

| Entry | Contents | Retention | Removal |
|---|---|---|---|
| `deck:` + page path + `:` + checker name | Up to five memories for that checker, each with the name you gave it, the fields, the ticked boxes and the view in use | Until you delete it | Delete on one memory, Clear all for every one, or clear this site's stored data in the browser |
| `deckmode:` + site address | The view you picked: Code only, Cross-check or Show the math | Until you pick another | Pick a view again, or erase site data |
| `sc-safe` | Which warning signs are ticked in the red-flag check | Until you untick them | Untick the boxes, or erase site data |
| `theme` | Dark or light, as chosen with the theme switch | Until you go back to the system setting | Choose the system setting, or erase site data |
| `look` | Classic or Nova, the two page styles | Until you switch | Use the style switch, or erase site data |
| Cache Storage, `v-` + version | Offline copies of the checker's pages, scripts and fonts, so it opens with no signal | Replaced each time the site is republished | Erase site data; uninstalling the app clears it too |

The theme and style choices also go into `window.name` for this tab (keys `thm-theme`, `lk-look`), which carries them from page to page when localStorage is unavailable. Closing the tab discards them.

One step in the browser's settings removes all of it: erase stored data for swiftcodelookup.com. The host may place its own security cookie to turn away automated attacks; it is strictly necessary and does not follow you anywhere.

## Traffic the hosting network handles

Pages reach you through the network that hosts the site. To deliver them and filter out abusive traffic, that network must process each request: your IP address, the address asked for, the time and the browser's description of itself. GDPR Article 6(1)(f), legitimate interests, covers this: serving pages and shielding them from attack. The provider handles that traffic under its own privacy policy. On the site's side there is no visitor list, no analytics, no advertising and no outside script, and no request data feeds a profile of anyone.

## Email you send, and when it is deleted

The one route by which the operator gets personal data is a message to contact@swiftcodelookup.com: the sending address, a signature name if you add one, and the text. Both the EU GDPR and its UK version allow this on Article 6(1)(f) as well, because reading, answering and acting on a reported mistake is a legitimate interest. The thread stays while the exchange is open and is deleted once nothing in it awaits a reply. It is never sold, never handed to an advertiser and never put on a mailing list.

## Your rights, and where to complain

GDPR Articles 15 to 18 let you ask for a copy of what is held from you, a fix, its deletion, or a pause on its use, and Article 21 lets you object. Any of these goes to contact@swiftcodelookup.com.

Article 77 of the GDPR lets you go straight to a regulator, with no need to write here before. Residents of the EEA (EU members plus Norway, Iceland and Liechtenstein) can pick the authority of the state where they live or work, or where the issue arose. Those authorities are named by the European Data Protection Board on its [members page](https://www.edpb.europa.eu/about-edpb/our-members). UK residents go to the ICO (Information Commissioner's Office) through its [complaints page for data protection](https://ico.org.uk/make-a-complaint/data-protection-complaints/).

When this page is rewritten, the date below moves on and the revision dates page records the change.

Revised 2026-10-24

---
SWIFT Code Guide. Errors or changed codes: contact@swiftcodelookup.com