725Tracko · Legal

725Tracko Privacy Notice

How the internal 725Tracko workspace and Accounting AI handle operational records, conversations, and authorized accounting information.

Effective November 8, 2026
Current integration status.
Accounting AI chat is available. QuickBooks and Plaid Production connections are not active as of November 8, 2026. No fixed retention period, automatic deletion mechanism, or independent security certification is asserted. Financial integrations require separate activation and authorization.

1. Who We Are & What This Notice Covers

LED Repair Techs Inc., doing business as 725co LED Repair Professionals (“725co,” “we,” “us,” or “our”), operates 725Tracko and its Accounting AI workspace at 725tracko.com. This notice addresses information handled in that internal application, including information about authorized personnel and individuals identified in business records.

The public repair-services website at 725co.com is covered by its separate Privacy Policy. These documents have different scopes. This application notice supplements, and does not replace, notices for separate employment, payroll, payment-processing, mobile-device, or marketing activities. Application use is addressed in the 725Tracko Terms of Use / End-User Agreement.

For data accessed through QuickBooks, 725co determines its own application purposes and responsibilities. We do not process that information on Intuit’s behalf. Intuit handles its services under its own Global Privacy Statement.

2. Current Release & Optional Connections

As of November 8, 2026, general Accounting AI chat is available, the QuickBooks invoice reader is installed but disabled, and QuickBooks Production and Plaid banking connections have not been activated in this release. A chat message alone does not connect an account or prove that financial records have been checked. For testing, 725co may connect an Intuit-provided QuickBooks Sandbox company, which contains only sample data and no real customer or financial records.

Sections describing connected accounting data apply only after the relevant integration has been enabled, its actual data practices have been confirmed, and an authorized account owner has completed the provider’s consent process. This notice is not a statement that payroll access, bank synchronization, reconciliation, or other proposed features are available. A material expansion will require updated information and any necessary consent before collection.

3. Information We Handle & Its Sources

Depending on the functions you use and your permissions, the application handles the following categories:

  • Account and access information: account identifiers, names, work contact details supplied to the system, account status, assigned permissions, and authentication or MFA status. These come from users, company administrators, and authentication activity.
  • Operational information: customer and company references, orders, equipment and module identifiers, repair and quality-control records, status updates, and related documentation entered by authorized personnel or company systems.
  • Conversation information: messages, responses, conversation titles, timestamps, and permitted results saved in a workspace conversation. Users and the application generate these records.
  • Usage and security information: request identifiers, access events, timing, usage counts, and technical error or connection status. Hosting and application systems may also produce network or device-related logs.
  • Authorized QuickBooks information, only when enabled: the approved company identifier and information needed for an invoice query, such as invoice ID and number, customer reference or display name, dates, currency, amount, and outstanding balance. This information comes from the authorized QuickBooks company, not from a general AI model.
  • Connection information, only when enabled: authorization state, provider/company identifiers, encrypted access and refresh tokens, token expiry details, and connection status needed to maintain permitted access.

The currently described invoice feature does not request full bank credentials, payment-card security codes, payroll records, or personal financial accounts. Never enter passwords, one-time codes, API secrets, or unnecessary sensitive personal information in chat or support messages.

4. How Information Is Used

Application information is used to authenticate authorized users, enforce permissions, manage internal operational workflows, respond to permitted queries, preserve relevant conversation context, provide support, investigate errors, protect the system, and meet applicable record-keeping obligations.

Connected QuickBooks information is limited to the authorized application functions. An invoice lookup supports internal accounting review; it is not a payment instruction or a bank-deposit verification. The application may save the permitted result in the user’s conversation and record limited audit information about the request.

Connected accounting data is not to be sold, used for unrelated advertising or profiling, supplied for a third party’s unrelated purposes, or used to train general-purpose AI models. A new purpose requiring permission cannot be authorized simply by editing this notice.

5. QuickBooks Authorization & Read-Only Access

When the integration is available, only an authorized company owner may approve the intended QuickBooks company through Intuit’s OAuth consent flow. 725Tracko uses the resulting authorization tokens; it does not ask you to provide your QuickBooks password in the workspace.

The invoice feature is limited by application controls to reading approved records. The provider’s authorization scope may be broader than the operations the feature performs; “read-only” is not a claim that OAuth scopes alone make every write impossible. The feature does not create or change invoices, make payments, or transfer money.

Approval to use the chat is separate from approval to administer connections. Financial queries require the configured permissions and security checks. A disabled feature, mismatched company, missing permission, or expired authorization must not be treated as a successful financial result.

6. AI Processing, Conversation History & Review

