Privacy Policy
Effective October 26, 2026
This policy explains what information EZPZ Labs collects when you use RepIQ, TeamIQ and AgencyIQ and app.ezpzlabs.net, how we use it, who we share it with, and the choices you have. It applies to the Service described in our Terms of Service.
1. Who we are and the two roles we play
EZPZ Labs runs the Service. You can reach us at admin@ezpzlabs.net.
For your account details (name, email, sign-in), we decide how the information is used, so we are responsible for it. For the content a team puts into its workspace (offers, bookings, notes, prospect details and so on), the team that enters it decides what goes in and who can see it, and we process it on the team's behalf to run the Service.
2. Information we collect
- Account information: your name, email address, and the way you sign in. If you use a password, we do not see it in plain text; our sign-in provider stores it protected. If you use Google, we receive your name and email from Google. We also keep your theme choice and display name.
- Access requests: if you ask for access, the name, email address and optional note you submit.
- Team information: team and workspace names, which product the workspace uses, your role, who invited you, and invitation records (invited email address, role, and an expiry date; the invite link itself is stored only as a one-way hash).
- Workspace content: what you and your team enter into the products, which can include offers and their terms, bookings and shows, sets and triage, follow-ups, payment plans and commissions, call reviews and notes, training progress and answers, settings, and files you upload. This can include names, emails, phone numbers and other details of your prospects and customers. Some of it is private to you and some is shared with your team, depending on the feature.
- AI requests: the text the products send to the AI features (for example a drill answer, a role-play message or a call transcript) and the response. We do not keep a separate record of the text in our usage log; we log the type of request, the model tier, token counts, an estimated cost, which team and user made it, and when.
- Connections you choose to add: if you connect Fathom, the API key you give us and the meeting information and transcripts we fetch from Fathom on your behalf. If you connect Google Calendar, your Google account email and the calendar events we read with read-only access.
- Activity records: a log of important actions in a team (such as inviting or removing people, changing roles and connecting or disconnecting a service), with who did it and when.
- Technical information: your IP address and basic device and browser details are received by our hosting and sign-in providers when you visit, and your IP address is used to limit repeated requests. We do not use advertising or analytics trackers.
We do not collect payment card numbers. The Service does not process payments.
3. How we use information
- to create and run your account and your team’s workspace, and to show the right content to the right people;
- to send emails you need, such as sign-in links, password resets, confirmation emails and invitations;
- to power the AI features and the Fathom and Google Calendar connections when you use them;
- to keep the Service secure, prevent abuse, enforce usage limits and AI spending caps, and fix problems;
- to answer your requests and send you notices about the Service, including changes to our terms or this policy;
- to meet legal obligations and protect our rights.
We do not sell your information. We do not use your workspace content to show advertising, and we do not use it to train AI models.
4. Who can see your content inside the Service
Teams are separated from each other: one team cannot read another team's workspace. Inside a team, people with the Owner, Admin or Manager role can see the team's shared content, and Reps and Setters see what the role allows. Content that a feature marks as private to you is readable only by you. Fathom keys and Google tokens are never shown to anyone in the Service, including team Owners and Managers.
An agency that runs several client teams can reach the client workspaces it manages.
A small number of EZPZ Labs platform administrators can view workspace data in a read-only view for support and security. They cannot change your data, and they cannot see your stored API keys or tokens (your Fathom key and Google token) or your Google Calendar data.
6. Google user data
If you connect Google Calendar, we ask for read-only access to your calendar (the calendar.readonly scope) plus your email address and basic identity (openid and email). We use calendar events only to show and sort your booked calls into the right offer inside the Service, with internal meetings left out. We use your Google email only to show which account is connected.
We keep a Google refresh token so the connection keeps working; it is encrypted before it is stored. Short-lived access tokens are held only in server memory and are not sent to your browser. We do not sell Google user data, use it for advertising, or use it to train AI models, and we do not let people read it except as needed to provide the feature to you, for security, or to follow the law. EZPZ Labs's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. You can disconnect Google Calendar in Settings, or remove the app's access at myaccount.google.com/permissions.
7. Fathom
If you connect Fathom, you give us a Fathom API key. We store it encrypted and use it only to list your meetings and read transcripts when you or the product ask for them. Call recordings and transcripts can contain other people’s words and details. Make sure you have the right to record and use calls, including any consent the law requires. You can disconnect Fathom in Settings, and you can delete the key in your Fathom account.
9. How we protect information
Information is sent over encrypted connections. Access to data is limited by team and role in the database itself, and the product pages run on a separate address and cannot read your sign-in session. Fathom keys and Google tokens are encrypted before they are stored. AI requests, connection requests and access requests are rate limited, and important actions are logged.
No system is perfectly secure, and we cannot promise absolute security. Choose a strong password, keep it private, and tell us at once if you think your account was used by someone else.
10. How long we keep information
We keep account and workspace information while your account or team is active. When a user account is deleted, we delete their profile, memberships, private content and saved connections. When a team or workspace is deleted, we delete its workspace content, and we will remove its uploaded files on request. Some records are kept in anonymous form (for example AI usage totals) or for legitimate record-keeping (the activity log).
Deleted information can remain in our providers’ backups for a limited time until they are overwritten. Access requests and invitation records are kept until they are no longer needed.
You can ask us to delete your account or your team’s data by emailing admin@ezpzlabs.net. A team’s Owner can ask for the whole team’s data. We may need to confirm it is you first.
11. Your choices and rights
You can ask us to tell you what we hold about you, to correct it, to delete it, or to give you a copy, and you can ask us to stop using it in some ways. You can also export your workspace data from the products with the Export button. To make a request, email admin@ezpzlabs.net. We will answer within the time the law requires.
If you live in a place with data protection laws (for example the European Economic Area, the United Kingdom or a US state with a privacy law), you may have additional rights, including the right to complain to your local regulator. We will not treat you differently for using your rights.
If your information is in a workspace run by another team, the team’s Owner decides what happens to it, so we may direct your request to them.
12. Where information is processed
EZPZ Labs is based in the United States, and our providers process information in the United States and possibly other countries. If you use the Service from outside the United States, your information will be transferred to and processed in the countries where we and our providers operate, which may have different data protection laws than yours.
13. Children
The Service is for businesses and adults. It is not meant for anyone under 18, and we do not knowingly collect information from them. If you think a child has given us information, email admin@ezpzlabs.net and we will delete it.
14. Changes to this policy
We may update this policy. When we make a material change, we will tell you by email or in the Service before it takes effect. The date at the top of this page shows when it was last updated.
15. Contact
Privacy questions and requests: admin@ezpzlabs.net.
Also see our Terms of Service.