App Privacy Policy
Effective date: October 25, 2026
James Gregory Fazio, operating as Fazio IT (“Fazio IT,” “we,” or “us”) provides the Fazio IT mobile app. This policy covers network checks, contact requests, optional business-support accounts and the Fazio IT support dashboard. Privacy questions and requests can be sent to [email protected].
Network checks and information on your device
The app saves network measurements, test dates, room names you enter, scores, recommendations, connection type, and device model on your device. It also saves survey progress and your selected tab so you can return to where you left off. You can use network checks and ordinary contact requests without an account. Signing in does not automatically upload or sync your local network-test history.
Network tests exchange generated test data with a service hosted on Cloudflare. They do not upload your personal files or inspect your browsing history, other apps’ traffic, or Wi-Fi password. Cloudflare processes connection information, including your public IP address, to deliver the test and help prevent abuse. Request and operational metadata may be retained in service logs. This occurs when you run a test even if you never send us your results.
Cloudflare’s retained request logs include connection IP addresses, approximate location inferred from IP addresses (such as country, region, and city), request URLs and timestamps, browser/app information, and technical timing and error information. IP-derived location is an estimate; the app does not request your device’s GPS location. We use these records to operate, troubleshoot, and protect the service.
The app checks your connection type and may try a connection to your local router to estimate its response time. This uses local network access where allowed by your device. The current version does not read your Wi-Fi network name or request GPS location. Room names are labels you provide, not GPS measurements.
Local app information may be included in device backups depending on your Apple and device settings. We do not operate those backups. You can export a report through the system share sheet; we receive that report only if you choose a recipient or service that sends it to us.
Contact requests and results you choose to share
When you submit a request, we receive your name, the email address and/or phone number you supply, contact preference, request type, selected service, message, and a request reference. If you attach network results, we also receive a summary that can include the test date, overall score, speed near your router, problem-room names and measurements, and a recommendation.
The summary is shown in the form before you send it. Opening the form does not itself send your results. Please do not include passwords, payment-card details, or information you do not want us to receive.
Requests are sent over HTTPS to our website contact service and forwarded to our business email. The current contact handler also includes a connection IP address in the email and writes the submitter’s name, email address, and IP address to operational logs. The IP address can reflect an intermediary if one is used by the hosting setup.
Optional accounts and business support
Business accounts are optional and available by invitation in account-enabled versions of the app. If you accept an invitation, we process your email, assigned user ID, any profile name you provide, sign-in and session information, and your business memberships and roles. Supabase handles authentication and stores account and support records. Passwords are processed for authentication; our staff dashboard does not display them. Authentication and security records can include sign-in, password-reset, session and verification events, IP addresses, device/browser information, timestamps and error information. Staff dashboard access requires an authenticator, and authentication services process the information needed to verify it.
Business records include the business name, member invitations, membership roles and support-agreement status and dates. Access is assigned explicitly; an email domain alone does not grant membership. Creating new tickets requires an active support agreement. While you remain a member, existing ticket history may remain available when that agreement ends or is suspended. Removing membership removes access to that business's tickets.
Tickets store the title, description, selected troubleshooting answers and summary, replies, status, author identifiers and timestamps. Please submit only information you are authorized to share, and do not include passwords, financial-account details or unnecessary sensitive information. Local network history is not automatically added to a ticket.
Tickets and customer-visible replies are shared with authorized Fazio IT staff and current members of the same business. They are not private conversations visible only to their creator. Internal staff notes are restricted to staff. Authorized administrators manage businesses, access, agreements and privacy reviews; we record administrative actions for accountability.
Email and app notifications
Resend delivers invitations, password-recovery messages and ticket notices. It processes recipient email addresses, message contents and delivery information. Ticket notices identify that there is an update and may include a ticket reference; they do not include the conversation body or private staff notes. Invitation and recovery emails contain security-sensitive links, so do not forward them to others. Our current sending-domain setup has no configured email-open/click tracking. Replies to ticket-notice emails go to our contact inbox; they are not automatically added to the ticket conversation.
If you enable app notifications, we register an Apple push token linked to your signed-in session and account. We do not use the advertising identifier for this purpose. Apple Push Notification service receives that token and a generic support-reply alert containing internal ticket and recipient identifiers so the app can open the relevant ticket after access checks. The alert does not contain your ticket description, reply text, email address or private staff notes. We retain notification delivery status and retry information to operate this service. Notifications can appear on a locked device according to your settings.
You can turn off ticket push notifications in Account or control alerts in iOS Settings. Turning off push does not turn off email notices. Signing out removes the current session's push registration. Already delivered alerts or emails cannot be recalled. Private staff notes do not generate customer notifications.
Why we use this information
We use information to provide network checks, retain your local survey progress, respond to requests, discuss and arrange requested IT services, investigate delivery problems, manage business access and support agreements, answer tickets, send service notifications, handle privacy requests, and protect our services from abuse. The current app has no advertising SDK or advertising-tracking integration.
We do not sell personal information, share it for targeted advertising, or add app inquiries to marketing lists. We use the service providers described below to operate the app and respond to requests.
Who processes information
Our website also uses Cloudflare Web Analytics to measure page visits and page performance, including when you open our website’s policy or terms pages from the app. These reports include page URLs, browser and operating-system categories, country, and page-load and interaction timing. We use Cloudflare reports to view traffic, monitor performance, and help protect against bots and abuse.
Our website and contact service run on a Fazio IT-managed server. Cloudflare operates the network-test endpoint and acts as a proxy for our website, processing requests and connection information to route traffic and protect the service. Google Workspace/Gmail processes and stores our business email, including requests and results you submit. We also use a Google Apps Script tool to review email metadata for retention purposes; it does not delete messages automatically.
Supabase provides account authentication, database storage, server-side support processing and provider-managed database backups. Resend delivers account and support email. Apple delivers app push notifications. Separately encrypted full database recovery copies and recovery journals are stored on our managed server and in private Cloudflare R2 storage. Separately encrypted recovery-key material is backed up in Apple iCloud Drive. Authorized operators may use private temporary copies when testing or performing recovery.
Our website loads fonts from Google-hosted services, which receive the connection requests needed to provide those fonts. That is separate from Google Workspace/Gmail processing our business email.
These providers may process information in the United States and other countries where they operate. United States App Store availability does not mean that all processing occurs exclusively in the United States. More information is available in Cloudflare’s Privacy Policy, Google privacy information and Google’s Cloud Data Processing Addendum, Supabase privacy information, Resend privacy information, and Apple privacy information.
We disclose information to these providers as needed to operate the services described here. We may also disclose information when required by law or reasonably necessary to address fraud, security incidents, or legal claims.
Account deletion and shared support records
In the account-enabled app, open Contact → Account → Delete account. Confirm using your current password. A successful deletion removes your login, profile, memberships, sessions and registered notification devices. It also removes matching invitation records and queued notification records addressed to that account. Your submitted ticket titles, descriptions, troubleshooting summaries and replies are replaced with removal notices.
The business, other members and other people's messages are not automatically deleted with your login. Remaining conversations are queued for staff review because they may quote you or contain information about you. We review that queue proactively; you do not need to send a separate email to initiate that review. You can also contact [email protected] to help us identify additional information that needs review. Removing your account does not itself terminate a business's support agreement or erase other people's service records.
If a customer account requires a records review, a verified deletion attempt keeps the account active and offers Request account deletion in the app. You can submit that request using your current password and view its reference and status on the same screen. We aim to acknowledge review requests within 2 business days and complete the review and active-account deletion process within 30 calendar days. These are service targets, not a replacement for an applicable legal deadline. If more time or legally required retention is necessary, we will explain the reason and next steps.
When the app shows Ready to finish deletion, return to Contact → Account → Delete account, refresh the request status if needed, and confirm using your current password. The final deletion check runs again at that point. An unresolved request does not itself delete or deactivate your login. Staff or administrator privileges require controlled offboarding before account deletion can finish; the customer deletion control cannot remove those privileges. The staff-offboarding procedure must be completed separately. Ordinary business support-history preferences are not themselves a legal requirement to retain personal information.
We retain a minimal account-deletion receipt containing an internal user identifier and deletion date for a target of 12 months. Completed deletion requests and their structured review activity have the periods described below. Separate recovery-journal records retain internal identifiers and deletion, redaction and access-removal events to help prevent restoring removed information or access from an older backup. These limited records do not contain your submitted message text, email address or password, but are not treated as anonymous merely because names are absent. Recovery-journal cleanup keeps events for at least 90 days and removes older events only after recovery checks confirm that the remaining approved backups can safely recover without them. An older backup that still needs an event, failed verification or an unresolved inventory check can delay removal beyond 90 days. Access is restricted. Other privacy-review records identify the affected ticket and review status and remain with the ticket until it is removed.
Account deletion does not remove your phone's saved network tests. Use the separate local-data controls below. It also cannot recall emails, delivered notifications, exports made by authorized recipients or backup copies. Backup restoration requires reapplying completed deletions, redactions and access removals before reopening service.
Retention and deletion
Saved test history remains on your device until you remove it. In the release version, Contact → Delete All removes saved tests, resets the current survey, and clears the unsent request form, including attached results. Deleting an individual saved test also resets its current survey copy and clears an unsent request containing its results. Deletion is unavailable while a request is being sent. Starting over resets the current survey without deleting saved history. Earlier test builds may retain separate survey or form copies after history deletion. Device backups may retain earlier copies according to your backup settings.
Deleting local results does not recall a request already sent to us or erase information held in email, server logs, or device backups.
For inquiries that do not become client work, our retention target is 12 months after the last interaction. Cleanup is manual: we review closed inquiries, check for later conversations and reasons to retain them, and delete those no longer needed. Our review tool only identifies conversations for review; it does not delete email automatically. Messages may remain beyond the target until that review is completed. Messages moved to Gmail Trash normally remain there for up to another 30 days before Gmail permanently deletes them.
Routine Nginx, system, and contact-service logs on our server are configured for approximately 30 days of retention. File rotation and cleanup timing mean this is not an exact per-entry deadline. The period does not apply to the copy of an IP address included in an inquiry email; that copy follows the email’s retention. Client correspondence is separate from the 12-month inquiry target. We retain client records as needed to provide agreed services, document work and transactions, meet legal and accounting obligations, and resolve disputes. Retention depends on the type of record and those needs; there is no single fixed period for all client records. Records relevant to an ongoing request, security incident, or legal claim may also need to be retained longer.
For shared support tickets, our routine retention target is 12 calendar months after both closure and the most recent reply. Open tickets and records under a reviewed hold are excluded. Completed notification delivery records and accepted, revoked or expired invitation records have a target of 30 days from the relevant completion event. Pending deliveries, active delivery attempts and invitations still being sent need operational review. Administrator activity has a target of 12 months. Completed account-deletion requests and their review activity have a target of 12 months after completion and the latest review activity; unresolved requests remain until resolved. Tickets awaiting a personal-information review are excluded from automatic ticket cleanup. These targets do not override removal of your submitted text when your account is deleted.
Automatic application-database cleanup runs daily in bounded batches. It excludes protected records and pauses if recovery checks are unhealthy; outages or a backlog can delay removal. These are retention targets rather than an exact per-record deletion deadline. Provider logs, mailbox copies, recovery copies and other business records have separate retention processes.
Independent encrypted full database backups are scheduled daily and before significant database changes. Each new backup is checked by restoring it in an isolated environment. Full-snapshot cleanup targets copies older than 30 days but preserves the newest two snapshots and the current successful snapshot, which can keep some copies longer. Recovery-journal cleanup separately keeps events for at least 90 days and requires verified replacement backups before retiring older recovery points. Obsolete backup and journal exports may then be retired as part of that safe transition. These checks can delay cleanup; neither 30 nor 90 days is a promise that every historical copy has been erased. Recovery keys have a separate lifecycle and are not removed by archive cleanup.
Our approved recovery process uses verified backups managed on our server and Cloudflare R2. Supabase continues to maintain its own backups with separate provider retention; those copies are not currently approved for live restoration through our recovery process. Recoveries must reapply completed deletions, text removals and revoked access, and review expired records before service reopens. Removing an active record does not instantly remove every historical recovery copy.
Authentication audit logs, email-provider delivery records, mailbox copies and provider-managed backups have separate retention processes and may remain after an active record is deleted. Our application cleanup does not automatically purge all of these provider records. Service-provider logs and backup copies follow the applicable provider settings and retention processes. Our server-log period is not a promise that every provider copy expires at the same time.
To request access to, correction of, or deletion of information you sent us, email [email protected]. We may need to verify that the request is yours. We will handle requests according to applicable law and explain any information we must retain. You can stop future submissions by not sending a request and stop future test traffic by not running tests.
Security
We use HTTPS for app submissions and network tests. No transmission or storage system can be guaranteed completely secure. Keep your device protected and avoid sending unnecessary sensitive information.
Children and regional scope
The app is intended for adults and is initially offered through the United States App Store. It is not directed to children under 13. If you believe a child has submitted personal information through the app, contact [email protected] so we can investigate and arrange deletion as appropriate.
Changes and contact
We may update this policy as our app or practices change. The published policy will show its effective date, and we will provide additional notice or obtain permission when required. Contact: [email protected].