RenoTally Privacy Policy

Overview

RenoTally is a local-first renovation cost worksheet. It has no account, no ads, no backend, no contractor marketplace, no payment processing, no material calculator, no legal form generator, no insurance claim system, no tax or accounting workflow, and no required cloud sync.

Information you enter

RenoTally can store renovation project titles, project currency codes, room or scope labels, scope templates, vendor or payee labels, planned budgets, estimates, deposits, progress invoices, final payments, unpaid invoices, refunds, credits, allowance entries, selected-cost changes, receipts, invoices, quotes, progress photos, due dates, decision deadlines, follow-ups, reminder alert state, notes, cost review totals, export contents, and local delete or reset state that you choose to create.

Storage and sharing

RenoTally is designed to keep project details, project currency codes, scope templates, vendor or payee labels, cost rows, reminder due dates, reminder alert state, attachments, cached exports, and cost review totals on the current device. These project details do not leave the device through RenoTally unless you choose to export or share them.

Renovation project details, reminders, and exports

RenoTally keeps the amounts, attachments, reminders, and notes you enter. It does not decide whether an amount is fair, whether you should pay or withhold payment, whether a quote is acceptable, or whether an export is suitable for legal, tax, insurance, accounting, warranty, permit, code, or construction-compliance use.

User-facing data inventory

• Persisted records: Renovation projects, project currency codes, room or scope labels, scope templates, vendor or payee labels, cost rows, allowance decisions, attachments, reminder dates, reminder alert state, notes, and cost review totals stay on this device.
• Transient search and filters: Ledger route selection and visible filters are workflow state; RenoTally does not store search-query history.
• Generated exports: CSV review files and handoff preview text are generated from the selected project when you open the export route.
• Cached or prepared exports: Cached exports can stay with the local project until the project is deleted or local reset is used; exported/shared copies outside the app are controlled outside RenoTally.
• Notification state: Reminder due dates and reminder alert state are stored with project rows. iOS notification permission controls alert delivery.
• Recent history: No separate recent-history list. Timeline rows, archived scopes, and archived cost rows are saved project records.
• Clear or reset controls: Use project, scope, timeline, allowance, and reminder delete/archive controls, or local reset, to remove projects, cost rows, reminders, pending alerts, attachments, and cached exports.

Analytics, Logs, And Diagnostics

RenoTally imports the shared analytics wrapper, but the current app runtime creates it with analytics disabled. Product events are therefore not emitted by this app build.

The app's local event names are limited to workflow states such as create, update, archive, export, reminder, attachment, calculator, support, or screen events. They must not include project names, vendor and payee labels, scope templates, cost rows, amount values, reminder state, notes, exports, and screenshots you choose to share.

Debug builds used by developers may print the event name and analytics pipeline to the local debug console. Release builds do not write these analytics logs. RenoTally does not include a third-party analytics SDK, advertising SDK, attribution SDK, third-party crash-reporting SDK, IDFA use, App Tracking Transparency prompt, account tracking, or cross-app tracking.

Apple may separately provide App Store, TestFlight, crash, diagnostic, or aggregate App Analytics reports through Apple-operated systems, App Store account controls, iOS privacy settings, or diagnostic settings. Those Apple-operated reports are separate from RenoTally's local analytics wrapper. The App Store privacy label lists data Darts Creative collects through its own systems, such as user-initiated support emails, and does not treat local-only event names as uploaded analytics or tracking.

Support requests

If you contact product support at support@dartscreative.com, the email address and details you send are used to answer the support request.

Support screenshots, logs, and email attachments can include private app data if you include them. Do not send contractor names, vendor costs, payee details, invoices, permit details, insurance claim details, legal notes, tax notes, project photos, exports, or screenshots that identify a renovation unless support explicitly asks for a redacted example.

What RenoTally does not use

RenoTally does not use advertising SDKs, third-party analytics SDKs, account tracking, hosted sync, contractor marketplaces, price-comparison feeds, material takeoff calculators, payment processors, legal form systems, lien tools, insurance claim systems, tax or accounting integrations, permit databases, inspection checklists, code-compliance systems, or remote AI processing.

Your choices

You control what project facts, currency codes, scope templates, vendor or payee labels, cost rows, allowances, receipts, photos, reminders, notes, exports, and shared files you enter, keep, delete, export, or share. Review exported review files before sending them to another person or storing them outside the app.

Public routes

• Privacy policy: https://apps.dartscreative.com/en-in/apps/renotally/privacy/
• Support page: https://apps.dartscreative.com/en-in/apps/renotally/support/

Contact

• Privacy requests: privacy@dartscreative.com
• Product support: support@dartscreative.com