General Accounting AI conversation uses the OpenAI API. Your messages and the selected conversation history needed to generate a response may be transmitted to that provider. Do not enter information you are not authorized to disclose for this purpose. Authorized company administrators may review conversations for accounting oversight, security, support, and quality assurance.

The installed invoice-reader design handles invoice requests separately from general AI chat: its structured reply is produced by the application, and the associated financial messages are excluded from the general model’s conversation history. This boundary does not prevent a user from manually typing or pasting financial information into an ordinary message; such text may be sent with the general AI request.

Our application’s conversation storage and an AI provider’s processing or security logs are different. A non-storage request setting does not by itself establish zero provider retention. OpenAI’s published API documentation states that API data is not used for model training by default unless the customer opts in, and describes separate retention controls. The applicable account settings and agreements must be checked before any expanded financial-data use. See OpenAI’s API data controls.

AI answers can be inaccurate. Important accounting conclusions require human review against the identified source system. This application is not intended to make automated eligibility decisions about credit, insurance, employment, housing, or other regulated opportunities.

7. Who May Access Information & When It Is Disclosed

Access within 725co is limited by assigned responsibilities and permissions. It may include authorized workspace users and administrators handling operations, accounting oversight, technical support, or security. Permission to review one function is not blanket permission to inspect every conversation or financial record.

Information may be processed by service providers supporting hosting, infrastructure, communications, AI responses, and an authorized financial integration, only as necessary for the relevant service and permitted purpose. QuickBooks receives the authorized API requests; OpenAI receives the general chat content described above. Any provider receiving QuickBooks-derived information must be subject to the required written data-protection and security terms before that disclosure.

We may disclose information when legally required or necessary to investigate misuse, protect rights or safety, or respond to a valid legal process, subject to applicable law and provider obligations. This is not permission to sell accounting data or share it for unrelated third-party marketing. This notice does not represent that a pending Plaid integration is already receiving data.

8. Storage, Processing Locations & Retention

Workspace records, conversations, permitted financial responses, and audit data may be stored in company application systems and supporting hosting infrastructure. External services may process authorized information in the United States or other locations under their applicable agreements. We do not promise that every copy or service is confined to one geographic region.

Our intended retention standard is to keep information only as needed for its permitted purpose and applicable record-keeping obligations. Relevant criteria include whether an account or connection remains active, whether an operational or accounting task is open, whether a security issue requires investigation, and whether a legal preservation duty applies.

We are establishing a category-specific retention and secure-deletion procedure, including backup handling and service-provider requests, before activating financial integrations. We do not currently claim a fixed automatic deletion schedule. Hiding a conversation does not necessarily erase every retained copy.

9. Disconnection, Withdrawal & Deletion Requests

Contact 725co using the details below to request access changes, correction, connection assistance, or deletion. Identify the workspace or relevant account and the request, without sending passwords, tokens, or complete financial credentials. We may need to verify your identity and authority, using only information reasonably necessary for that verification.

An authorized QuickBooks account owner may disconnect the application at any time using the Disconnect button in the Accounting AI workspace, through Intuit’s connected-app controls in QuickBooks, or by contacting 725co. When disconnected from the workspace, 725Tracko asks Intuit to revoke the authorization and deletes the stored access and refresh tokens. Valid withdrawal of the connection must stop further access and processing under that authorization. Necessary legally retained records must be restricted to the applicable retention obligation, not used to continue the withdrawn feature.

QuickBooks-derived information must be securely deleted upon a valid user request, subject to legally required record keeping. This includes addressing relevant application copies and derived records, rather than treating disconnection alone as deletion. A deletion workflow and provider coordination must be in place before the financial integration is activated. A request to 725co does not automatically delete original books or account records held by Intuit, a bank, or another independent provider.

We will handle requests within applicable legal requirements and explain any permitted limitation. We do not promise instant or automatic deletion.

10. Security & Incident Handling

Controls reviewed for the application include authenticated access, active-user checks, assigned permissions, and MFA requirements for protected financial access. The financial connection components are designed to keep authorization credentials server-side and encrypted when stored. These controls reduce risk; they are not a guarantee that all systems are invulnerable or that every deployment setting has been independently certified. Stored QuickBooks tokens are encrypted, renewed automatically only when needed, and revoked and deleted when the connection is removed. Intuit request identifiers (intuit_tid) may be logged for troubleshooting; tokens and invoice contents are not written to application logs.

If an incident affecting application data is discovered, it must be investigated and handled under applicable legal and contractual obligations, including any required notifications to affected people and service providers. This application notice does not substitute an unsupported promise of notifying every person within one business day. Contractual notice to a provider and legal notice to affected individuals may have different requirements.

