Cookie Inventory
Below is the full list of cookies, storage keys, and related data mechanisms used by the Registration Town platform.
| Origin | Type | Key / Cookie Name | Purpose | Category | Consent Required |
|---|---|---|---|---|---|
| Registration Town (first-party) | localStorage | app.selectedLanguage | Store user language preference | Functional | No |
| Registration Town (first-party) | localStorage | consent.cookies.version | Record cookie consent version | Essential | No |
| Registration Town (first-party) | localStorage | Meteor.loginToken | Persistent login | Essential | No |
| Registration Town (first-party) | localStorage | Meteor.loginTokenExpires | Login expiry | Essential | No |
| Registration Town (first-party) | localStorage | Meteor.userId | Identify user | Essential | No |
| Registration Town (first-party) | sessionStorage | consent.cookies.version | Session-level cookie consent | Essential | No |
| Registration Town (first-party) | indexedDB | MeteorDynamicImportCache | Dynamic module loading | Functional | No |
| Registration Town (first-party) | cookie | __stripe_mid | Stripe fraud detection | Analytics | Yes |
| Registration Town (first-party) | cookie | __stripe_sid | Stripe session ID | Analytics | Yes |
| Registration Town (first-party) | cookie | AWSALB | Load balancing | Essential | No |
| Registration Town (first-party) | cookie | AWSALBCORS | Load balancing for CORS | Essential | No |
| m.stripe.network | sessionStorage | * | Stripe internal session management | Analytics | Yes |
| m.stripe.network | cookie | m | Stripe user tracking | Analytics | Yes |
| pay.google.com | cookie | NID, SOCS, etc. | Google Pay session & fraud detection | Analytics | Yes |
| b.stripecdn.com | cookie | __Secure-ENID | Stripe fraud prevention | Analytics | Yes |
| newassets.hcaptcha.com | cookie | __cf_bm, hmt_id, etc. | CAPTCHA functionality | Essential* | Maybe |
| facebook.com / meta.com | cookie | _fbp, fr, datr, etc. | Page view, event tracking, session linking | Analytics | Yes |
Note: Essential classification for third-party tools depends on how they’re used. For example, CAPTCHA may be essential if required for login or payment protection.