Account and sign-in details
Name, email address, password hash, time zone, and optional phone number are used to identify the account, protect access, and format reminders in a useful way.
Privacy
Privacy should be predictable: what the app keeps, why it needs it, and what you can control.
Holdward is designed to keep purchase proof and coverage history useful without turning routine warranty tracking into broad surveillance. The goal is limited, legible, job-related data.
What data can exist in the product
Most stored information should support one of four jobs: identify the account, preserve proof of purchase, schedule coverage reminders, or explain recall status.
Product, coverage, and reminder records
Saved product names, brands, models, retailers, purchase dates, prices, warranty windows, and reminder preferences support the vault, coverage status, and alert views.
Proof and recall review history
Receipt files, receipt filenames, upload timestamps, and recall review decisions help keep proof of purchase attached to the right product and make recall status auditable.
Usage activity and beta feedback
Lightweight activity events and feedback notes are stored during beta so the product can measure what people used, where they got stuck, and what improved trust or clarity.
Why the product uses that data
Each category should support a visible product behavior rather than background profiling.
Render a useful vault and proof trail
The app keeps saved products, receipts, and coverage windows together so a claim, return, or recall issue can be reviewed from one record.
Generate reminder schedules and status
Purchase dates, warranty lengths, and reminder preferences are used to calculate coverage deadlines and show whether reminders are pending, sent, or disabled.
Match products against recall sources
Saved product details such as brand, name, and model are compared against recall source data so the app can surface possible matches for review.
Improve the product during beta
Feedback notes and limited workflow analytics help identify confusing states, broken steps, and the parts of the product that genuinely save time.
When data may move beyond the main screen
Some features require processing or delivery outside the immediate page request.
Reminder delivery can vary by environment
Depending on configuration, reminders may stay in logs for local testing or be sent through configured delivery integrations for a hosted environment.
Recall sync reaches external sources
Background recall checks query the configured recall source so the app can refresh alert matches against newer official notices.
Hosted deployments may have their own operator
If you are using a shared or hosted deployment, storage location, retention practices, and support contacts may be managed by that operator rather than by your own machine.
Controls you have
The product should make it straightforward to reduce, review, or remove stored data.
Review suggestions before saving them
OCR and import helpers suggest fields, but they should not silently commit product details without a user choosing to save.
Adjust or disable reminder timing
Coverage reminder offsets can be edited per warranty window, and leaving a coverage window fully unchecked turns those reminders off.
Delete receipts, products, or the account
Receipts can be removed from individual products, saved product records can be deleted, and account deletion removes the owned purchase data tied to that sign-in.