Privacy Policy

We do not sell personal information, we do not share it for cross-context behavioral advertising, and we do not build advertising profiles. We have never done either.

Consumers.

• Account: your email address, used for passwordless magic-link sign-in through our authentication provider.
• Profile: legal name, mailing address, phone number, date of birth, and optional demographic fields. Agencies such as the CFPB require most of these to accept a complaint.
• Social Security Number (strictly optional): required by the CFPB only for certain categories (e.g., identity theft, credit reporting). It is encrypted at the application layer before storage, with encryption keys isolated from the database and accessible only to the service itself.
• Evidence documents: PDFs, images, and text you upload while preparing a complaint.
• CFPB portal credentials (optional): if you ask us to file through an existing CFPB account, we store your portal email, password, and MFA codes. The password is encrypted in transit and at rest and is used only to interact with the CFPB portal at your direction.
• Gmail app password (optional): to read CFPB multi-factor codes from your inbox automatically, you may supply a scoped Gmail app password. It is encrypted and used exclusively to retrieve those messages.
• Identity verification: where identity checks apply, they are handled through an identity-verification partner or by reviewing documents you upload.
• Payment: processed entirely by PayPal. We receive a confirmation, payer ID, and amount. We never see or store card or bank account numbers.

Business customers (property management companies and landlords).

• Company profile: organization name, business type, contact person, business email, and one verification document (business license, articles of incorporation, EIN letter, or government ID) stored in a private bucket.
• Portfolio data: companies, properties, units, leases (including lease PDFs), and complaint records you create in the portal.
• Tenant data: names, contact details, unit assignments, complaint narratives, and evidence your organization uploads about tenancies. For this category you are the controller; see Section 10.
• Team members: names, emails, roles, and permission settings for the people you invite.

• IP address and request metadata recorded in our internal usage-analytics records for fraud prevention, abuse detection, and regional usage analysis. Records may include referer, country, path, and utm parameters.
• Essential session cookies set by our authentication provider to keep you signed in (HTTP-only, same-site). We set no advertising or third-party analytics cookies.

We deliberately do not publish details about our infrastructure, storage layout, or security architecture; those details are maintained internally on a need-to-know basis because the service handles regulatory correspondence and other categories of non-public information. Because we run no third-party ad tech, there is nothing to which a Global Privacy Control signal could apply beyond what we already do not do; we honor GPC as a "do not sell or share" instruction regardless.

We use personal information to:

• Provide, maintain, and secure the service;
• Extract facts from your evidence and draft complaint documents with AI assistance;
• Submit complaints to agencies only after your explicit approval of each filing;
• Poll agency portals for status updates and notify you of changes;
• Operate billing, subscriptions, prepaid credits, and statements;
• Verify business customers and prevent fraud and abuse;
• Send service notifications (filing confirmations, status updates, statements) and legally required notices, including advance notice of policy changes (Section 14);
• Comply with law and enforce our Terms of Service.

We do not use personal information for automated decisions that produce legal or similarly significant effects about you. Filing always requires a human click: the AI drafts, you approve.

Legal bases (EEA/UK users): performance of a contract (providing the service), legitimate interests (security, fraud prevention, product improvement), consent (optional features such as portal credentials or SSN entry), compliance with legal obligations (records tied to filings), and substantial public interest / legal claims where relevant to complaint correspondence.

Document analysis and drafting use three classes of AI models:

• Document OCR models: convert uploaded PDFs to clean text;
• OpenAI-class extraction models: per-document extraction of transactions, dates, events, and contacts;
• Claude (Anthropic): timeline curation, full complaint drafting, quality critique, and agency taxonomy mapping.

Each provider operates under commercial terms that prohibit training on our inputs. Every dollar amount, date, reference code, and account number in a generated document must trace back to extracted facts; anything unverifiable is flagged and corrected or surfaced for review before filing is allowed. You remain the final reviewer, and nothing is submitted to any agency until you explicitly approve it.

We share personal information only as follows:

We keep this list at the category level on purpose: we do not publish the specific vendors or architecture behind each category. A detailed sub-processor list is available to business customers under their Data Processing Agreement.

