RoadPact is published by Flint Software, an independent iOS developer (Apple Developer Team ID ZM8LF8494F). For any privacy question, write to captainlongevity@gmail.com.
Is there a RoadPact server holding my road's records?
No. There is no RoadPact server. Your roads, parcels, assessments, ledger, meetings, and maintenance events live in this app's local SwiftData store on your iPhone. We cannot read them, restore them, or transfer them.
Does RoadPact handle any money?
No. The shared-cost ledger records assessment amounts, each parcel's share, and a paid or unpaid status that you set by hand. RoadPact does not connect to any bank, payment processor or card network, and it never moves money. Those amounts are records you keep, nothing more.
Do you collect analytics, crash logs, or device identifiers?
No. There is no analytics SDK, no crash reporter, and no advertising identifier in the binary. We do not know how often you open the app, which screens you visit, or whether you subscribed unless we look up the purchase in Apple's standard developer reports.
How does the assessment calculator decide each parcel's share?
The calculator runs deterministic, rule-based math on your iPhone: by frontage (a parcel's frontage divided by the road's total frontage), by equal share (the total divided by the number of parcels), or by a usage share you enter. The state road-law notes are bundled reference content drawn from publicly available statutes (for example, Maine Title 23 and California Civil Code 845). It is a recordkeeping tool, not a tax, legal, or financial calculation.
Do you talk to any town, county, road commission, or DOT?
No. RoadPact makes no calls to any government road authority, county registry, as a records service. References to state statutes are bundled lookup content; opening a source link contacts the selected website.
Do you add anything to my iCloud or Apple ID?
No. RoadPact does not declare the iCloud entitlement and has no CloudKit container or remote sync. Device backups may include local records according to your Apple backup settings and successful completion. Calendar events you add can synchronize through the Calendar account you use; that is separate from in-app record synchronization.
Apple device backups may contain these records according to your settings; verify that a usable backup exists before removing the App. We cannot access or restore your device backups. There is no in-app database export, import or restoration feature. A records PDF is a readable copy, not a restorable database backup.
RoadPact uses Apple StoreKit for an Annual subscription and a one-time Lifetime purchase. The App checks verified transaction information such as product identifiers, purchase dates, expiry, revocation and applicable renewal state, and caches local access information. Apple processes payment; the App does not receive your payment-card details or Apple Account password. See the RoadPact terms for available plans and billing details.
You can revoke any permission at any time in iOS Settings > RoadPact. RoadPact requests no camera, no microphone, no photo library, no location, no HealthKit, and no contacts permission.
RoadPact is a personal recordkeeping tool for shared private roads. It is not legal advice and not a substitute for an attorney. The records it creates are not a legally recorded Private Road Maintenance Agreement, easement, or any binding legal document. It is not a payment service and is not affiliated with any town, county, road commission, department of transportation, or county registry. State references are general information based on publicly available statutes, not legal advice.
RoadPact is intended for U.S. adults. There is no child account or developer-operated record collection. If a child sends personal information to support, contact us so we can address it.
You control local App records; shared files, Calendar accounts and backups have separate retention. Removing the App can remove its local container; generated PDFs, Calendar events, recipient copies and device backups remain separate and must be managed at their destinations. There is no remote copy for us to delete.
RoadPact is published in English and marketed in the United States. The state road-law reference content is U.S.-specific. The App does not upload the local road database to our own server. Apple services, Calendar synchronization, sharing destinations, website hosting and support messages may involve processing outside your region.
If a future release ever changes how the app handles data — for example, if a later version ever introduces any sync, analytics, or third-party integration — we will update this policy and surface the change in the app before that feature becomes available. The "Last updated" date above reflects the most recent revision.
Privacy questions: captainlongevity@gmail.com
These RoadPact legal pages are hosted by Vercel. Visiting them sends ordinary request information, such as IP address, browser information and the requested URL, to the host for delivery and security; see Vercel's Privacy Notice. These pages contain no advertising or analytics scripts. If you email support, we receive your email address and the content you choose to send so we can respond. Do not include sensitive records unless needed for your request.
Deleting a road removes its linked parcels, assessments and assessment-share history, maintenance events and meetings after successful saving. Deleting an assessment removes its share records. Deleting only a parcel leaves existing assessment shares, saved owner names and payment-status history intact; removing a current member is not erasure of that history. There is no Recently Deleted or database import/restore.
Successful direct meeting and assessment deletion requests a reminder rebuild. Successful road deletion attempts cancellation of its known meeting/assessment identifiers and requests a rebuild. Database success does not guarantee completed system cancellation or notification delivery; an earlier pending reminder can remain after a system failure. Previously written Calendar events and exported PDFs remain independent. An external display is not evidence that its original record still exists.
The updated App pauses the normal record interface if its persistent database cannot be opened and only a temporary in-memory store is available. New recording and editing through that interface are blocked. The App keeps the existing database and attachment files rather than treating the temporary empty store as your archive. Database-dependent startup work in that interface is paused; previously scheduled reminders, widget snapshots or independent copies may remain.
Check available device storage, close and reopen the App, and contact support before deleting or reinstalling it. This recovery screen is not a backup, a repair guarantee or an automatic restoration of missing records. Older installed versions may behave differently until updated.
The updated App checks road, parcel, maintenance, meeting and assessment writes, onboarding completion, confirmed deletion and manual paid-status changes. Failed saves keep original stored fields, Decimal amounts, historical share rows, paid/partial/unpaid marks and dates, linked meetings/motions and other pending edits, while current form values remain for retry. Create-form Cancel no longer rolls back unrelated drafts. Road and first-parcel onboarding commit together before selected-road/completion preferences change. Ordinary forms hold their input in memory until Save; they are not restart-proof backups. Removing a parcel updates the current road frontage in the same checked save while retaining historical assessment shares, saved owner names and payment status keyed by the former parcel identifier. Road deletion still cascades parcels, assessments/shares, maintenance and meetings only after a successful save. No payment processing, bank connection or money movement is added.
Assessment title/date/due-date edits preserve stored shares and paid marks. A changed total uses the assessment’s original member identifiers and allocation method, with calculated replacement rows fixed before old shares are deleted; replacing rows and total is one checked save. A successful confirmed re-split still resets paid marks as the existing interface warns. Failure restores the original graph. Adding a later roster member does not silently add them to an earlier assessment. When an original member record is no longer present, changing the historical total is refused rather than replacing shares using missing weights; the stored amount can be kept while editing title/dates, or a new assessment can be created for the current roster. This does not restore a deleted member. The original allocation formulas and free/paid limits are unchanged. Unreadable stored meeting-motion data is retained rather than overwritten with an empty list; the meeting editor explains the read failure and blocks replacement through Save. This is preservation, not recovery of damaged content.
A successful road deletion attempts immediate cancellation of the known meeting/assessment reminder identifiers and requests a rebuild. Other successful meeting/assessment writes and paid-status changes request refresh afterward. Reminder refresh uses strict reads before canceling the previous plan and copies record values before notification awaits; failed reads keep the earlier plan. Superseded plan work is checked before scheduling, but scheduling and cancellation remain separate system operations with possible partial completion and no delivery guarantee. Explicit Add to Calendar on a meeting remains independent: it can create a Calendar event from the open draft before the meeting is saved, and canceling the App form does not erase that Calendar copy. A Calendar failure now reports the failure while keeping the form. Calendar-account copies, original external files, shared/generated PDFs and device backups remain separate. There is no trash, full database import or guaranteed restoration. PDF output is a readable copy, not proof that unreadable or deleted data can be reconstructed.