Skip to content

Security

What we read, what we keep, how we protect it, and how to stop us reading at any time.

What we read from Stripe

Sellers connect by installing the Earncrest app in their Stripe account. It asks only for read access: charges (which include refunds), disputes, account details, products, prices, Payment Links, and the events that tell us the app was uninstalled. The app can’t move money, issue refunds, create anything or change any setting, and Stripe enforces that, not us.

Stripe’s records include each customer’s contact details, and Stripe always sends them whole. We use only the billing email, in memory while the payment is read: to group payments by customer and to spot payments from the seller’s own address. We never store or log it, or any other customer detail.

What we read from PayPal

A seller who connects PayPal signs in to PayPal and gives Earncrest one permission: to search their transactions. We search with our own credentials, on the seller’s behalf, so we never hold a seller’s PayPal password or a token for their account. PayPal, not us, limits us to that search: we can’t move money, issue refunds or change anything.

PayPal’s sign-in link works for whoever it’s sent to, so signing in doesn’t prove the account is the seller’s. An account counts only once its owner is confirmed: straight away when the email address PayPal has for it is the seller’s own, or at a domain they’ve verified; otherwise from a link we email to that address, which works only for the seller who connected it, signed in with their second code. Until then we read nothing from it.

Each transaction comes with the payer’s details. We use only their PayPal account ID or email address, in memory while the transaction is read: to group payments by customer and to spot payments from the seller’s own address. We never store or log them, or any other customer detail.

What we keep

  • For each payment: its amount, currency, date, how much was refunded and any dispute’s status (for PayPal, each refund, dispute or hold against it). That’s what the figures are made from.
  • Who paid, and with which card (PayPal doesn’t say), each only as a keyed hash that’s different for every connected account, and whether the payment came from the seller’s own email address or domain. We never store a customer’s name, email address or card details.
  • The account’s business name and website (for PayPal, the legal name PayPal gives), to check it matches the seller.
  • The daily figures computed from all that.

Payment records are kept for 25 months on a rolling basis, and deleted as soon as an account is disconnected. Our database and servers are in London. The providers that send our emails and keep our analytics and error reports are listed, with where they are, in our privacy notice.

How we protect it

  • Stripe access tokens are encrypted with a key only the process that reads payments holds. The website itself can’t open them, and they never reach a browser, a log or an error report. For PayPal there’s no token to keep.
  • Admins sign in with a password and an authenticator app. Sellers sign in with a password and a second code: from an authenticator app if they’ve added one, otherwise one we email them each time. Either way, a seller’s account never opens with a password alone, or with an email inbox alone. Passwords must be at least 12 characters and are checked against known breaches.
  • Sign-in and emailed codes are rate limited and protected by a security check. On an account with an authenticator app, connecting Stripe or PayPal and other sensitive changes need a fresh code from it. If the password of an account without one is reset, which needs only its email, we remove what we read from Stripe or PayPal, or hold the account until we’ve checked with its owner, before anyone is let in.
  • The database refuses direct access from browsers: every read and change goes through our server, which checks who’s asking.
  • Every change an admin makes is recorded, and admins can’t edit any verified number.

Stopping access

You can stop Earncrest reading your Stripe account at any time, either way round: uninstall the Earncrest app from your Stripe dashboard, or disconnect the account on your Earncrest dashboard. Either one stops our access; disconnecting also deletes the payment records we kept. With PayPal, disconnecting on your Earncrest dashboard stops our reads and deletes the payment records we kept, at once; the permission stays in your PayPal account until you remove it there, but we don’t use it unless you connect PayPal again. Removing it in PayPal stops our access and deletes the records too, as soon as PayPal confirms it’s gone. Deleting your Earncrest account removes your certificate, payment records and login straight away. Our activity log keeps its entries about the account for 24 months, and our backups roll over within 7 days. And if a certificate was suspended or under a serious fraud flag when its account was deleted, we keep its Stripe and PayPal accounts’ IDs for 24 months, so the same account can’t simply be connected again to start afresh.

Reporting a vulnerability

If you think you’ve found a security problem, email support@virtascend.com with “Security” in the subject and enough detail for us to reproduce it. Please don’t access other people’s data, run automated scans that could disrupt the service, or share the problem publicly until we’ve fixed it. We’ll reply within a few working days.