Originally Posted by
sehgalanuj
You could just make it a question in the settings for now too, i.e. when did you acquire your current status. Since the statement goes back only so far as 3 years, this could help down the road.
I'll continue playing with it and see what else I find.
Good catch on the SOC2 certification. You’re right that it’s only for the Team plan. For the data I’m storing (flight history, XP calculations), I consider the risk acceptable, but thanks for pointing this out for transparency.
For RLS documentation:
https://supabase.com/docs/guides/dat...level-security
It’s a PostgreSQL feature that Supabase makes easy to enable. Each table has policies like:
```sql
CREATE POLICY "Users can only see own data"
ON flights FOR SELECT
USING (auth.uid() = user_id);
```
PFL Tracking: that’s a great suggestion! For now, users can set their starting status to Platinum and starting XP to whatever they had at cycle start. But tracking consecutive years for PFL qualification (haven’t implemented that) is definitely on my radar. You’re right that a simple ‘When did you first reach Platinum’ question could work as a stopgap until I can detect it from the statement history.
I hope you have more success with the PDF parser. It’s killing me. I got it to work perfectly in Dutch, but with multiple languages, multiple currencies, and 100,000 variables, suddenly nothing works properly anymore. So I’m rebuilding it from scratch in my test environment. With smarter logic.