A filed complaint becomes part of the receiving agency's records and may be published in anonymized form under that agency's rules (for example, the CFPB's public consumer complaint database). Once filed, submission cannot be undone by us.

• Account, profile, and complaint records: while your account is active;
• Evidence files: retained with your case so your record stays complete; deleted within 30 days of account deletion;
• Filed-complaint metadata (confirmation numbers, timestamps): kept as an internal audit record even after account deletion, because filings cannot be retracted;
• Consent and agreement records (checkbox acceptances at payment): at least 3 years or 1 year after termination of the contract, whichever is longer, consistent with Cal. Bus. & Prof. Code § 17602(a)(6);
• Usage analytics: 24 months;
• Deletion requests are honored within the timeframes in Section 12.

• All traffic is encrypted in transit (TLS 1.2+) and data is encrypted at rest;
• Highly sensitive fields (SSN, portal credentials) receive an additional layer of application-layer encryption with keys isolated from the primary database;
• Access controls ensure you can read and modify only your own records;
• Private, access-controlled storage for evidence and business documents;
• Limited internal access: engineers touch production data only for support, security, or fraud investigations.

We do not disclose detailed security architecture publicly. No system is perfectly secure; Section 13 explains breach notification.

Regardless of where you live in the United States, you may email legal@4eye.me to access, correct, export, or delete your personal information, or to withdraw consent for optional features. We verify requests by contacting you at your account email and respond within 30 days (45 days where a state law allows an extension).

California (CCPA/CPRA). California residents have the right to:

• Know and access the categories and specific pieces of personal information collected;
• Delete personal information (subject to legal retention duties);
• Correct inaccurate personal information;
• Port personal information in a machine-readable format;
• Limit the use and disclosure of sensitive personal information (we use SSN and credentials only to provide the requested service, never to infer characteristics);
• Opt out of sale or sharing (we do neither);
• Be free from discrimination for exercising these rights.

Other states. Residents of Colorado, Connecticut, Virginia, Utah, Texas, Oregon, Montana, Florida, Delaware, Iowa, Nebraska, New Hampshire, New Jersey, Tennessee, Minnesota, Maryland, Indiana, Kentucky, and Rhode Island (each with a comprehensive privacy law in effect as of January 2026), together with residents of any other state, receive at minimum: confirmation of processing, access, correction, deletion, portability, the ability to opt out of targeted advertising, sale, or profiling (all of which we do not engage in), and appeal of any denied request by replying to our decision email. Maryland residents additionally receive the strictest processing limits available anywhere in this policy: we collect only what is reasonably necessary for the services you request.

Authorized agents may submit requests with written permission. Parents and guardians may exercise rights on behalf of children under 16.

When a property management company or landlord uploads tenant information, that customer determines the purposes and means of processing and remains responsible for having a lawful basis (such as performing the lease or a legitimate business need) under laws like the Fair Credit Reporting Act when applicable, state landlord-tenant statutes, and local housing rules. We process tenant data strictly to deliver the portal: intake, routing, response drafting, statements, and support.

• We act as a service provider / processor and sign a Data Processing Agreement on request (legal@4eye.me);
• Tenant data belongs to the customer's organization, scoped by organization ID with row-level security; team members see only their assigned properties unless granted broader permissions;
• The customer, not 4eye, responds to tenant requests regarding tenant-held data; we will reasonably assist;
• On termination, tenant data is returned or deleted per the enterprise agreement.

The service is intended for adults 18 and older. We do not knowingly collect personal information from children under 13 (COPPA, 16 C.F.R. Part 312) or maintain accounts for anyone under 18. If a child has provided us personal information, contact us and we will delete it promptly.

We serve users worldwide from infrastructure in the United States. For transfers out of the EEA, UK, or Switzerland we rely on the European Commission's Standard Contractual Clauses (Module Two/Three as applicable) plus supplementary technical measures; UK transfers use the UK Addendum. Transfers from Canada occur under PIPEDA's accountability principle with comparable safeguards, from Brazil under LGPD Article 33 mechanisms (including SCCs), and from Australia under APP 8 with comparable protection commitments. EEA/UK users may lodge a complaint with their supervisory authority (or the ICO in the UK); we will provide our SCC-executed DPA on request.

Your EEA/UK rights include access, rectification, erasure, restriction, portability, objection to legitimate-interest processing, and withdrawal of consent, exercisable at legal@4eye.me.

If we determine that personal information was subject to a breach of security, we will notify affected individuals without unreasonable delay as required by every U.S. state's breach-notification statute (as New York residents under Gen. Bus. Law § 899-aa and elsewhere), HHS-style timelines do not apply, but where GDPR/UK GDPR applies we will notify the competent supervisory authority within 72 hours of becoming aware unless the breach is unlikely to result in risk, and we will keep a written incident log.

When we make a material change to this policy or to the Terms of Service, we will automatically notify every registered account holder by email at least 14 days before the change takes effect, summarizing what changed, and we display a notice banner inside the app. Non-material edits (clarifications, typo fixes) update the version line at the top without individual notice. If a change affects an active paid subscription in a way you do not accept, you may cancel before the effective date without penalty.

Version history: v1.0 (May 31, 2026, initial publication); v2.0 (August 22, 2026, dual-audience rewrite covering business customers, payment-consent flow, U.S. state and international rights).

Privacy questions, data requests, appeals, and security reports: legal@4eye.me. We correspond by email only and do not publish a postal address.