EzWitness™ FAQ

EzWitness is digital witness technology designed to help preserve structured acknowledgment records for important transactions, exchanges, or interactions between people.

For example, if two people meet to buy and sell a used laptop for cash, they may use EzWitness to help preserve a timestamped witness record associated with the exchange.

EPP Lite is a lightweight digital receipt, verification, and documentation service designed to help users create structured records for important exchanges or payments.

EzProofMe 799 is an enhanced proof and continuity service that may support richer transaction documentation features such as attachments and expanded verification records.

Users may use the platform for contractor payments, marketplace sales, caregiving visits, deliveries, vehicle sales, apartment walkthroughs, personal agreements, and other important exchanges.

For example, a buyer purchasing a used motorcycle with cash may want both parties to acknowledge the exchange before leaving the meeting place.

Yes. Certain transaction flows may generate dual receipts or shared verification records so both participants can retain acknowledgment details associated with the event.

EzWitness is designed to help preserve structured continuity and acknowledgment information that may help reduce misunderstandings later.

For example, buyers and sellers may prefer creating a witness acknowledgment before exchanging cash, keys, electronics, or other valuable items.

No. EzWitness does not determine truthfulness or legal outcomes. The platform is designed to help preserve structured digital witness and transaction records associated with interactions between participants.

Yes. Many users may use EPP Lite, EPM799, or EzWitness for small business, independent contractor, service, or marketplace transactions.

A verification code is a unique identifier connected to a transaction or witness event that may help users reference or verify associated records later.

For example, a buyer may provide the verification code to another authorized person to confirm that a witness record exists for a specific exchange.

EzWitness is designed to function as a structured digital acknowledgment and continuity-recording system for important exchanges between people.

Yes. EzWitness may be useful for in-person online marketplace transactions involving electronics, vehicles, collectibles, furniture, tools, and other valuable items.

For example, before handing over cash for a used laptop, both parties may create a short witness record showing the item and acknowledging the exchange.

Yes. Some users may use EzWitness during cash payments, item exchanges, contractor payments, or private sales where both parties want a structured acknowledgment record.

Yes. Vehicle buyers and sellers may use witness records during private sales or exchanges.

For example, before transferring cash and keys for a used car, both parties may create a short witness acknowledgment showing the vehicle and transaction discussion.

Yes. Some users may use witness records during package deliveries, inventory transfers, or item handoffs.

Yes. Contractors and customers may use witness acknowledgments during milestone payments or project completion stages.

For example, after finishing plumbing work or painting services, both parties may create a witness record acknowledging the payment and completed work stage.

No. The platform records acknowledgments and transaction-related information but does not certify item authenticity, quality, legality, ownership, or working condition.

Yes. Some users may use witness records during apartment walkthroughs, key handoffs, or rental-related exchanges.

For example, a landlord and tenant may create a witness acknowledgment during a move-in inspection to help preserve a record of the meeting and related conditions discussed at that time.

Yes. Some users may use EzWitness to help preserve acknowledgment records for informal agreements or exchanges between individuals.

Yes. Some users may use witness acknowledgments during furniture transfers, roommate deposits, appliance exchanges, or property handoffs.

For example, roommates exchanging a security deposit and apartment keys may choose to preserve a digital witness acknowledgment of the exchange.

After completion, the platform may generate a receipt containing event details such as timestamps, verification identifiers, integrity fingerprints, and related transaction information.

Yes. Depending on the service mode, users may share verification links, receipts, or transaction identifiers with authorized individuals.

For example, both the buyer and seller in a laptop transaction may each retain a verification receipt with matching event details.

In many cases, users may access receipts or associated records during the active retention period, subject to account access and platform policies.

Yes. Depending on the platform mode, certain records may support private receipt access along with limited public verification options that avoid exposing sensitive information unnecessarily.

For example, a private receipt may contain more detailed user information, while a public verification page may show only limited confirmation details.

A receipt may include event details such as timestamp, verification code, location-related information, submitted evidence status, and other transaction documentation fields depending on the service mode.

The receipt is designed to preserve structured transaction information and acknowledgments. It does not guarantee truth, payment validity, ownership, or legal outcomes.

For example, if two people acknowledge a cash exchange, the receipt may help document that acknowledgment, but it does not independently judge whether every statement made by either party is true.

