Your information
inFLO Privacy Policy
Effective October 13, 2026
How we handle customer information, connected email, files, and scheduling in our event-management system.
Who we are
Pop Pop Balloon operates inFLO, also called Pop Pop Balloon CRM, to manage inquiries, event projects, customer communications, documents, payments, and crew schedules. This policy covers information processed through inFLO and its connected services. It does not replace another website’s or provider’s privacy policy.
Information we collect and use
We process contact and organization details; event dates, locations, access instructions, and schedules; service selections; inspiration photos and mockups; messages; quotes and contracts; and payment, refund, and tip records. These may come from customers, authorized team members, or connected services. We use them to respond to requests, prepare and fulfill orders, coordinate work, maintain business records, and provide customer support.
Staff sign-in and access records, activity history, and technical logs support account access, troubleshooting, and security. Cookies and browser storage support sign-in, preferences, and restoring unfinished forms. Our page fonts are loaded from Google Fonts, which receives the browser requests needed to provide them.
Gmail and Google Calendar
When the account owner connects Google, inFLO requests permission to identify the connected account, read Gmail messages and attachments, send email, and manage events on calendars the account owns. inFLO uses these permissions for its inbox, customer and event matching, reply tracking, follow-ups, file imports, and scheduling. Connection credentials are stored in encrypted form so authorized background work can continue without repeated sign-in.
Email information can include sender and recipient addresses, subject lines, message bodies, dates, thread identifiers, and attachments. Calendar information can include event titles, dates, times, locations, and descriptions. Saved email and calendar information may be available to authorized team members according to their roles.
Routine Gmail catch-up currently starts with the last 14 days and then processes new changes. This is a synchronization window, not a deletion policy: older saved messages remain, and staff-requested live Gmail searches can retrieve older messages. Selected email attachments can be copied into project files.
Email is sent through the connected account when authorized staff send it or enabled business automations dispatch it. Calendar synchronization can create, update, or remove entries as business records change.
AI-assisted work
inFLO uses the OpenAI API for its staff AI assistant and AI-assisted automated-message drafting. Depending on the feature, requests can include customer and project directory details, schedules, instructions, conversation excerpts, live Gmail search or thread results, and selected images or PDFs. This processing helps summarize correspondence, draft messages, and carry out authorized CRM work. AI-assisted automation may run in the background when those features are enabled; it is not limited to staff opening the assistant.
The app requests that these API responses not be stored using the API’s store: false setting. That setting does not mean all provider processing or security-log retention is disabled. Provider handling remains subject to the applicable service terms and account settings.
We do not use Google Workspace data to train, develop, or improve general-purpose or non-personalized AI models. AI outputs can be inaccurate and should be reviewed before relying on them.
Retention, disconnection, and deletion
inFLO retains saved business records and files until they are removed or otherwise managed for business, legal, accounting, or dispute-resolution needs. It does not automatically delete saved email when it becomes older than 14 days. Different records may need different retention periods.
The account owner can disconnect Google in inFLO Settings. This removes the saved connection and attempts to revoke its Google authorization. You can also remove the app’s access directly in your Google Account. Disconnection stops future connected access but does not automatically erase previously imported messages, project files, calendar copies, or financial records.
For access, correction, or deletion requests, contact us at the address below and identify the relevant account or event. We may verify your identity and retain records when needed for legal obligations or legitimate recordkeeping. Removing data from inFLO does not by itself delete the original email in Gmail, copies held by recipients, or records maintained separately by other providers. Backup and provider retention may differ from the active app.
Security and choices
inFLO uses authenticated staff access, role restrictions, encrypted Google connection credentials, and HTTPS connections. No system can guarantee absolute security. Only upload or share information you are entitled to provide, and avoid unnecessary sensitive information in event notes or files.
Contact us to discuss communication preferences or questions about your information. Account owners control connected services, staff access, and automation settings. Updated versions of this policy will be posted here with a revised date.
Google Limited Use commitment
inFLO’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy and the Google Workspace user data and developer policy, including their Limited Use requirements.
Contact us
Pop Pop Balloon · Fort Wayne, Indiana
Privacy questions and requests: events@poppopballoonfw.com