Privacy Policy

1. Overview

This Privacy Policy describes how Nick Persico ("I", "me", or "my") collects, uses, and stores information when you use Robin at robin.closekit.com (the "Service"). By using the Service, you agree to the practices described here.

2. Information We Collect

From Close (via OAuth)

• Your Close user ID, name, and email address — used to identify your account within the Service.
• OAuth access and refresh tokens — used to authenticate API requests to Close on your behalf.
• Lead records from your Close account — read during polling operations to identify leads for assignment. Lead names and IDs are stored in Robin's assignment log to provide an audit trail.

From you directly

• Group and Lead List configuration — group names, member ordering, lead list names, and the Close filter queries you provide.

Automatically

• Assignment history — a record of each lead assigned, including the lead name, the Close user it was assigned to, and the timestamp. This forms the Activity Log.
• Polling metadata — timestamps of last check, lead list status, and error messages used to display status in the app.

3. How We Use Your Information

• To authenticate you via your Close account.
• To poll your Close account for leads matching your configured filters.
• To assign those leads to your team members in round-robin order via the Close API.
• To display assignment history, group status, and lead list activity within the app.
• To maintain your session while you are logged in.

We do not use your data for advertising, analytics, or any purpose other than operating the Service.

4. Data Sharing

We do not sell, rent, or share your personal information with third parties, except as necessary to operate the Service:

• Close CRM — we read lead data and update lead ownership via Close's API using the permissions you grant via OAuth.
• Fly.io — the Service is hosted on Fly.io. Data at rest is stored in a Fly.io-managed PostgreSQL database. See Fly.io's privacy policy.

5. Data Retention

Your account information, OAuth tokens, group and lead list configurations, and assignment history are retained for as long as you have an account with the Service. To request full deletion of your account and associated data, contact nick@closekit.com.

6. Security

OAuth tokens are stored in a private, encrypted-at-rest database. All connections to the Service use HTTPS. However, no method of transmission or storage is 100% secure. You are responsible for maintaining the security of your Close account.

7. Your Rights

You may revoke the Service's access to your Close account at any time via Close's OAuth settings. You may also request that we delete all data associated with your account by emailing nick@closekit.com.

8. Changes to This Policy

I may update this Privacy Policy from time to time. Continued use of the Service after changes are posted constitutes your acceptance of the revised policy.

9. Contact

Questions or requests regarding this Privacy Policy may be sent to nick@closekit.com.