FullView 360 Privacy Policy

Operator and scope

Daniel Santamaria, owner of FullView 360, an individual in Florida, United States, personally owns and operates the platform. FullView 360 is not a separate LLC. Public notice address: FullView 360; Attn: Daniel Santamaria; 14859 Lyons Road, #122B; Delray Beach, FL 33446, United States. Effective date: October 15, 2026. Application use is private/internal by two individually authorized users, without external customers, public registrations or fees. Documents and practices will be reviewed before external/commercial use.

Website and contact

The public product/legal website is hosted separately on Cloudflare Pages. It contains static pages, without application login, financial-data forms, advertising or analytics scripts. Cloudflare processes network/request information to deliver and protect it. The authenticated application and narrow integration callback are separate surfaces. Infrastructure providers may process service and security metadata under their own policies.

Support: support@fullview360.com. Privacy: privacy@fullview360.com. Cloudflare Email Routing forwards to an owner-controlled Gmail mailbox. Sender/recipient information, messages, attachments and delivery metadata pass through Cloudflare and the destination provider. Forwarding alone does not provide an outbound mailbox. Do not email passwords, OAuth credentials or unnecessary financial information.

Data and purposes

The application processes account/session data, operational records, integration references, reviewed links and audit history. Supported QuickBooks data includes company identity, Chart of Accounts, customers, vendors, invoices, payments, bills and credits, with selected identifiers, contact fields, amounts, balances, dates and allocations. ServiceMinder training data includes supported contacts, proposals, invoices and payments. Authorized users may enter notes and operational financial records.

Data is used only for operational, project-financial analysis, reconciliation, reporting, security, backup and recovery functionality. It is not sold, used for advertising or used for unrelated purposes. QuickBooks is authoritative for accounting actuals; FullView is an operational analysis layer, not a replacement general ledger. QuickBooks production is currently disabled. Sandbox and production credentials, keys, realms and connection records are separate. Current accounting functions read records; they do not initiate payments or write accounting transactions.

Processing and recipients

Render hosts the primary application and managed PostgreSQL database. Intuit handles authorization, tokens and accounting APIs; FullView receives OAuth tokens rather than the user's QuickBooks password. ServiceMinder processes authorized API requests. Cloudflare provides the separate static website, DNS and email forwarding; the app and integration hosts route to Render. No R2 or external recovery-journal service is used. Authorized operators access data for administration/support.

Development/troubleshooting has involved selected source, screenshots and diagnostics through Codex/ChatGPT; this is not a runtime AI integration. No runtime advertising or analytics integration was found in reviewed source. Access and necessary disclosures are limited to authorized users and service providers needed to host, secure, back up and operate the application. Users and the owner control their browser downloads and manually retained copies. No US-only processing/residency promise is made.

Storage, security and recovery

The primary database is Render-managed PostgreSQL; public database connections are blocked and the application uses a restricted database role. Individual authentication and server-enforced permissions protect application access. OAuth tokens and persisted QBO realm/company identifiers are encrypted by the application; other database fields are not all individually application-encrypted. Codes/tokens/provider data are also processed in server memory.

Render supplies managed database recovery facilities. Isolated restore, application login and key recovery were tested. Windows remains rollback only, with its own independent data/configuration and local artifacts. Local exports, diagnostics and stopped restore clusters can also contain data. The owner verified an encrypted portable Render key-recovery copy off-device and stored its passphrase separately. This does not mean every database export is separately encrypted or copied off-device.

Supported recovery suspends processing, locks integrations and rotates a recovery generation in Render configuration BEFORE restoration. Restored integrations cannot automatically refresh or call providers. Quarantine removes restored QBO credentials and pending OAuth state; administrator reconciliation purges QBO caches while preserving independent operational records. Reconnection needs explicit review or new authorization. Raw same-address restoration bypassing the procedure cannot reliably be detected from the restored database alone. No security control guarantees absolute security.

Disconnection and deletion

An administrator's QBO disconnect disables local access before attempting Intuit revocation. Already dispatched requests may finish but cannot continue syncing or silently reconnect. Stored access credentials are removed. Failed revocation retains only encrypted retry material, unusable for ordinary accounting access, with an expiry bounded to at most seven days; expired material is removed when maintenance executes. Remote revocation is not guaranteed during provider outages/configuration failures.

Tested purge controls remove scoped QBO caches and synchronization diagnostics following verified requests. Independently authored operational records are preserved. Embedded accounting-derived values without adequate provenance are flagged for review rather than blindly erased. Incomplete purge is not reported as completed deletion. Disconnecting FullView does not erase original accounting records at Intuit or operational records at ServiceMinder.

Retention and limitations

Retention depends on data purpose, platform recovery, manual copies and applicable legal obligations. Observed POC recovery capabilities included three-day PITR and managed exports retained for at least seven days; these are observations, not a promise that every copy expires then. Local artifact maintenance uses a seven-day age threshold for supported locations. Scheduling, monitoring, active-log rotation and manual external copies still require an operational procedure.

The owner targets deletion of eligible QBO-derived caches within 30 days of disconnection or verified request, except where legally required. This is not a guaranteed deadline. Backups, diagnostic copies, unresolved provenance and provider retention can prevent universal immediate erasure. Logical deletion is not proof of physical sanitization. Every older restored backup must undergo quarantine/review before provider access resumes.

Requests, incidents and changes

Contact privacy@fullview360.com for access, correction, export or deletion. Authority must be verified with minimal necessary information and requests coordinated with the responsible business. The owner tracks verified requests, actions, exceptions and completion, handles incomplete purges, and is responsible for security notices, maintenance and applicable incident response obligations. No fixed response deadline beyond applicable law is promised. Material changes receive a new effective date and notice where appropriate. Review before any external/commercial use.