SteadLog
Back to SteadLog

SteadLog Privacy Policy

Effective date: November 8, 2026

Wild Flowers Tech LLC operates SteadLog, a private maintenance logbook and household knowledge base ("Wild Flowers Tech," "we," "us"). This policy explains what information SteadLog collects, how it is used, and the choices you have. The short version: your household records exist for you and the people in your household — we don't sell them, we don't show ads, and we collect only what the product needs to work.

Information we collect

Account information. When you sign up we collect your email address and, if you provide them, a display name and profile photo. If you sign in with Google, we receive your email address and basic profile information from Google; we never see your Google password.

Household records you create. SteadLog exists to store the records you and your household members choose to enter. Depending on how you use it, this can include:

  • Home details: addresses, year built, appliance and system details (brand, model and serial numbers, install and warranty dates).
  • Vehicle details: make, model, year, VIN, license plate, odometer readings.
  • Maintenance history: tasks, service logs, dates, costs, mileage, and notes.
  • Attachments you upload: receipts, photos, and manuals.
  • Service providers and contractors: names, phone numbers, emails, websites, account numbers, and notes.
  • Pets: names, species, breed, birth dates, photos, and notes.
  • Household utilities: grocery lists and simple budget/finance records (categories, savings goals, and transactions you enter manually — SteadLog does not connect to your bank).
  • The household board and any notes you keep there.

How you found us. When you arrive at SteadLog we note how you got here — any campaign labels in the link you followed (for example from an ad or a guide we published), the domain of the site that referred you, and the page you landed on — and store it with your household record when the household is created. If you sign up with an email address, it is also kept with your sign-in account so it survives confirming your email on a different device. These are short text labels and a page name, not identifiers for you, and they are stored only in SteadLog: we never send them, or anything else about you, to an advertising platform.

Billing information. If you subscribe on the web, payment is handled by Stripe. We store your Stripe customer ID and subscription status; we never see or store your full card number. If you subscribe in the iOS or Android app, payment is handled by Apple App Store or Google Play. RevenueCat helps us manage and verify the mobile subscription. The app passes RevenueCat an opaque account identifier, and we store the subscription status and transaction identifier needed to apply the purchase to your household; we never receive or store your full card number. For a gift purchase, we keep the buyer's email address, purchase and refund status, and the Terms version accepted so we can fulfill the purchase, handle refunds, and provide support. We store a one-way hash of the gift code for redemption and an application-encrypted recovery copy so the buyer can recover it after payment. Optional recipient name and message fields on the printable gift card stay in the buyer's browser; they are not transmitted to or stored by SteadLog.

Feedback and support. If you send feedback or contact us, we keep the message and your contact information so we can respond. A bug report sent from an error screen also includes bounded technical details such as the app release, general screen category, error type, and code stack locations; it does not attach the full page URL or your household records.

Notification registrations. If you turn on notifications on a device, we store that device's push subscription so reminders can be delivered to it: the push service's endpoint address, its encryption keys, and optional diagnostics such as app version, language, time zone, and a device label you choose. We never include your notes or other sensitive record details in notification content, and reminders are sent only for maintenance you opted in to be reminded about.

Technical information. Like most services, our servers keep standard operational logs (such as IP address, browser type, timestamps, requested path, and referrer) used for security and keeping the service running. Access logs are retained for up to 56 days. We also use privacy-limited error tracking that receives code stack locations, the app release and environment, and a generic error description. We configure it not to send account identity, request bodies, authorization headers, household records, attachment contents, navigation history, or the original error message by default.

Connected assistant activity. When a connected assistant changes household records, SteadLog keeps an audit record with the account, token, assistant, household, action, target, version, request identifier, and time. The audit record does not contain household record content or token secrets. Audit records become eligible for deletion after 90 days. A scheduled cleanup removes them in batches, so removal can take longer if cleanup is delayed. Deleting the account or household removes its associated audit records.

Aggregate page counts. We count visits to our public marketing and content pages to understand which pages and campaigns reach people. These counts contain only the UTC day, a reviewed page category, a reviewed campaign label, and a broad referrer category. We do not use cookies, browser IDs, local storage, advertising identifiers, or persistent profiles for these counts. A short-lived keyed digest of IP address and browser type prevents double-counting within a day and is deleted after that day; those values are not retained in the aggregate counter. We honor Do Not Track for this counting.

If you choose Allow analytics, SteadLog sends a small set of named product events used to understand signup, app use, release adoption, and whether the product is useful. These events use a random browser identifier and may include the app release, a general screen or landing category, and cleaned campaign labels. They do not include your email, name, household records, full URL or navigation identifiers, form contents, clicks, session recordings, advertising identifiers, or precise location. Analytics is off until you choose to allow it, respects Do Not Track, and can be disabled from your profile. We do not use advertising trackers.

Information about other people

Household records naturally mention people other than the account holder — family members, contractors, service companies. If you enter information about someone else, you're responsible for having a reasonable basis to store it, and it is protected the same way as the rest of your household data. SteadLog does not contact or market to people mentioned in your records.

How we use information

We use your information only to:

  • provide the service: storing, displaying, and syncing your household records among your household's members;
  • process subscriptions and payments;
  • fulfill gift purchases and handle gift refunds and support;
  • send authentication, account, billing, service, and security messages, plus optional setup emails during a free trial that you can turn off from your profile and maintenance reminder emails you explicitly enable for a household;
  • respond to your feedback and support requests;
  • understand which of our own pages and ads bring people to SteadLog;
  • keep the service secure and debug problems.

