EZTipr
    Security & Compliance

    Built securely. Audited continuously.

    From Row-Level Security in our database to Stripe-PCI payments and full audit logging on every org action — security is a first-class feature of EZTipr, not an afterthought.

    How requests flow

    A small, auditable surface area.

    Fewer moving parts, fewer places for data to leak. Here's every system that touches an EZTipr request.

    Row-Level Security on every table

    Every database query is filtered by Postgres Row-Level Security policies tied to the authenticated user. RLS alone isn't enough — we also explicitly GRANT only what each role needs.

    JWT-validated edge functions

    Every privileged backend action runs in a Supabase edge function that validates the caller's JWT before touching data or third-party services.

    Encrypted secrets, in transit & at rest

    API keys, OAuth tokens, and Stripe credentials live in the secrets vault — never in client code. Traffic uses TLS end-to-end. Database is encrypted at rest.

    Public profile IDs, private auth IDs

    Public tip pages expose a separate profile ID — never your internal Supabase auth UUID — so user enumeration attacks can't pivot from a tip page to your account.

    Audit log on every org action

    Invitations, role changes, removals, and admin promotions are all written to an immutable audit log visible to org admins.

    Clickjacking protection

    A framebusting script ships in the page shell so malicious sites can't embed your tip page in a hidden iframe to capture taps.

    PCI-compliant payments

    Subscription payments flow through Stripe, a PCI-DSS Level 1 provider. EZTipr never sees raw card data. Tip payments are peer-to-peer through Cash App, Venmo, PayPal, etc. — we don't touch that money either.

    Account deletion you can trust

    Deletion runs through a dedicated edge function: account removed from auth, profile cleared from the database, Stripe subscriptions canceled — all atomically.

    Compliance posture

    EZTipr inherits enterprise controls from its underlying providers and adds product-level protections on top.

    Stripe
    PCI-DSS Level 1
    Supabase
    SOC 2 Type 2
    Hosting
    AWS regions
    Privacy
    GDPR / CCPA aligned

    Responsible disclosure

    Found a vulnerability? Email info@eztipr.com with the subject line "Security". We acknowledge reports within 2 business days and credit researchers who request it.

    Security FAQs

    Not today. We inherit Supabase's SOC 2 Type 2 controls for our database, auth, and edge functions, and we inherit Stripe's PCI-DSS Level 1 controls for subscription payments. Independent certification of EZTipr itself is on the roadmap as the company scales.

    See also our Privacy Policy and Terms of Service.

    Security questions for your team's vendor review?

    We answer infosec questionnaires and provide details on request.