How the record, and the people in it, are held.

Tidewater Steward Co, LLC, doing business as Wrenmont (“Wrenmont”, “we”, “us”), provides an invitation-only operating record for significant homes. We are based in Williamsburg, Virginia, United States.

This policy covers wrenmontproperty.com, access requests, the team application, the owner portal, the field application, document intake, Ask Wrenmont, and on-site or remote Record Builds we perform for a customer.

It does not cover Wrenmont Steward household membership, a customer’s own vendors, or any site we do not control.

Contact for privacy matters: office@tidewatersteward.com.

Account holders and prospects. People who request access, sign in, pay, or administer an organization. We handle this information as a business acting for ourselves.

People inside a property record. Household members, staff, vendors, guests named in a note, names printed on a warranty, faces in a field photograph, phone numbers in a vendor file. We handle this information as a processor on the customer organization’s instructions. The organization that owns the record is responsible for telling those people what it stores and for having a basis to store it.

If you are a household member or a vendor and you want a correction or a deletion, start with the organization that holds the record. We will support that organization. We will not open one organization’s record because an individual wrote to us, except where the law requires us to look.

From an access request. Name, email, telephone if given, organization, role, properties under care, and what the person is trying to solve. A request does not create an account. We keep it long enough to review fit and to answer, then as needed for a short record of who asked.

From an account. Name, email, organization, role, property assignments, authentication data, device and session data needed to sign in and to keep the session honest, billing contact details, and the seats and properties on the order.

Inside the Customer Record, when a customer chooses to put them there. Property addresses and descriptions; zones, systems, equipment (manufacturer, model, serial, install date, useful life, replacement assumptions); service history; inspection notes; photographs and scans; manuals, warranties, invoices, permits; vendor names, trades, after-hours numbers, licence and insurance standing, internal notes; contracts and coverage dates; knowledge-base items including shutoff locations, access procedures, and — where the customer stores them — codes and key locations; project files; owner-facing summaries; messages or questions typed into Ask Wrenmont.

From the field application. The same record scoped to that user, plus photographs, scans of equipment, task completions, and the fact of a sign-in from that entrance.

Automatically, when you use the site or the application. Approximate location at a network level, browser and device type, pages or views needed to operate and secure the service, and diagnostic logs. We do not run advertising pixels on the marketing site, and we do not sell or share personal information for cross-context advertising.

From payments. Our payments processor collects card or bank details. We receive confirmation, last four digits where provided, and whether a charge succeeded. We do not store full card numbers on our own systems.

From an on-site or remote Record Build. Notes, photographs, and documents gathered with the customer’s arrangement, written into that customer’s record.

We do not want children’s accounts. The service is for adult operators of significant homes.

We do not require government identity numbers, health records, or payment-card PANs to operate the record. If a customer uploads a document that contains them, that is the customer’s choice and the customer’s responsibility.

We use information to:

• review invitations and decide fit
• create and administer organizations, users, roles, and property boundaries
• hold and display the property record
• run field workflows, document intake, extraction proposals, and Ask Wrenmont
• bill, collect, and account for fees
• keep an append-only audit trail of who changed what, when, and on which property
• secure the service, diagnose faults, and prevent abuse
• answer a customer or a regulator when we are obliged to
• send service notices (access, security, material changes to terms or this policy)

We do not use the contents of a Customer Record to train a general model for other customers. Extraction and Ask Wrenmont run against the records the asker is permitted to see, in order to serve that organization.

We do not sell personal information. We do not share it for advertising.

Every record belongs to exactly one organization. That boundary is enforced by the database’s own row-level policies. A query that reaches for another organization’s property returns nothing.

Inside an organization, roles see different amounts of the record. Access can be limited to named properties.

Alarm codes, key locations, security procedures, and confidential documents can carry a sensitivity level that narrows who may read them, including inside the same organization.

Ask Wrenmont is scoped the same way. It does not answer from records the asker cannot open in the application.

Team, owner, and field users sign in through different doors and land in different experiences. They are governed by the same permissions. A separate entrance does not grant separate rights.

Files are not publicly addressable. A file is served through a short-lived, permission-checked link.

An executive snapshot link points at a published point-in-time summary, may expire, and may be revoked. It is not live access to the underlying record.

