01 · Scope and roles
One policy for the TriedFlow platform
TriedFlow is business software operated by Tafech Floors of Texas LLC for flooring companies. This policy applies to triedflow.com, app.triedflow.com, and related TriedFlow services. TriedFlow is currently available through an invitation-only private preview.
Each customer company has its own workspace, authorized users, business records, and optional provider connections. One company cannot choose another company's Google accounts, calendars, staff, customers, or records.
Company and platform privacy roles
TriedFlow determines how public-website, trial-request, company-account, user-authentication, support, security, and service-administration information is handled. Depending on applicable law, TriedFlow may be described as the controller or business for that information.
Each customer company determines why and how its own customer, lead, employee, job, estimate, appointment, communication, and related business information is used. TriedFlow processes that company-controlled information to provide and protect the service on the company's behalf and according to authorized instructions. A customer or lead of a company using TriedFlow should normally direct a privacy request to that company first. TriedFlow assists the company with verified requests when required.
02 · Information
Information TriedFlow may handle
Website and trial-access information
When someone requests trial access, TriedFlow may receive their name, email address, company, optional phone number, primary trade, team size, message, page URL, and campaign attribution values. The website accepts limited conversion events such as the page, placement, and campaign associated with a request. Those event requests are designed not to include a name, email address, company, or phone number.
Company workspace information
Companies and their authorized users may provide account, customer, lead, job, estimate, appointment, material, production, payment, communication, media, and closeout information needed to operate their workspace. Access is limited by company, role, and record rules.
Connected-account and transaction information
When an optional provider feature is configured and enabled, TriedFlow may handle provider account and resource identifiers, encrypted credentials, connection status, user selections, command receipts, and the bounded provider data needed for that feature. Payment history can include amounts, status, references, refunds, disputes, and audit evidence. Full payment-card details remain with the configured payment provider rather than in TriedFlow application records.
Technical, security, and browser information
TriedFlow may process browser and request information, connection status, logs, audit and command receipts, security signals, error information, and support records needed to operate and protect the service. The public website does not currently use third-party advertising cookies or pixels. Guided-demo and trial-request retry state stays in current-page memory rather than persistent browser storage.
03 · How information is used
Purposes tied to the requested service
TriedFlow uses information to:
- Provide company workspaces and the workflows a company enables.
- Authenticate users and enforce company, role, and record boundaries.
- Route trial requests, leads, documents, provider commands, and support work.
- Maintain security, audit evidence, reliability, and abuse prevention.
- Communicate with account holders about access, support, service operation, and material changes.
- Comply with law and enforce the Terms of Use and other applicable agreements.
TriedFlow does not sell personal information or share it for cross-context behavioral advertising. TriedFlow does not use one company's customer or lead data to advertise TriedFlow or another company, or to train a generalized artificial-intelligence model.
04 · Google connections
Separate permissions for separate company features
A verified company Owner sponsors and manages the company's general Google connection. Where company policy allows it, an eligible active team member may authorize only that member's own personal calendar connection. The Google account holder chooses whether to grant access, and company policy determines which permitted resources TriedFlow may use.
| Google OAuth scope | How TriedFlow uses it |
|---|---|
https://www.googleapis.com/auth/adwords | Lets an authorized company Owner connect Google Ads, select one or more accounts, and view account details and daily reporting. The permission is broader than the read-only reporting functions TriedFlow uses. |
https://www.googleapis.com/auth/calendar.calendarlist.readonly | Allows read-only access to the connected account's calendar list so the authorized user can choose eligible calendars. |
https://www.googleapis.com/auth/calendar.events | Allows viewing and editing events on selected calendars. TriedFlow limits provider calls to bounded availability reads and correlated scheduling work. |
Google's consent screen can grant broader access than the product actions described here. TriedFlow's application logic limits use to the company-selected accounts and calendars needed for the connected user-facing feature.
05 · Google Ads reporting
Selected-account reporting for invited testers
When a company Owner connects Google Ads and selects one or more accounts, TriedFlow may read and retain the selected accounts' names and IDs, currencies, time zones, and daily impressions, clicks, and cost. This information is used to show the company its own connected reporting.
The reporting connection is currently limited to invited registered testers under Google's External Testing restrictions. It does not create or edit campaigns, change advertising spend, ingest Google lead forms, or upload conversion events.
06 · Google Calendar
Selected calendars and correlated appointments
When Calendar is configured and admitted, the authorized Google account holder chooses eligible calendars. TriedFlow receives the calendar ID, calendar name or summary, access role, primary-calendar flag, and time zone. A calendar ID can resemble an email address.
For selected calendars, bounded Events.list requests use event ID, status, transparency, start and end time, ETag, and private correlation properties to calculate availability. Those occupancy requests omit titles, descriptions, locations, and attendees. Exact event reads and provider write responses can return additional Google event fields. For a TriedFlow-owned copy, the connector validates the provider-returned title against the expected limited title. It does not persist provider-returned titles, descriptions, locations, or attendees as free-form customer content.
TriedFlow-created calendar copies use a limited TriedFlow title and, when applicable, a safe assigned-representative or crew label. They include start and end time, time zone, and private correlation identifiers. They do not include customer contact information, customer location, attendees, or a customer invitation. Update and removal require the corresponding TriedFlow record and version.
TriedFlow requests the calendar-list read-only and event-management permissions shown above, not calendar.events.freebusy. The calendar.events permission is broader than the operations TriedFlow performs, and application logic limits calls to selected calendars and correlated scheduling work.
07 · Google Limited Use
Limits on Google API information
TriedFlow's use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Google API information is used only to provide and protect the connected, user-facing features the account holder and company authorize. It is not sold or used for ad targeting or retargeting, credit or lending decisions, data brokerage, or generalized or non-personalized artificial-intelligence or machine-learning model training. Calendar data is not used for advertising.
Human access to Google API information is limited to cases involving the user's consent, security and abuse response, legal requirements, or contracted service delivery allowed by Google's policies. Calendar information is also subject to the Google Workspace API User Data and Developer Policy.
09 · Security
Protection and company isolation
TriedFlow uses HTTPS, company and role boundaries, audit records, restricted server roles, and enforced database access rules. OAuth access and refresh tokens stay on server-only paths, saved grants are encrypted, and tokens are not returned to the browser. Connections, selected resources, receipts, commands, and provider work are bound to a verified company and authorization context.
No system can guarantee absolute security. TriedFlow limits access to the people and systems needed to provide and protect the service and responds to security incidents as required by applicable law.
10 · Retention and deletion
Records are kept for defined business and legal purposes
TriedFlow keeps information for as long as reasonably needed to provide the service, maintain security and audit evidence, resolve disputes, meet contractual or legal obligations, and preserve accurate business and financial history. Retention depends on the record type, workspace status, company instructions, applicable law, and backup cycle. Information no longer required is deleted or deidentified when reasonably practicable, subject to legal holds, security records, backups, and records that must be preserved.
Disconnecting Google Ads clears TriedFlow's active saved grant and stops new reporting while preserving completed reports, receipts, and history. Disconnecting Calendar clears the active encrypted grant and disables its connected targets while preserving connection metadata and historical evidence. Native TriedFlow customer, job, appointment, and business records remain separate from a Google connection.
Disconnecting in TriedFlow does not itself revoke Google's connected-app permission or erase every completed record or backup. The Google account holder can separately review or remove TriedFlow in Google Account third-party connections. Events already created in Google Calendar remain at Google until removed through the applicable TriedFlow scheduling workflow or by the Google account holder.
11 · Choices and requests
Controls available to companies and individuals
- Do not connect an optional Google service if it is not needed.
- A verified company Owner manages company provider connections and selected resources.
- An eligible team member can manage only a permitted personal-calendar connection.
- A company can pause or disconnect its TriedFlow connection.
- A Google account holder can revoke TriedFlow separately in Google Account settings.
- Authorized users can ask their company Owner about company-managed records and access.
Depending on applicable law, an individual may have rights to ask for access, correction, deletion, or a copy of personal information, or to object to certain processing. TriedFlow may need to verify the requester and may retain information where law, security, fraud prevention, contracts, or recordkeeping duties require it. If a customer company controls the record, TriedFlow may route the request to that company and assist it with the response.
Contact TriedFlow
Send privacy, access, correction, or deletion requests to legal@triedflow.com. Written requests may be sent to Tafech Floors of Texas LLC, 5216 Airport Fwy, Fort Worth, TX 76117, United States.
12 · Other privacy terms
Children, processing location, and policy changes
TriedFlow is business software and is not directed to children under 13. If TriedFlow learns that a child provided personal information outside an authorized company record, TriedFlow will take reasonable steps to delete it, subject to applicable law.
TriedFlow is operated from the United States. TriedFlow and its service providers may process information in the United States and other locations where they operate, subject to applicable legal and contractual safeguards.
TriedFlow may update this policy as the service, law, or provider requirements change. The updated policy will be posted here with a new effective or last-updated date. When reasonably required, TriedFlow will give company Owners additional notice of material changes.