Report suspected unauthorized access promptly. Do not include secrets in the report.

11. Cookies & the Public Website

The workspace uses session and security mechanisms needed for sign-in and application operation. Blocking essential cookies may prevent access or interrupt a session. The presence of this legal page on 725co.com does not mean the public website’s analytics or advertising tools are deployed inside Accounting AI.

For cookies and analytics used while browsing the public 725co.com website, consult its separate Privacy Policy. No claim about advertising-cookie consent, browser opt-out signal handling, or app-wide tracking is made here without a corresponding implementation review.

12. Privacy Rights & California Requests

Depending on the law that applies, you may have rights to know about or access personal information, correct inaccuracies, request deletion, obtain a portable copy, or exercise applicable opt-out or sensitive-information controls. The availability of a right and lawful exceptions depend on the information, the requester, and the obligations that apply to 725co. This notice does not assume that every statutory regime applies to every activity.

Use the email, telephone, or postal contact below to make a request, including an authorized-agent request where permitted. You may ask about an application’s data practices even if you are identified in a business record rather than being a registered user. We will not unlawfully discriminate or retaliate because you exercise a protected privacy right.

The California Privacy Protection Agency provides further information about California privacy rights. These rights are distinct from the application’s operational permissions and do not require disclosing passwords or tokens to 725co.

13. Intended Audience

725Tracko is a company workspace for authorized personnel, not a general-public financial application or a service directed to children. Access must be granted by the company. Contact us if information appears to have been submitted through unauthorized use or by a child; do not use this notice as a substitute for access controls.

14. Changes to This Notice

This notice displays its revision date above. Material changes in collection, recipients, purposes, retention, or integrations will be explained before the changed practice is introduced where required, and separate authorization will be obtained when necessary. Mention of a future feature in this notice does not authorize that feature to collect information today.

15. Privacy Contact & Requests

Use the subject “725Tracko Privacy Request” for data requests or “725Tracko Security” for suspected access issues. Describe the concern without including credentials or unnecessary financial information.

LED Repair Techs Inc., doing business as 725co LED Repair Professionals
725Tracko / Accounting AI — Privacy Contact
12628 Hoover St, Garden Grove, CA 92841, United States
Email: info@725co.com
Phone: (714) 373-2219
Related document: 725Tracko Terms of Use / End-User Agreement
Portrait of José de Jesús “Chuy” Martínez, founder of 725co LED Repair Professionals

José de Jesús “Chuy” Martínez

Founder & CEO · 725co. LED Repair Professionals

José de Jesús “Chuy” Martínez is the founder and CEO of 725co. LED Repair Professionals, with more than two decades of hands-on electronics experience and over a decade specializing in professional LED display technology. His expertise reaches far beyond the repair bench, encompassing live-event production, LED video wall assembly, on-site technical support, and permanent display installations.

His technical foundation began in León, Guanajuato, Mexico, where he learned electronics alongside his father, an electronics repair technician. From repairing cassette players for classmates to developing advanced diagnostic skills on computers and electronic equipment, Chuy built a reputation for solving difficult technical problems. In 2008, he established his first business, 777 Computer Repair, specializing in hands-on troubleshooting and component-level repairs.

In 2012, an invitation from his friend Luis brought him into the professional LED industry through Matrix Visual. Working from the beginning as an independent contractor under LED REPAIR TECHS, Chuy developed extensive field experience traveling to major productions, assembling LED video walls, diagnosing technical issues, and repairing displays during live shows—often under the time-sensitive demands of an active event.

Throughout his career, he has contributed to events and productions involving major audiovisual companies, including PRG, 4Wall, and Freeman, as well as numerous other industry providers. A notable example was his work installing and repairing LED screens for the live performance featured in Kevin Hart: What Now?, the 2016 concert film. His background also includes extensive experience with permanent LED display installations, giving him a broad understanding of display systems from installation through maintenance and repair.

As his responsibilities at Matrix Visual expanded, Chuy took charge of its repair operation, personally recruiting, training, and directing a growing team of technicians. His first recruit was his brother David. He incorporated LED REPAIR TECHS INC in 2018 and opened a dedicated repair facility in Garden Grove, California, in 2021, building on the professional relationships and technical reputation he had established across the industry.

In 2022, he introduced 725co as the company’s DBA in memory of David, whose birthday was July 25. Today, Chuy combines deep technical knowledge, extensive production experience, and entrepreneurial leadership to guide 725co with a focus on precision, reliability, and professional repair standards—while carrying forward the family legacy behind its name.