Storing data outside Kit

RSG has to hold some of your Kit data outside Kit. This page explains what leaves Kit, why it has to, and what RSG does to keep it small. You are asked to agree to this when you connect your account.

What leaves Kit

• —The Kit subscriber ID of anyone RSG has matched to a Stripe customer, and the email address the two were matched on.
• —The IDs and names of the tags RSG created, and the ID of any sequence you asked it to protect.
• —The exclusion settings on those sequences, as IDs — so RSG can tell whether they still match what it wrote.
• —Your Kit account ID and name.

Nothing else does. RSG does not copy your subscriber list, your custom fields, your email content, your broadcasts or your purchase history.

Why it has to

RSG's job is to notice when Stripe and Kit disagree — someone has paid, but is still in a payment reminder sequence. To do that it has to know which Stripe customer is which Kit subscriber, and it has to remember what it wrote so it can check afterwards that the write actually landed. Neither is possible without holding those identifiers.

The email address is held for one reason: it is what the match was made on. If it changes, RSG stops and asks rather than moving someone's state onto a different subscriber.

How it is protected

• —Your data is separated from every other account at the database level, not just in application code.
• —Access credentials for Kit and Stripe are encrypted with a key stored separately from the database.
• —Webhook deliveries from Kit are signature-verified before anything is read from them.
• —Nothing that could identify a person is written to logs or error reports.

Getting it back out

Disconnect from the Setup page. RSG removes its own tag from your sequences' exclusion settings and deletes its webhook while it still has access, then erases your data within 30 days. Your subscribers keep every tag they have. See Privacy for the full retention periods, or email masanori.iwata@orumio.com to have it removed sooner.