Version 2.3 · Effective October 15, 2026
Privacy Policy
This Privacy Policy explains how FlawlessIQ LLC (“BuiltCue,” “we,” “us” or “our”) collects, uses, discloses, protects and retains personal information in connection with the BuiltCue websites, applications, portals and related services (the “Service”), and the choices and rights available to you.
BuiltCue is software for photography and video businesses. Some of the information in the Service is about the people those businesses work with. Section 2 explains how responsibility for that information is divided between BuiltCue and each business.
1. Who we are and what this policy covers
FlawlessIQ LLC is a New Jersey limited liability company located at 2 Green Village Rd, Suite 209, Madison, NJ 07940, United States. You can contact us about privacy at support@builtcue.com.
This policy applies to information we process: about visitors to builtcue.com; about the businesses that subscribe to BuiltCue (“Companies”) and their owners, staff and contractors (“Company Users”); and, as a service provider to Companies, about the people Companies work with. It does not cover the privacy practices of Companies themselves, or of third-party services that a Company connects to BuiltCue.
2. Companies and the people they work with
- Company accounts. For information about Company Users and website visitors, BuiltCue determines how the information is used and is the business (or controller) responsible for it under this policy.
- A Company’s clients, crew and vendors. When a Company puts information into BuiltCue about the people and businesses it works for — for example couples, families, companies, teams and the people who contact the Company — or about its crew, vendors and planners (together, “Client Data”), the Company decides what is collected and why. BuiltCue processes Client Data on the Company’s behalf and under its instructions, as its service provider (or processor), under our Terms of Service and Data Processing Addendum. The Company’s own privacy notice governs how it uses that information.
If you are a client, crew member or vendor of a Company and want to access, correct or delete your information, please contact the Company directly. If you contact us, we will refer your request to the Company and assist it in responding as required by law. If you cannot reach the Company, write to us and we will help.
3. Information we collect
Information provided to us
| Category | Examples | Source |
|---|---|---|
| Account and contact details | Name, business name, email address, phone number, role, password or single-sign-on identifier, business address | Company Users when they register or are invited |
| Billing information | Plan, billing address, transaction history, last four digits and type of payment card (full card details are held by Stripe, not by BuiltCue) | Company Users at checkout, and our payment processor |
| Demo requests and how you found us | Name, company name, email, phone, website or Instagram, what you would like to see, good times to talk, and how you heard about BuiltCue; for a Company that signs up, the link that brought it to BuiltCue and any referral or promotion code used | Photographers who request a demo or create a Company |
| Inquiry information | Name, email, phone, event date, location, venue, guest count, budget, how they heard about the Company, message and answers to the Company’s questions | People who submit a Company’s inquiry form or email a Company’s forwarding address |
| Job and planning information | Event details, schedules, locations, questionnaires, shot lists, preferences, special requests, crew assignments and the names of people to be photographed | Companies, their clients and crew |
| Agreements and signatures | Proposals, agreements, amendments, the signer’s typed name, email, date and time, IP address, device and browser, consent version and document fingerprint | Companies and the clients who sign |
| Invoices and payments | Amounts, due dates, payment status, billing addresses and tax details for invoices between a Company and its clients (payments themselves are processed by the Company’s payment provider) | Companies and their connected accounting services |
| Documents and files | Certificates of insurance, contracts, schedules, images, and other files uploaded to the Service | Companies, clients, crew and vendors |
| Communications | Emails, messages and comments sent through the Service, and replies to them; feedback and support requests | Company Users, clients, crew and vendors |
| Crew information | Name, contact details, roles, availability, rates, preferences and tax-form status | Companies and crew members |
Information collected automatically
- Device and usage information: IP address, browser type and version, device type, operating system, pages and features used, dates and times of access, referring pages and actions taken in the Service.
- Logs and error reports: server logs, security events and, if an error occurs in your browser, a technical report of the error, the page and the browser (with email addresses, links and identifying details removed before it is stored).
- Approximate location: derived from IP address, used for security and to show times in the right time zone. We do not collect precise geolocation.
- Cookies and browser storage: as described in our Cookie and Browser Storage Notice.
Information from other sources
- Connected services that a Company chooses to connect, such as Google Calendar, Zoom, QuickBooks Online and Dropbox, as described in Sections 6 to 9.
- Sign-in providers: if you sign in with Google, we receive your name, email address and profile image from Google.
- Fraud-prevention providers: Google reCAPTCHA Enterprise provides signals that help us distinguish people from automated abuse.
4. How we use information
| Purpose | What it involves |
|---|---|
| Providing the Service | Creating and maintaining accounts and workspaces; operating inquiries, proposals, agreements, invoices, questionnaires, schedules, crew coordination, galleries, reviews and portals; sending the communications Companies ask us to send |
| AI-assisted features | Drafting replies and documents, summarizing inquiries and consultations, proposing schedules and extracting details from documents, always for a person’s review (Section 5) |
| Electronic signatures | Presenting agreements, capturing signatures and keeping evidence that they were made (Section 6) |
| Billing | Processing subscription payments, managing trials, renewals and cancellations, and keeping financial records |
| Sales and referrals | Responding to demo requests; understanding which channels bring Companies to BuiltCue; applying a referral offer to a Company that signs up with another Company’s code, and crediting the Company that referred it. A Company sees how many Companies signed up with its code and when, never which Companies they are |
| Support and communication | Responding to requests, sending service and account notices (such as trial reminders, security alerts and changes to our terms), and handling feedback |
| Security and integrity | Authenticating users, preventing fraud, spam and abuse, monitoring and investigating security incidents, and enforcing our terms |
| Improving the Service | Understanding how features are used, diagnosing errors and developing improvements, using de-identified or aggregated information wherever possible |
| Legal obligations | Complying with law, responding to lawful requests, and establishing, exercising or defending legal claims |
We do not sell personal information, we do not share it for cross-context behavioral advertising, and we do not use it to make decisions that produce legal or similarly significant effects about any individual based solely on automated processing. BuiltCue shows no advertising.
Vendor invitations: when a Company leaves this setting on, a vendor that the Company adds to a booked job (such as a planner, DJ or florist, never a venue or the Company’s client) receives one email from BuiltCue inviting them to try BuiltCue with that Company’s referral code. We use only the vendor’s name and email address and the Company’s name, send it once to any address, never to someone who already has a BuiltCue account, and never again to anyone who uses the unsubscribe link in it. A Company can turn this off on its Subscription page.
With a Company User’s agreement we may send occasional product news. Every such email includes an unsubscribe link, and opting out does not affect service and account notices.
5. AI features and Google Limited Use
BuiltCue’s use of raw or derived user data received from Google Workspace APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is not used, transferred, or sold to create, train, or improve foundational or generalized artificial-intelligence or machine-learning models, whether in raw, aggregated, anonymized, or derived form.
BuiltCue’s AI-assisted drafting and review features run on Google Vertex AI, using Google’s Gemini models, inside BuiltCue’s own Google Cloud project in the United States. BuiltCue integrates no third-party AI service providers, model gateways, model aggregators, or self-hosted models. Data obtained from the Google Calendar API is not sent to these features at all: they operate on the Company’s own BuiltCue records, such as inquiry, project, package, questionnaire, and document data. We do not use Customer Data or Client Data to train or fine-tune AI models, and Google does not use data sent through Vertex AI to train its models. AI output is advisory and is never the authority for legal, payment, signature, permission, or readiness decisions, each of which requires a human decision.
6. Electronic signatures
When a Company sends an agreement through BuiltCue and a client signs it, BuiltCue records, as evidence of each signature, the name typed, the email address the signer is signed in with, the date and time, the signer’s IP address, and the device and browser used, together with the version of the electronic-signature consent they agreed to and a fingerprint of the exact agreement text. This record is kept with the agreement, printed on its signing record, and available to the signer, the Company, and BuiltCue to operate the service. It is retained for as long as the agreement is, so that the signature can be verified if it is ever questioned.
7. Google Calendar data
A Company may connect its own Google Calendar so BuiltCue can offer clients only consultation times the Company is genuinely free, and place booked work on that calendar. BuiltCue requests two Google OAuth scopes. The Google user data accessed under each is:
- https://www.googleapis.com/auth/calendar.freebusy — the free/busy availability of the primary calendar of the connected Google Account. BuiltCue receives only the start and end times of periods marked busy. This scope does not permit reading the title, description, location, attendees, or any other content of a calendar entry, and BuiltCue does not receive that content.
- https://www.googleapis.com/auth/calendar.events.owned — calendar events on calendars the connected Google Account owns. BuiltCue creates consultation and event-day entries for that Company’s booked work, reads, updates, or deletes those same entries when the Company reschedules or cancels, and reads them back to check they still match the booking. It acts only on entries it created, identified by an event identifier stored with the corresponding consultation or project. It does not list a Company’s calendars or modify entries created by anyone else.
In addition to the calendar data above, BuiltCue stores the OAuth access and refresh tokens issued for that Google Account, and for each entry it creates, the Google event identifier and event link.
How it is used. Free/busy availability is used to compute which consultation times to offer, and the event scope is used to keep the Company’s calendar in step with its bookings. Google user data is used only to provide these features for the authorizing customer. It is not sold, used for advertising, shared with unrelated customers, or used to train or improve generalized artificial-intelligence or machine-learning models. Google Calendar data is not sent to BuiltCue’s AI features.
How it is stored and retained. Free/busy availability is requested at the moment a set of consultation times is calculated and is not written to BuiltCue’s records. Event identifiers and links are retained for as long as the consultation or project they belong to exists. Access and refresh tokens are held server-side in managed secret storage and are never exposed to the browser.
How to stop and remove access. Disconnecting Google Calendar in BuiltCue removes its reference to the stored credential and ends all further access to the Google Account, including availability reads and calendar writes. Revoking BuiltCue from the Google Account permissions page invalidates the issued tokens directly. Removing or moving an entry in Google Calendar does not cancel or move the booking in BuiltCue: BuiltCue records that the entry was removed, or the time Google now shows, and asks the Company what to do.
8. Zoom data
If a Company connects Zoom, BuiltCue processes OAuth authorization details and the meeting information needed to create, view, update, and cancel that Company’s Zoom meetings. Zoom information is used only to provide the connected workflow for the authorizing customer. It is not sold, used for advertising, shared with unrelated customers, or used to train AI models. Disconnecting Zoom in BuiltCue ends further access; the Company can also remove BuiltCue from its Zoom App Marketplace settings.
9. Other connected services
- QuickBooks Online and QuickBooks Payments (Intuit). If a Company connects QuickBooks, BuiltCue creates and updates customers and invoices in the Company’s QuickBooks company and reads their payment status. Payment details entered by clients are collected and processed by Intuit, not by BuiltCue.
- Dropbox. If a Company connects Dropbox, BuiltCue stores job documents the Company chooses in a folder in the Company’s own Dropbox and reads them back when needed.
- Google Maps Platform. When someone types an address or venue, the text is sent to Google’s Places service to suggest matching places.
Access tokens for every connected service are stored server-side in managed secret storage, encrypted, and never exposed to the browser. A Company can disconnect any service at any time in Settings → Integrations.
10. Emails sent for Companies
BuiltCue sends emails on behalf of Companies — for example inquiry acknowledgements, proposals, agreements, invoices, reminders, schedules and delivery notices — under the Company’s name. We record delivery events (such as delivered, opened, clicked or bounced) so the Company knows whether a message arrived, and we may stop sending to addresses that bounce, complain or unsubscribe. Replies go to the Company. If you no longer wish to receive emails from a Company, contact the Company or use the unsubscribe link where one is provided.
11. How we disclose information
We disclose personal information only as follows:
- Service providers (subprocessors) that host and operate the Service for us, under written contracts that restrict their use of the information to providing services to us and require appropriate security. They are listed, with their purpose and location, on our Subprocessors page.
- Within a Company. Information in a Company’s workspace is available to that Company’s authorized users, and to the clients, crew and vendors the Company chooses to share it with through the Service.
- Connected services that a Company chooses to connect, as directed by the Company.
- Legal and safety reasons, where we believe in good faith that disclosure is required by law, subpoena or other legal process, or is necessary to protect the rights, property or safety of BuiltCue, our users or others, or to detect and prevent fraud or security issues.
- Business transfers, to a successor in connection with a merger, acquisition, financing, reorganization or sale of assets, subject to this policy or protections at least as strong.
- With consent, or at the direction of the person concerned.
We do not sell personal information and we do not share personal information for cross-context behavioral advertising, and we have not done so in the past 12 months.
12. Cookies and browser storage
BuiltCue uses cookies and similar browser storage only to provide the Service: to keep you signed in, to secure your session, to protect forms from automated abuse (through Google reCAPTCHA Enterprise) and to remember preferences. We do not use advertising cookies, cross-site tracking or third-party analytics. Details are in our Cookie and Browser Storage Notice.
13. How long we keep information
| Information | Retention |
|---|---|
| Company workspace data (clients, jobs, agreements, documents, messages, files) | While the Company’s account is open. Companies can delete individual records or whole jobs at any time. When an account closes, the Company has 30 days to export its data; the workspace is then deleted, and backup copies expire within 90 days |
| Signature evidence records | For as long as the signed agreement is retained in the Company’s workspace |
| Inquiries that do not become bookings | Until the Company deletes them or the account closes |
| Company User account details | While the user has access to any workspace, then deleted with the workspace or on request |
| Subscription billing and tax records | Seven years after the transaction, to meet tax and accounting obligations |
| Support and feedback correspondence | Up to three years after the matter is closed |
| Security and application logs | Up to 30 days, or longer only while needed to investigate a specific security incident |
| Browser error reports | Up to 30 days |
| Backups | Up to 84 days, then overwritten |
| Audit records of changes to agreements, payments and permissions | For the life of the related record, so that changes can be verified |
We may keep information longer where required by law or to resolve a dispute or enforce our agreements, and we will delete or de-identify it when it is no longer needed.
14. Security
We use administrative, technical and physical safeguards designed to protect personal information, including: encryption in transit (TLS) and at rest; isolation of each Company’s data, enforced on every request; role-based permissions within each workspace; least-privilege access for our personnel; credentials for connected services held in managed secret storage; audit records for sensitive changes; automated backups; monitoring and alerting; and verification of webhooks from payment and integration providers. Our infrastructure is provided by Google Cloud, which maintains independent security certifications.
No method of transmission or storage is completely secure. If you believe your account or information has been compromised, contact us immediately at support@builtcue.com. We will notify affected Companies and individuals of a breach of personal information as required by law.
15. Where information is processed
BuiltCue is operated from the United States, and personal information is stored and processed in the United States on Google Cloud. The Service is intended for businesses in the United States. If you use it from another country, your information will be transferred to, stored and processed in the United States, where data-protection laws may differ from those in your country.
16. Your choices
- Account information: Company Users can review and update profile details in the Service.
- Connected services: Companies can disconnect any integration in Settings → Integrations.
- Marketing emails: use the unsubscribe link in any marketing email. Service and account notices cannot be turned off while you have an account.
- Cookies: you can clear or block cookies and site data in your browser, but the Service requires its essential storage to sign you in.
- Export: Company account owners can export workspace data at any time in Settings → Data & account.
17. Your privacy rights
Depending on where you live, you may have the right to:
- know or confirm whether we process your personal information, and access it;
- receive a copy of it in a portable format;
- correct inaccurate information;
- delete it;
- opt out of the sale of personal information, sharing for cross-context behavioral advertising, targeted advertising and certain profiling (we do not engage in any of these);
- limit the use of sensitive personal information (we use it only as permitted for providing the Service, security and legal compliance);
- withdraw consent where processing is based on consent; and
- not be discriminated against for exercising these rights.
How to make a request
Email support@builtcue.com with the subject “Privacy request,” or write to us at 2 Green Village Rd, Suite 209, Madison, NJ 07940. Tell us which right you wish to exercise and how we can reach you. We will verify your request by matching information you provide with information we hold, and may ask for additional information where necessary. You may use an authorized agent; we may require written proof of the agent’s authority and verification of your identity. We will respond within 45 days, and may extend that by a further 45 days where reasonably necessary, in which case we will tell you why.
If your request concerns Client Data held by a Company, we will refer it to that Company and support its response (see Section 2).
Appeals
If we decline your request, you may appeal by replying to our decision or emailing support@builtcue.com with the subject “Privacy appeal.” We will respond within 45 days. If you are not satisfied with the outcome, you may contact your state attorney general or privacy regulator.
18. Additional information for California residents
This section supplements this policy for California residents under the California Consumer Privacy Act, as amended (“CCPA”). In the past 12 months we have collected the following categories of personal information, for the purposes described in Section 4, from the sources described in Section 3, and disclosed each for business purposes to the categories of recipients shown:
| Category (CCPA) | Collected | Disclosed for a business purpose to |
|---|---|---|
| Identifiers (name, email, phone, IP address, account identifiers) | Yes | Service providers; the Company concerned; connected services a Company chooses |
| Customer records (address, billing details, signature) | Yes | Service providers; the Company concerned |
| Commercial information (plans, purchases, invoices) | Yes | Service providers (payment processing); the Company concerned |
| Internet or network activity (usage, logs, error reports) | Yes | Service providers (hosting, security) |
| Approximate geolocation (from IP address) | Yes | Service providers (security) |
| Audio, visual or similar (images and files uploaded) | Yes | Service providers (hosting); the Company concerned |
| Professional information (role, business, crew details) | Yes | Service providers; the Company concerned |
| Sensitive personal information (account log-in credentials) | Yes, for authentication only | Service providers (authentication) |
| Biometric, health, precise geolocation, government ID | No | — |
| Inferences used to profile individuals | No | — |
We retain each category for the periods in Section 13. We do not sell or share personal information, and we do not knowingly sell or share the personal information of consumers under 16. We use sensitive personal information only for purposes permitted by the CCPA. We do not offer financial incentives in exchange for personal information.
Shine the Light. California residents may request information about disclosures of personal information to third parties for their direct-marketing purposes. We make no such disclosures.
19. Additional information for residents of other U.S. states
Residents of states with comprehensive consumer-privacy laws — including Colorado, Connecticut, Delaware, Indiana, Iowa, Kentucky, Maryland, Minnesota, Montana, Nebraska, New Hampshire, New Jersey, Oregon, Rhode Island, Tennessee, Texas, Utah and Virginia — have the rights described in Section 17, to the extent those laws apply. We do not sell personal data, process it for targeted advertising, or use it for profiling in furtherance of decisions that produce legal or similarly significant effects. We do not process sensitive data except as necessary to provide the Service or as permitted by law. You may appeal a decision as described in Section 17.
Nevada. We do not sell covered information as defined under Nevada law.
20. Children
The Service is intended for businesses and adults. Accounts are available only to people 18 and older. We do not knowingly collect personal information directly from children under 13, and we do not create accounts for, send communications to, use facial recognition on or publish profiles of children. When a Company’s work involves minors — for example family sessions, school events or youth sports — the parent, guardian or organization is the Company’s client and the person who interacts with the Service, and a child’s name appears only where the Company enters it. If you believe a child has provided personal information to us directly, contact support@builtcue.com and we will delete it.
21. Do Not Track and Global Privacy Control
Because we do not sell or share personal information, or track users across other websites for advertising, there is nothing for a Do Not Track or Global Privacy Control signal to switch off. We nonetheless treat a Global Privacy Control signal as a valid request to opt out of sale and sharing for the browser that sends it.
22. Changes to this policy
We may update this policy from time to time. The version and effective date at the top of this page identify the current version. If we make a material change, we will notify Company account owners by email and by notice in the Service before it takes effect.
23. Contact us
FlawlessIQ LLC, Attn: Privacy, 2 Green Village Rd, Suite 209, Madison, NJ 07940, United States · support@builtcue.com