*PRIVACY POLICY
what we collect, why, and the controls you hold. version 1.4 — effective november 14, 2026 (states first-party ads and the learning switch; under legal review).
WHO WE ARE
ASILUM ("ASILUM", "we") operates asilumapp.com — a taste discovery and social media service with a personal taste engine. Privacy questions and requests: legal@asilummagazine.com.
WHAT WE COLLECT
a pseudonymous device identity. a random identifier in a signed, http-only cookie plus a matching identifier in your browser's local storage. it is not your name and we do not link it to one unless you sign in.
an optional account. signing in uses a magic link, so we hold your email address. signing in moves your existing anonymous taste data under your account, once, with your action.
taste signals. stamps, likes, skips, searches, viewing time, corrections you give the Asterisk system, and moodboard training words. these build the taste profile that ranks your feed. learning is on by default; the "Learn from browsing" switch in Settings turns it off, after which only explicit actions (a save, a like) teach. pausing or erasing your memory works as before. you can inspect every class of this data in the Asterisk control room.
content you add. moodboard images are analyzed for color inside your browser — only the color summary and the file name reach our servers, never the image itself. wardrobe garment photos are different: with your explicit per-upload consent they are stored in a private bucket, served only through short-lived signed links, and erased — verifiably — when you delete them. body measurements you enter stay in the first-party fit engine; they are never sent to merchants or to any external model.
outside purchases. if you ask us to track a purchase made on an outside site, we store what you submitted, with your consent, under the disclaimer shown at the time.
native storefront records. if you open a Storefront, we store the public name, description, images and product facts you submit, plus private ownership, moderation, inventory and payment readiness records. provider account, payout, address and earnings details are never part of the public Storefront response. order, inventory-reservation, fee, refund and provider-reference records are retained as transaction and fraud-prevention evidence rather than being moved to another device identity or erased as personalization.
purchase info. if you pay a passenger fee, the name and address you enter once are stored in a purchase-info vault kept apart from the catalog and your taste record, used only to open checkout without retyping. your card goes to stripe, our payment processor — we store a reference and the last four digits for display, never a card number. the shipping address you give at checkout is stored on that order and used only to print the seller's USPS label. order records (what was charged, when, and its outcome) live in an append-only ledger.
technical records. rate-limit counters (stored as hashes, not identities), search queries for relevance improvement, and the security logs our hosting providers keep to run the site.
WHAT WE DO NOT DO
ads on ASILUM are first-party placements — medium cards, ticker links, BRDCST, and boosted listings — sold and placed by ASILUM itself. your personal data is never sold or shared with advertisers. no third-party ad networks, analytics, or tracking pixels. no cross-site tracking. ASTERISK+ members see no ads. no inference of sensitive traits, ever. no children's data — the service is not directed to children under 13 and we do not knowingly collect their information. no external AI model receives your personal data: every model integration in this product is switched off, and if one is ever enabled it will be opt-in, disclosed on the surface where it operates, and covered by an updated version of this policy.
WHO PROCESSES DATA FOR US
supabase (database, authentication, and private file storage; hosted in canada), vercel (site hosting, delivery, and security filtering), and stripe (payment processing for native Storefront orders, when enabled — card entry happens in stripe's own fields, and saved payment methods live with stripe, never with us). all act under our instructions to run the service — no other recipients.
COOKIES
essential cookies only: the signed device-identity cookie described above, the cookie that remembers your learning switch, and the short-lived security cookies our hosting sets when it checks that a visitor is not an abusive bot. there are no advertising or analytics cookies, which is why there is no cookie banner.
YOUR CONTROLS
see it: the Asterisk control room shows what the system holds and lets you export it as JSON. correct it: every recommendation carries correction controls that retrain or exclude. pause it: the Asterisk system guidance can be switched off; hard filters still apply and your data sits unused. delete it: Settings holds a typed-confirmation delete that removes personalization data — and the purchase-info vault with it — and wardrobe photos erase on demand, storage object first. settings → PURCHASE INFO also edits or erases your stored purchase details and removes the saved-card reference on their own. deleting your data is not conditioned on anything.
RETENTION
taste and content data persist while your profile is active and go when you delete them. purchase-info details stay until you erase them; order and hand-off ledgers are retained as transaction records. security and search records are kept for limited operational periods; the exact schedule is under final review and this policy will state it when fixed. we never keep deleted wardrobe photos — erasure is verified against the storage bucket before the request succeeds.
CHANGES
we will post any material change here with a new version number and effective date. continued use after the effective date means the new version applies.