How we handle your data
We're a cybersecurity-career platform. Our audience is unusually data-literate, and you should be able to read this page in three minutes and decide whether to trust us.
What follows is what we actually do today — not marketing copy and not a wish list. When something changes, this page updates in the same pull request.
Account & activity data
- Profile fields you fill in: name, email, job role, location, target roles, current skills, certifications obtained and planned, years of experience. All optional except email.
- AI conversation history — every prompt you send to the chatbot or career advisors, and every response we generate. Used to debug prompt quality and improve grounding.
- Activity logs — which tools you ran, which articles you saved, which quiz results you produced. Powers the dashboard's "recent activity" surface.
- Purchase records for paid reports (order ID, amount, currency, status). Payment is currently DuitNow / bank transfer with manual confirmation. When card payments via Stripe go live, we will not store full payment instruments — Stripe will hold those.
- Referral relationships if you share LumaShift with a peer using your referral link.
Things we won't do with your data
- We don't sell anything to recruiters. Your profile is not for sale to staffing firms, employers, or third parties. There's no "talent pool" we monetise behind your back.
- We don't share your resume or AI conversations with employers without you explicitly choosing to send them. The artifacts we generate are yours.
- We don't run third-party ad-network pixels. No Facebook Pixel, no Google Ads remarketing, no LinkedIn Insight tag. Our analytics is PostHog (see processors below) and Vercel platform telemetry.
- We don't enrich your profile with data from data brokers or scraped sources.
Who else sees your data
We use the following processors. Each handles a specific slice of data necessary to run the platform.
Specific infrastructure topology, regions, and versions are deliberately omitted from this public page — available to enterprise customers under NDA via lumashift@outlook.com.
| Processor | What it sees |
|---|---|
| Supabase | Database + authentication. All account data lives here. |
| Vercel | Hosting + edge compute. Sees request metadata (IP, user-agent) and request bodies in transit. |
| Groq | AI inference. Sees the prompts we send (your input + grounding context) and returns generated responses. |
| Stripe | Not yet active. Card payments are being onboarded — today, payment is by DuitNow or bank transfer with manual confirmation. Once live, Stripe will see email, name, and payment instrument; we will never store full card details. |
| Resend | Transactional email (digest, order delivery, password reset). Sees email and message body. |
| PostHog | Product analytics. Sees anonymised event data (page views, button clicks). No raw PII is sent — we use user IDs only. |
How long we keep things
We retain your account data — profile, activity, AI conversations, saved items — for the lifetime of your account. When you delete your account, the data is removed within 30 days from our active database. Backups roll off on a 60-day window.
To delete your account or request export of your data, email lumashift@outlook.com. We'll respond within 7 business days.
Anonymous session data (people who use free tools without signing up) is retained for 90 days and then deleted automatically.
How we run the platform
- Row-level security on the database. Every table that holds user data restricts reads to the row owner or to service-role (used only by trusted backend handlers like order processing and, once Stripe is live, its webhook).
- Per-user AI spend cap (100,000 tokens per hour by default). Prevents a compromised account from being weaponised as a token-burn vector.
- Continuous eval harness on our AI prompts. A daily cron alerts us if any prompt's rolling 7-run pass rate drops below 90%, so quality regressions surface quickly.
- Periodic security advisor scans via Supabase's linter. We treat ERROR-level findings as merge-blockers.
Found something?
If you've identified a security vulnerability, data exposure, or anything that looks wrong, email lumashift@outlook.com. We'll acknowledge within 48 hours and keep you in the loop on disposition.
We're a small team — no formal bug bounty yet — but we treat reports seriously and will credit you if you want public acknowledgment.
General contact