Legal
Privacy Policy
Perfectigo is the CRM and outreach part of MyAIStaff. It is operated by MyAIStaff LLC, Las Vegas, Clark County, Nevada, USA (“Perfectigo”, “we”, “us”). This policy explains what personal information Perfectigo handles, why, who else touches it, how long we keep it, and the choices you have.
1. What this policy covers
- The Perfectigo web app at app.perfectigo.com and its API at api.perfectigo.com, including the public Contacts and Events APIs.
- The Perfectigo mobile apps for iPhone and Android, including versions published for a customer under the customer’s own name and brand (section 14 adds what is specific to them).
- The pages and widgets we host for our customers: consent widgets on their websites, offer pages, booking pages and intake forms, and the unsubscribe and tracking links in the emails and texts they send.
- This website, perfectigo.com.
It does not cover MyAIStaff’s AI-agent product, which has its own policy at myaistaff.com/privacy-policy, or our customers’ own websites and businesses, which have theirs. Our Terms of Service are the agreement between us and our customers; this policy is part of them.
2. Two kinds of people, two roles
Customers are the businesses that sign up for Perfectigo, and the team members they invite (“you” in most of this policy). For your account, we decide how your information is used: we are the controller.
Contacts are the people in a customer’s database: people who receive a customer’s emails or texts, fill in its forms, book a time with it, opt in on its website, or were captured at an event. That information belongs to the customer. We hold and process it only to run Perfectigo for that customer and on its instructions: we are its processor (in US terms, its service provider). The customer is responsible for having a lawful basis — usually your consent — to contact you.
If a business contacted you through Perfectigo: every marketing email it sends has an unsubscribe link, and you can stop its texts by replying STOP. For anything else — seeing, correcting or deleting what it holds about you — contact that business. If you cannot reach it, write to us at admin@perfectigo.com and we will pass your request on and help it respond.
3. What we do not do
- We do not sell personal information, and we do not share it for cross-context behavioural advertising.
- We do not use contacts’ information to market our own products, and we never mix one customer’s contacts with another’s.
- There is no advertising in our websites or apps: no ad networks, no advertising SDKs, no advertising pixels. Our apps do not track you across other companies’ apps or websites, and the iOS app does not use the advertising identifier.
- There are no third-party analytics or session-recording tools in the web app or on perfectigo.com, and perfectigo.com sets no cookies at all.
- We do not train AI models on your information. Perfectigo’s AI features run through the customer’s own OpenAI account (section 8).
4. Information about customers and their team
- Account: your name and email address, your password (stored only as a one-way hash, never as text), the workspaces you belong to and your role in each.
- Workspace settings: the organization’s name, time zone and logo, its sender names and email addresses, legal name, mailing address, privacy-policy link, and the reason recipients are given for receiving its emails. Some of these are printed in the footer of every marketing email a workspace sends, because the law requires it.
- Account branding: the product name, theme colour, logos and icon that an account holder sets for their workspaces.
- Connected accounts: the credentials you enter for Mailgun, Twilio, OpenAI, Apollo or EventPlus. They are stored encrypted and used only to do what you ask.
- API keys and tokens: their names and permissions. Secret keys are stored only as hashes we cannot reverse.
- Activity: an audit log of significant actions in a workspace — who changed a setting, invited or removed a member, or scheduled or sent a campaign, and when.
- Support: what you send us when you write to us.
- Technical information: IP address, browser or device details and request times in our server and security logs, used to keep the service running and safe.
5. Information our customers keep about their contacts
Depending on which features a customer uses, its workspace can hold:
- Contact details: name, email address, phone number, company, job title, city, region, country, time zone, LinkedIn and other profile links, and any custom fields the customer defines; plus tags, lists, segments, lifecycle stage, pipeline stage, deals, notes, and which team member the contact is assigned to.
- Consent records: for each opt-in, the channel (email or SMS), the exact wording that was shown, the date and time, the IP address and browser details, and where it happened. They are kept as evidence that the person agreed. Opt-outs are kept too, so they can be honoured: unsubscribes, spam complaints, bounced addresses, and texts stopped with STOP.
- Messages and engagement: which campaigns were sent to the contact and whether they were delivered, opened or clicked. Opens are detected with a small image in the email and clicks through a redirect link; links in texts are shortened and counted the same way.
- What a contact submits: answers to a customer’s intake form; a booking (name, email, phone, notes, the time chosen and time zone); an opt-in on an offer page or a consent widget.
- What a customer imports or connects: CSV files; contacts and events its own systems send through our API — for example a sign-up, an order and its amount, or a plan change; and leads from EventPlus, which can include a photo, a picture of a business card or a short video captured at an event.
- What a customer’s team captures at events with the mobile app: a photo of the business card someone handed over, a photo of the two of them together, short videos, the event where they met (its name, city, venue and dates) and when, and the rep’s notes — and, if the rep lets the app use the phone’s location, where each photo or video was taken (section 14).
- Enrichment, if the customer runs it: job, company and location details that Apollo returns about the contact and their employer.
6. How we use information
- To provide Perfectigo: store and organise contacts; send the emails and texts a customer schedules; record consent; enforce opt-outs, suppression lists and SMS quiet hours; run automations, booking pages and forms; and report results to the customer.
- To keep it secure and working: sign-in, rate limits, abuse prevention, troubleshooting and backups.
- To communicate with customers about their account: invitations, password resets, security notices and important service updates. We never send contacts anything on our own behalf.
- To meet legal obligations and enforce our Terms.
7. Legal bases (EEA and UK)
Where data-protection law such as the GDPR applies, we rely on: contract, to provide your account; legitimate interests, to secure and operate the service and prevent abuse; legal obligation, where the law requires us to keep or disclose something; and consent, where we ask for it. For contacts’ information, the customer is the controller and decides the legal basis.
8. Who we share information with
Providers we use to run Perfectigo
| Provider | What for | Where |
|---|---|---|
| Amazon Web Services | Hosting, database, file storage and backups | United States (Virginia) |
| Cloudflare | DNS, encryption in transit and network protection for our domains; hosting of perfectigo.com | Global network |
| Brevo | Sending our own account emails: invitations, password resets, welcome and security notices | European Union |
| Expo | Delivering notifications to the mobile apps, if you allow them; it holds a push token for your device | United States |
| OpenStreetMap | Drawing the map of where a photo or video was taken, in the web app’s media library — only when a member asks to see the map, which sends that place’s coordinates from their browser to OpenStreetMap | United Kingdom |
Providers a customer connects with its own account
Information goes to these only when a customer sets them up, and under that customer’s own agreement with the provider.
| Provider | What for |
|---|---|
| Mailgun | Sending the workspace’s email campaigns and booking emails, and reporting deliveries, bounces and complaints |
| Twilio | Sending the workspace’s text messages, and receiving delivery reports and STOP replies |
| OpenAI | AI features: drafting content and campaign ideas; reading the text on a business card or event banner photographed in the mobile app, which sends that photo; and personalizing a message for a recipient, which sends the message and that recipient’s name, email address and up to ten custom fields |
| Apollo.io | Enrichment: looking up a contact’s job and company from their email address, name and company website |
| EventPlus | Sending leads captured at events into the workspace |
Otherwise
- Inside a workspace: its members see contacts according to their role, and a member can be limited to the people assigned to them.
- When the law requires it, or to protect the rights, property or safety of our customers, contacts, the public or ourselves.
- In a merger, acquisition or sale of all or part of our business, where the information stays protected by this policy.
- With your consent.
9. Cookies and browser storage
| Where | What | Why |
|---|---|---|
| app.perfectigo.com and api.perfectigo.com | laravel-session cookie, two hours | Keeps you signed in. Strictly necessary. |
| app.perfectigo.com and api.perfectigo.com | XSRF-TOKEN cookie, two hours | Protects your account against cross-site request forgery. Strictly necessary. |
| The web app | Browser storage (not cookies) | Remembers your light or dark theme, whether the sidebar is collapsed, how you lay out the media library (grid or list, the details panel, whether to show maps), and your account’s colour and logo so the app opens in them. Never sent to us. |
| Booking, form and offer pages we host for customers | Nothing | They set no cookies. |
| A customer’s consent widget | Browser storage, only if you close a slim bar | So the closed bar stays closed on that site. The widget sets no cookies. |
| Emails a customer sends | A tracking image and redirect links | Tell the customer whether its email was opened and which links were clicked (section 5). |
| The mobile apps | No cookies; a sign-in token in the device’s secure storage | Keeps you signed in until you sign out, or for at most a year (section 14). |
| perfectigo.com | Nothing | No cookies, no browser storage and no third-party requests. |
10. International transfers
We are based in the United States and store data there. If you use Perfectigo from elsewhere, your information is transferred to and processed in the United States, and by the providers in section 8 in their locations. Where the law requires a transfer mechanism, we rely on the data-processing terms, including standard contractual clauses, that those providers offer.
11. How long we keep information
- Customer accounts: while the account exists. When you ask us to delete it, we do so within 30 days — see perfectigo.com/delete-account — except anything the law requires us to keep.
- Contacts’ information: for as long as the customer keeps it. Customers can delete contacts at any time, and when a workspace is deleted its contacts go with it.
- Photos and videos captured with the mobile app: kept with the contact and erased with them; an event video is kept until it is deleted.
- Consent records and opt-outs: for as long as the workspace exists, even after a contact is deleted. They are the evidence that permission was given, and an opt-out has to be remembered to be honoured.
- Automated database backups: seven days, after which they are overwritten.
- Exports: download links expire after 24 hours.
- Sign-in sessions: end after two hours without activity.
- Server and security logs: kept for a limited period for troubleshooting and security, then deleted.
12. Security
- All traffic is encrypted in transit (HTTPS). The database is encrypted at rest, and the credentials of connected accounts are encrypted again inside it. Passwords and API secrets are stored only as one-way hashes.
- Each workspace’s data is kept separate from every other workspace’s. Inside a workspace, access follows roles, and significant actions are logged.
- Unsubscribe, tracking and download links are signed, so they cannot be forged or used to look up anyone else.
No system is perfectly secure. If a breach affects your information, we will tell you, and the authorities, as the law requires.
13. Your rights and choices
- Customers can see and correct their information in the app, export their contacts as a CSV file, delete contacts, and ask us for a copy of their account information or to delete their account (how to delete your account).
- Contacts can unsubscribe with the link in any marketing email, reply STOP to any text, or ask the business that holds their details. If you write to us instead, we will forward your request to that business and help it respond.
- Depending on where you live — for example the EEA, the UK, California or another US state with a privacy law — you may have the right to access, correct, delete or receive a copy of your information, to object to or restrict how it is used, to appeal our decision on a request, and to complain to your data-protection authority. Californians also have the right to know what we collect and to opt out of its sale or sharing; we do neither. We will not treat you differently for using any of these rights.
To make a request, email admin@perfectigo.com. We will confirm it is you — usually by writing back to the email address on the account — and respond within 30 days, or sooner where the law requires. You may use an authorised agent; we will ask for proof of their authority.
14. The mobile apps
Our iPhone and Android apps are for our customers’ team members — for example a sales rep at a trade show. They sign in with their Perfectigo account; there is no sign-up in the apps, because people join a workspace by invitation. Some customers have the app published under their own name and brand; it works the same way, and this policy applies to it. Everything else in this policy applies to the apps too, and in addition:
- What the apps are for: capturing the people a rep meets at an event — by photographing a business card, scanning a QR code or typing details in — adding a photo or a short video, writing follow-up notes, moving people along the customer’s sales stages, and showing the rep’s own contact card as a QR code that someone else can scan to save it. What is captured goes into the customer’s workspace, where section 5 applies and the customer controls it.
- Reading cards and banners: a photographed business card or event banner is sent to the workspace’s AI provider (OpenAI, through the customer’s own account) to read the text. The rep checks what was read before a contact is saved.
- Permissions are asked for when a feature first needs them — location once, after you first sign in — and you can change them at any time in your device settings. Camera: to scan cards and QR codes, take photos and record videos. Microphone: only for the sound of a video you are recording. Photo library: to attach photos or videos you choose. Location, while you use the app: to note where a photo or video is taken (below). Notifications: if you allow them, the app gets a push token for your device from Expo, which delivers notifications to iPhone and Android, and we store it to alert you about your workspace.
- Where a photo or video was taken: if you allow it, the app reads your phone’s location at the moment you take a photo or video with someone you meet — never in the background — and keeps it with that photo or video: the coordinates, how precise the phone says they are, and the place’s name (city, region and country). The name comes from your phone’s own location service (Apple’s on iPhone, Google Play services on Android); we do not send your location anywhere to look it up. Your workspace’s members see it with the photo in the media library, where a map is drawn by OpenStreetMap only when someone asks for one (section 8). The app asks once, and says why first; you can turn it off at any time in your phone’s settings, and photos you take after that have no place. It is deleted with the photo or video. An event’s own city and venue are whatever is typed in.
- Your sign-in is a token kept in the device’s secure storage. It lasts at most a year and is deleted when you sign out, and you can see and revoke a phone’s access in the web app under Settings → API tokens. It reaches only what the app needs — contacts, the CRM and reading cards — never your workspace’s members, keys or account settings.
- No advertising, analytics or tracking. The apps contain no advertising, no third-party analytics and nothing that tracks you across other companies’ apps or websites; the iOS app does not use the advertising identifier.
- Deleting your account: see perfectigo.com/delete-account. A workspace Owner or Admin can also remove you from their workspace, which signs the app out on its next request.
15. Children
Perfectigo is a business tool for adults. It is not directed to children under 16, and we do not knowingly collect their information. Customers must not use Perfectigo to market to children. If we learn that we hold a child’s information, we will delete it.
16. Changes to this policy
We will post any new version here with a new date. If a change is significant, we will tell customers by email or in the app before it takes effect.
17. Contact us
MyAIStaff LLC (Perfectigo)
Las Vegas, Clark County, Nevada, USA
Email: admin@perfectigo.com
Questions about this policy, privacy requests and account deletion requests all go to the same address.