FilePeek
Privacy by function

Your preview stays local.

This notice explains how the FilePeek Windows app, its Peek3D engine, and this website handle information.

Updated November 9, 2026 · Publisher: Rashid Al Haqbany

Pre-release notice: FilePeek is not yet available from this website. The support mailbox is being provisioned; its activation status is on the support page. The app will not be submitted for release with a non-working support contact.

Files and previews

When you select a file and press Space, use Browse, or launch FilePeek with a file path, the app reads the selected file locally to produce its preview. This can include file names, paths, file contents and metadata. Files can contain personal or confidential information; FilePeek processes that information only to show the requested preview. The app does not upload previewed files or their contents to the publisher.

Keyboard and Explorer access

FilePeek listens for the Space key to recognize its preview shortcut. It checks the foreground window and reads the current Explorer/Desktop selection. The implementation does not record typed text or maintain a keystroke history. Keyboard monitoring is removed when you exit FilePeek.

Storage and retention

Preview data is held in memory. The app may retain the most recent mesh and file metadata in a memory cache until it is replaced or the app exits. The Microsoft Store version does not create a publisher account or store an activation name, email address, or serial number. Windows and Microsoft Store may retain installation, diagnostic or purchase information under their own settings and policies.

Purchases and Microsoft services

The Store edition uses Microsoft Store services to check Pro entitlements and request purchases. Microsoft handles payment and account information. FilePeek receives entitlement information, such as whether an add-on is licensed and its expiration date; the publisher does not receive your payment-card details through the app. Microsoft’s privacy statement applies to its services.

Analytics, advertising and sharing

The current release candidate contains no publisher-operated analytics, advertising, or crash-upload service. We do not sell previewed file data or share it for advertising. Open file launches the selected file in its associated application; that application has its own privacy practices. Opening an external link uses your browser and the destination’s policies.

This website

This website is hosted through Cloudflare. Delivering and protecting the website involves processing information such as your IP address, request time, URL and browser information. Cloudflare may process operational or security logs under its privacy policy. This site includes no contact-upload form, analytics script, advertising script or application-set tracking cookies. Hosting and security infrastructure may have its own essential behavior.

Support correspondence

If you choose to email support after the mailbox is activated, your email address, message and attachments will be processed to answer your request. Please do not send passwords, payment details, or confidential model files. Share a non-confidential reproduction sample only when needed. Support correspondence is retained while needed to handle the request and meet applicable obligations; you may request deletion, subject to those obligations.

Your choices and rights

You choose which files to preview. Close the preview or exit FilePeek to stop previewing; exiting clears its in-memory cache. Manage Microsoft account, purchase and diagnostic settings through Microsoft. Depending on the law that applies to you, you may have rights to access, correct or delete personal information, object to processing, or complain to your local data-protection authority. Contact details and mailbox status are on the support page.

Children and changes

FilePeek does not intentionally solicit personal information from children. We may update this notice when functionality or data handling changes and will update the date above. The supported public release must match the behavior described here.