Data Isolation
Understanding how Fruga ensures complete data isolation for partners.
Why this matters
When you embed Relay into your platform, your users authenticate through you — not through Fruga directly. As a result, Fruga maintains a separate record for each user that is scoped entirely to your partner environment. This has important implications for data access, compliance, and deletion rights.
A user’s cashback history, coverage records, and payout details are only ever accessible within the context of your integration. No other partner can see or query this data, and neither can users of Fruga’s own products.
What this means in practice
From a compliance perspective, your users’ data sits in a dedicated logical partition. If a user exercises their right to erasure (GDPR Article 17), deletion requests are scoped to your partner context — they do not affect unrelated records elsewhere in the system.
From an integration perspective, you supply a userRef — your own internal user ID — when authenticating each user. Fruga maps all activity, balances, and records to that reference, within your partner scope. The same userRef across different partners would refer to entirely different users.