Document extraction produces proposals, not records. A person reviews each proposal before it becomes part of the authoritative account.

Ask Wrenmont retrieves from the authoritative record, cites sources, and is built to keep uncertainty visible. Generated text can still be wrong. It is an aid to reading the record, not a second record.

Document content and questions are treated as untrusted input, not as instructions that can widen access.

When we send text or a document excerpt to a model provider so extraction or Ask Wrenmont can run, we do so as a processor for that customer, for that task. We do not permit those providers to use Customer Record content to train their general models, to the extent the contract with them allows us to forbid it.

We share personal information only as follows:

• The customer’s own Users, according to the roles and property scopes the customer set
• Snapshot recipients the customer chooses
• Processors who run the service for us, under contract: hosting and database, authentication, private file storage, email delivery, error and uptime diagnostics, payment processing, and model providers used for extraction and Ask Wrenmont. The current core processors include the infrastructure behind our application database and file storage, our payment processor, and the model provider used for Ask Wrenmont and document extraction. A current list is available on request at office@tidewatersteward.com
• Professional service personnel we send to a property, who see what they must see to build the record and no more
• Authorities, when the law requires it, or to protect a person, a property, or the platform
• A buyer of the business, if we sell or reorganize, under the same kinds of limits set out here

We do not sell lists. We do not put a Customer Record in a public directory.

Access requests: kept long enough to review and reply, and for a limited record of inquiries.

Active Customer Records: kept for the life of the organization account.

After an account closes: we make a commercially reasonable export available to the administrator for a reasonable window on request, then delete or irreversibly de-identify the Customer Record from production systems. Security logs, billing records, and legal holds last only as long as that purpose requires. Backups age out on their rotation.

Audit entries cannot be edited or deleted by anyone using the application while the account is live. That is so the record can be trusted. It is not a promise we will keep an audit trail after the organization is removed.

We design the service on the assumption that the contents of a significant home must be narrowly held and that access should be accountable. In practice that means organization isolation at the database, role and property scopes, sensitivity gating, private file storage, short-lived file links, separate entrances under one permission model, and an append-only audit trail the application cannot rewrite.

Transmission to the application is encrypted. Stored records and files sit on systems that encrypt at rest.

No method of transmission or storage is perfect. The customer remains responsible for roles, sensitivity, field devices, and snapshot links.

More detail on how access works lives on the Security page. That page is a product description, not an extra warranty.

We operate from Virginia in the United States. Processors may process data in the United States and in other countries where they run. If a customer needs a written processing addendum or a restriction on location, that is a matter for the order, not for this public policy alone.

We use cookies and similar technology that are necessary to run the site and to keep a signed-in session. We do not use advertising cookies on the marketing site.

You can block cookies in a browser. The application will not sign in without the cookies that hold the session.

Requestors. You may write to office@tidewatersteward.com to withdraw a pending request or to ask us to delete a request we are no longer reviewing.

Users. You may correct your account profile inside the application, or ask your administrator. You may leave the service when your administrator removes you.

Administrators. You control invitations, roles, property scope, sensitivity, snapshot links, and what is stored in the Customer Record. You may ask us to export or close the organization.

People who appear only inside a Customer Record. Contact the organization that holds the record. We will assist that organization where we can.

Residents of the European Economic Area, the United Kingdom, and California have additional rights in some cases — access, correction, deletion, restriction, portability, objection, and (in California) the right to know, delete, correct, and to opt out of sale or sharing. We do not sell or share personal information as those laws use those words. To exercise a right, write to office@tidewatersteward.com. We will need enough to identify you and to know which organization is involved. We will not open another customer’s record on an email alone.

You may complain to a data-protection authority. We would rather hear first.

The service is not directed at children. We do not knowingly create a User account for anyone under 16. If we learn we have done so, we will close it.

A customer may still store a child’s name in a household note. That is the customer’s record and the customer’s responsibility.

If we change this policy in a way that materially affects how we handle personal information, we will post the updated policy here and note the new date. When the change is material we will also notify organization administrators.

Tidewater Steward Co, LLC · Wrenmont
Williamsburg, Virginia
office@tidewatersteward.com