Depending on the service mode and browser, users may be able to copy, save, screenshot, print, or share receipt information for their own records.

Yes. Verification codes may help users reference or confirm associated records later, depending on service availability, retention policies, and platform rules.

For example, a buyer may use a verification code to confirm that a witness record was created for a specific exchange.

Yes. Certain flows may allow both participants to keep matching or related receipt information connected to the same transaction or witness event.

Depending on account status, retention policies, and service availability, some records or verification information may still be recoverable during the active retention period.

For example, if a user loses a receipt link shortly after creating a record, they may still be able to access related information through their account or transaction flow if supported.

No. A private receipt may include more detailed information for authorized users, while a public verification page should generally be limited to safer, less sensitive confirmation information.

Witness records and uploads are generally intended to remain accessible only to authorized users, subject to user sharing choices, technical limitations, platform policies, and applicable legal requirements.

For example, a private witness upload may be available inside a user's receipt area, while a public verification page may show only limited confirmation details.

No. Private witness videos are intended to remain accessible only to authorized users unless intentionally shared through approved verification or sharing tools, subject to technical limitations, platform policies, and applicable legal requirements.

Witness videos may be stored for a limited retention period, depending on service plan, platform policy, and future updates. Certain receipt details, timestamps, and verification fingerprints may remain after the video itself expires.

For example, a user may still retain the receipt verification code and integrity fingerprint even after the original witness video is no longer available for playback.

No. Certain uploads or witness videos may have storage limits or retention periods to help manage privacy, storage resources, and system performance.

Depending on the service mode, certain witness media may expire after a defined retention period while verification details, timestamps, and integrity fingerprints may remain associated with the receipt.

For example, the actual witness video may no longer be viewable, while the receipt record may still show that a witness file was created and fingerprinted.

Depending on the service mode, device, browser, and platform policy, users may be able to save, copy, download, or share certain receipt or verification information.

Users should treat receipt and verification links carefully. Anyone with access to a shared link may be able to view the information made available through that link, depending on how the service mode is configured.

For example, if a user sends a verification link to another person, that person may be able to view the limited public verification information connected to that record.

Public pages should generally avoid exposing sensitive uploads unless the platform mode and user sharing choices specifically allow it.

Limited retention may help reduce privacy risk, storage cost, and unnecessary long-term exposure while still preserving key receipt and verification information.

For example, a witness video may be useful shortly after a transaction, while the long-term receipt may only need to preserve timestamps, verification identifiers, and integrity information.

Removal options may depend on service mode, platform policy, user authorization, technical requirements, and applicable legal or operational obligations.

A SHA-256 fingerprint is a cryptographic integrity hash generated from a digital file. If the underlying file changes, the fingerprint changes as well. This helps create a tamper-evident record for uploaded content.

For example, if a witness video is changed after fingerprinting, the altered file would generally produce a different fingerprint than the original record.

If a protected file changes after fingerprinting, its integrity fingerprint may no longer match the original recorded fingerprint. This helps create a tamper-evident verification structure.

No. SHA-256 helps verify whether a specific digital file has changed. It does not determine truth, intent, ownership, authenticity of objects, or legal responsibility.

For example, a matching fingerprint may help show that a file is the same file originally recorded, but it does not independently judge whether every statement inside the video is true.

Supported formats may vary by service mode and future updates. Images may include JPG, JPEG, or PNG. Documents may include PDF or DOCX. Video features may use standardized formats such as MP4 when available.

Standardizing video may improve playback compatibility, reduce storage size, support mobile devices, and help create more consistent integrity records.

For example, an iPhone and Android phone may record video differently, so standardizing the file can make receipt playback and verification more predictable.

No. EzWitness should not be described as a complete deepfake detector. It is designed to preserve structured records, integrity information, and continuity details connected to a witness event.

Future enhanced modes may support deeper media integrity methods such as keyframe fingerprints or continuity checks. These features should be described carefully as tamper-evident support, not as a guarantee that alteration is impossible.

For example, frame-related fingerprints may help identify certain kinds of file changes, but sophisticated manipulation may still require expert review or additional context.

No. Most users can use a normal smartphone, tablet, or computer with a camera, microphone, and internet connection, depending on device and browser compatibility.

Upload quality may depend on network strength and device performance. In some cases, retrying from a stronger connection may help complete processing successfully.