We do not sell your personal information, share it with advertisers, or use your household records to train AI models.

Who can see your data

Your household. SteadLog is built around shared households. Members of your household can see the records in that household — that's the point of the product. Think of a household as a shared logbook: don't put something in it you wouldn't want other members to see.

Service providers that run SteadLog. We use a small number of infrastructure providers to operate the service, each bound by their own contractual and legal obligations:

  • Supabase — database, authentication, and file storage.
  • Google — optional sign-in provider when you choose "Continue with Google," and payment processing for subscriptions you purchase through Google Play.
  • Google Workspace — delivery and storage of messages you send to SteadLog support.
  • Stripe — payment processing for paid subscriptions, including its hosted checkout, billing portal, and billing email.
  • Apple — payment processing for subscriptions you purchase through the Apple App Store.
  • RevenueCat — mobile subscription management and subscription-status verification for purchases through the Apple App Store and Google Play.
  • OVHcloud — server hosting (VPS in the United States).
  • Better Stack — uptime, infrastructure monitoring, incident alerting, and privacy-limited application error tracking.
  • PostHog — optional, consent-based product analytics using explicit named events only. Separately from consent-based analytics, we record a small number of operational service counters (for example, that a payment-provider notification could not be matched to an account); these are not linked to any person and contain no personal data.
  • Resend — delivery of authentication and product email, including optional trial setup emails and necessary account, billing, service, or security messages. If you opt into maintenance reminder email, Resend also receives your email address, reminder title, asset name, due date or status, an app link, and a profile-scoped unsubscribe link. Reminder emails do not include notes, home addresses, account data, or attachments.

Legal requirements. We may disclose information if required by law, such as in response to a valid legal process, or to protect the rights, safety, or security of SteadLog or others.

Business transfer. If Wild Flowers Tech is acquired or transfers SteadLog or its assets, your information may be part of that transfer. This policy would continue to apply, and we would notify you of any material change.

That's the complete list. There is no other sharing.

Security

Your data is encrypted in transit (TLS) and at rest. Access to household data is enforced server-side: file attachments and images are served through short-lived signed URLs, invitation tokens are stored only as hashes, and the application backend — not the browser — decides who can read what. Particularly sensitive fields — provider account numbers and Noteboard secrets — are additionally encrypted at the application level and masked in normal app responses until you ask to reveal them. No system is perfectly secure, but we design SteadLog so that a lost link or leaked client credential does not expose your records.

Retention and deletion

We keep your data for as long as your account exists, so your maintenance history stays useful over the years — that's the product.

  • Deleting records: you can delete individual records at any time; deletion is permanent.
  • Deleting a household: a household owner can delete the household, which permanently deletes its records and uploaded files.
  • Deleting your account: you can permanently delete your account yourself from your profile in the app. Deleting requires verifying it's you — with your password or your sign-in provider, whichever you use — and typing a confirmation phrase, and takes effect immediately: your profile and the personal information associated with it are removed, and if you are the last member of a household, its records and uploaded files are deleted with it. We keep only a one-way hash of the deleted sign-in identifier so a deleted account cannot be quietly re-created. If you cannot sign in, use our public account deletion request page or email support@steadloghome.com.
  • Product analytics: your consent choice and random browser analytics data are removed from that device when you disable analytics or delete your account. You may also contact us for help with provider-side access or deletion.
  • Notification registrations: turning notifications off on a device, or signing out there, disables that device's registration immediately; a registration also expires on its own after 60 days without use. Disabled registrations have their push credentials permanently removed after a short cleanup window, and deleting your account removes them with it. Notifications are delivered through your browser or platform's push service (operated by companies like Google, Mozilla, or Apple), which handles messages under its own policies.
  • Email preferences and delivery: maintenance reminder email is off by default and can be enabled or disabled for each household in Notifications. The unsubscribe link in a reminder email stops reminder email across all your households and leaves push and optional setup preferences unchanged. Changing your email address requires fresh opt-in. Delivery pauses when the household subscription is no longer entitled. You can turn optional trial setup emails off from your profile or a setup email's unsubscribe link. Deleting your account removes those preferences and SteadLog's associated delivery records; Resend may retain its own suppression record after a permanent bounce or spam complaint to prevent more mail to that address.
  • Gift purchases: we retain the buyer email, purchase/refund status, and encrypted code recovery data needed for fulfillment, refund handling, and support. Recipient name and message fields used for a printable card are not received or retained.

Deleted data may persist temporarily in provider-managed encrypted backups until those backups expire under the provider's configured retention. Backup copies are isolated from normal product use and are restored only for disaster recovery. We recommend exporting before deleting anything: any household member can export the household's records from the app as a full backup archive, a complete JSON export, a maintenance-history CSV, an attachment archive, and a printable home record. Noteboard secrets are redacted in exports unless you verify it's you — with your password or your sign-in provider — to include them, and provider account numbers are never included. If you need an export the app doesn't cover, contact us at support@steadloghome.com.

Your choices and rights

You can access and correct your records directly in the app, export supported household data, turn maintenance reminder email and optional trial setup emails off independently, allow or disable product analytics from your profile, and request deletion as described above. For anything you can't do in the app, email support@steadloghome.com and we'll help. We respond to all requests regardless of which US state you live in.

Children

SteadLog is not directed at children under 13, and we do not knowingly collect personal information from them. Household records may mention family members of any age, but accounts are for adults and teens 13+.

Changes to this policy

If we make material changes, we'll notify you by email or in the app before they take effect and update the effective date above. Continued use after the effective date means the updated policy applies.

Contact

Questions or requests: support@steadloghome.com