HOW WE WORK · TRUST & SECURITY
A plain-language explanation of where data is handled, what the local tools create, and what you receive when work is complete. DataBasset is independently developed and operated; our dog family is fictional.
Planned service commitments · Review draft. Supported local workflows now include approval, stop controls, task reports, read-only checks and reviewed cleanup. Release-wide validation is still in progress. This website does not run recovery tasks.
Recovery takes place on your computer. Your photos, files and other private information are processed and saved locally. Optional memorial-video creation is separate: it requires your explicit approval to send the selected photo to a named cloud provider.
Before each data-processing step, we explain what we will do, what data we will access and where the results will be saved. We proceed only with your explicit approval. If the scope changes, we ask for your approval again. You can stop the task at any time to end further processing.
Recovery uses read-only inspection. It does not overwrite, change or delete the original files and backups you provide. Exported results are saved separately.
We explain where temporary copies, previews, indexes and task records are saved. You choose which working files to remove and approve the cleanup first. We report what was removed and what could not be deleted. Your originals, backups and the results you chose to keep are left in place.
We process only the data needed to complete your task and understand any related failures. Your private data is not sold, used for advertising or stored on our servers.
Working files and exported results stay on the computer you authorize. If we need your help investigating a product issue, we explain what diagnostic information we need and why. You decide whether to share it.
We identify the source of each result and distinguish original files, retained copies, thumbnails and incomplete records. We tell you what was not found, could not be read or could not be recovered. We do not present thumbnails or AI-generated details as original files, and we do not promise to recover every deleted item.
When the task is complete, we provide a report listing the sources checked, steps performed, results found, exported files and their locations, and anything that failed or remains incomplete. You can review it yourself or share it with a third party you choose.
Start with a supported local backup, a folder of retained files, or a supported device-reading workflow. The goal is to find data that is still readable: an existing original, a retained copy, a thumbnail or a record. A tool cannot guarantee that erased or unavailable content still exists.
The local prototypes have confirmation checks before supported scans and exports. You select what to export and where to save it. This website does not connect to your phone, inspect your files or perform recovery.
Supported backup reading, file inspection, image grouping and exports have local implementations. The photo-grouping prototype uses model files on the computer. The aim is to process recovery content on your computer rather than send it to a remote recovery service.
This is not yet an all-features, independently verified offline product. The website’s Bena is scripted guidance, not a connected local AI assistant. Model installation needs downloads; future checkout needs a network connection. Do not confuse local recovery work with every part of the service being offline.
The fourth commitment limits private data to the authorized task and investigation of related failures. Any request for diagnostic information needs a separate explanation and your decision. Running local tools does not itself grant us remote access to your computer.
Local processing still involves reading data. Depending on the workflow, the tool creates local indexes, previews, temporary extracts, task records and the files you choose to export. These may contain private information. “Local” does not mean that no copies are created or nothing is stored.
The guarded local workflow lets you review and select its managed working files before cleanup, with a separate choice for saved task records. Originals and exported results are excluded. Coverage is limited to supported local folders and readable backups; older experimental tools and device acquisition are not all covered. Cleanup is not secure erasure or removal of every system copy.
Results should identify the source, what is readable and what is missing. Full-size files and small previews must be distinguished. A message record does not prove its attachment exists. AI-generated detail is not proof of original content.
Existing photo delivery manifests include item details, dimensions and file hashes, plus successful exports, errors and diagnostic gaps. Other workflows use different delivery fields. Clear, consistent customer summaries are still being developed.
Our delivery standard: when supported work is completed, give you a work list alongside the results so you can review what was done and what remains unresolved. Local prototype exports already include a delivery list; the readable summary and coverage across all workflows are being unified.
The source type, content categories and limits of the checks.
Originals, copies, previews and readable records, with relevant source details.
Exported files or records, destination and applicable verification details.
Missing files, failed exports, unreadable sources and checks not completed.
A delivery list records the work and its output. It is not proof of every network connection, a security audit or a “zero-upload” certificate. A network privacy receipt has not been implemented.
Illustration only · invented values · not a real customer job or a downloadable report.
The website offers guides, proposed plans and a scripted conversation. It does not scan devices, accept recovery-file uploads or generate live AI answers. Demo chat stays in page memory and clears on refresh. Do not enter passwords or private messages.
Cloudflare hosts the public website and processes requests, including connection information such as IP addresses, to deliver pages. The application has no marketing tracking scripts. A session-only flag remembers that you dismissed the privacy introduction; it contains no conversation or recovery content.
Available in local prototypes: supported local reading and exports, confirmation checks, source and quality distinctions, and delivery manifests. These are development tools, not a public software release or compatibility guarantee.
The new guarded local workflow has approval, stop controls, readable task reports and selected-file cleanup, tested with synthetic inputs. A full local AI assistant, device-wide coverage, a network privacy receipt and complete release validation remain unfinished. No independent security certification or audit is claimed.
The boy, older woman and man beside the outdoor fire bowl in our visual examples are fictional AI-generated people. They are demonstration assets, not customer photos, testimonials, or recordings of real family members.
For the thumbnail example, a 256 × 256 image was created from the generated portrait, then enlarged locally to 1024 × 1024 with Real-ESRGAN. The smaller image is additionally blurred and darkened for display. That display treatment is not the input used for the local enhancement test, and the side-by-side presentation is not a controlled performance benchmark.
AI enhancement may change or invent details; it does not recover the original photo. Memorial clips add generated movements and expressions, with synthesized piano music. The current video examples were generated through a cloud video service with explicit approval; their source files and AI provenance metadata are retained.
These fictional examples do not require customer uploads. Any future cloud video service using your photo will require separate disclosure of the provider, data sent and relevant handling terms, followed by your approval.
No verified scan report, certification badge or review score is displayed here. Dated, verifiable links can be added when obtained. A malware scan does not establish recovery success or privacy protection. Search Console and Bing Webmaster Tools are search-management tools, not certifications.