For example, a user recording at a parking lot may need a better cellular signal or Wi-Fi connection before the upload can complete.

Timestamps and optional location information help preserve continuity details associated with a witness event or transaction acknowledgment.

Yes. Caregivers, families, and service providers may use witness acknowledgments to help preserve visit-related continuity records.

For example, a caregiver arriving at a patient's home may use a short witness acknowledgment to document the visit and reduce future misunderstandings about attendance.

Yes. Some caregiving situations may benefit from structured arrival or departure acknowledgments, depending on the service mode and user needs.

Yes. Families may choose to use witness acknowledgments during caregiving visits, medication deliveries, wellness check-ins, or scheduled support appointments.

For example, an adult child coordinating care for an elderly parent may appreciate having a structured acknowledgment of completed caregiver visits.

No. EzWitness is designed for intentional acknowledgment records, not hidden monitoring or continuous surveillance.

Some users may choose to use EzWitness before or during a first-time meetup to help preserve a basic acknowledgment record of the meeting.

For example, two people meeting for the first time after connecting online may choose to create a short mutual acknowledgment before starting their date or meetup.

No. EzWitness is designed around short, intentional witness events rather than continuous recording or surveillance.

Some users may choose to create a basic witness acknowledgment before meeting someone from an online platform or social app.

For example, two people meeting at a public coffee shop after talking online may decide to preserve a simple acknowledgment of the meetup location and time.

Some users may choose to use witness acknowledgments for personal arrangements, exchanges, or mutual understandings between adults.

Some users may choose to create witness acknowledgments during meetings, exchanges, or interactions where preserving a neutral transaction record provides additional peace of mind.

For example, two people meeting for a first-time marketplace exchange at a public location may prefer documenting the acknowledgment before completing the transaction.

Caregiving and dating situations often involve trust, timing, acknowledgment, and personal interactions where misunderstandings may occur later.

No. EzWitness does not determine truth, guarantee payment, ownership, legality, or provide legal judgments. The platform is designed to help preserve structured digital records and continuity information.

No. EzWitness is not a law firm, escrow provider, or notary service. It is a digital witness and transaction-recording platform designed to help users preserve structured records of important exchanges or acknowledgments.

For example, a witness acknowledgment may help preserve transaction details, but users should still seek professional legal or financial advice when appropriate.

No. The platform is not intended to function as a government identity verification service unless future features specifically state otherwise.

No. EzWitness is not a replacement for law enforcement, legal advice, court systems, insurance investigations, or official legal filings.

No. EzWitness is intended for voluntary and transparent acknowledgment between participants involved in a transaction or interaction.

For example, the platform is intended for intentional witness events, not covert recording or secret monitoring.

No. EzWitness is not designed to determine truthfulness, emotional intent, deception, or psychological state. It focuses on preserving structured records and continuity information.

No. EzWitness may help preserve integrity and continuity information associated with uploaded files, but it does not independently guarantee authenticity, ownership, or factual accuracy.

Digital trust systems should be described carefully and realistically. EzWitness focuses on structured acknowledgment, continuity records, timestamps, and tamper-evident integrity support rather than absolute guarantees.

A video witness record is a short structured witness event that may include video, timestamps, continuity information, integrity fingerprints, and transaction acknowledgment details.

For example, two people exchanging cash for a used phone may create a short witness acknowledgment video before completing the handoff.

Short witness videos help keep the process fast, intentional, mobile-friendly, and easier to process across different devices and network conditions.

Yes. Depending on the service mode, both participants may appear together in the witness acknowledgment to help preserve a shared continuity record associated with the interaction.

Yes. Users may choose to briefly show exchanged items, receipts, packages, electronics, keys, or related objects during a witness acknowledgment.

For example, a seller may briefly show the condition of a laptop before completing a marketplace exchange.

No. Most witness events are designed to work with standard smartphone cameras and microphones when supported by the device and browser.

Future platform versions may support additional witness capabilities such as enhanced continuity verification, expanded media support, stronger integrity structures, or additional receipt options.

EzWitness is designed around the idea of helping people preserve structured digital acknowledgment records for important interactions, exchanges, and transactions in an increasingly digital world.

For example, instead of relying entirely on memory later, users may choose to preserve continuity-related witness information connected to important moments between people.