Perfilo is published by an independent iOS developer (Apple Developer Team ID ZM8LF8494F). For any privacy question, write to captainlongevity@gmail.com.
Is there a Perfilo server holding my contracts and performance records?
No. There is no Perfilo server and no Perfilo account. Your contracts, performance events, attached photos, CPARS ratings, rebuttal drafts, and CDA claim notes live in this app's local SwiftData store on your iPhone. We cannot read them, restore them, or move them.
Does Perfilo connect to CPARS or any government system?
No. Perfilo makes no connection to the Contractor Performance Assessment Reporting System (CPARS), to any contracting agency, or to any government or cloud service. It cannot submit a comment, file a rebuttal, or read a rating on your behalf. Everything you see is information you entered, plus bundled reference content. The references to FAR 42.15, the Contract Disputes Act, and CPARS procedure are static lookup material drawn from publicly available federal regulations.
What about the photos I attach to a performance event?
Photos you take with the camera or import from your photo library are stored locally as image data on the performance event you attached them to. They are not automatically uploaded by the App to the developer; Perfilo declares no cloud container and has no backend. They may be included in your standard iOS Backups along with the rest of your on-device data.
Device-backup contents and recovery depend on your system settings, a successfully completed usable backup and Apple’s restoration process; enabling backup alone does not guarantee recovery of every record or original file. We cannot retrieve or restore your device backups.
Do you collect analytics, crash logs, or an advertising identifier?
No. There is no analytics SDK, no crash reporter, and no advertising identifier. We do not know how often you open the app, which screens you visit, how many contracts you track, or whether you subscribed — except through Apple's standard, aggregate developer sales reports.
A note on Controlled Unclassified Information (CUI).
Federal contract work can involve CUI. Perfilo is intended for your own personal work notes; the app asks you not to paste CUI into it. Summarize facts in your own words rather than copy sensitive source material. Record storage is local, but any PDF or Calendar event you choose to create can expose its included details to your selected destination or calendar account.
Does anything go to my iCloud or Apple ID?
Perfilo does not declare the iCloud entitlement; there is no CloudKit container and no remote sync. Your records may be included in your standard iOS Backups (iCloud Backup or Finder) when those are enabled — that is Apple's normal backup behavior for on-device data, not a Perfilo feature.
This data may be included in your standard iOS Backups when you have those enabled. We do not have access to your iOS Backups. If you delete the app without an iOS Backup available, your data cannot be recovered. There is no in-app export, import, or backup feature beyond the defense PDF you choose to generate.
aps-environment entitlement.Perfilo offers an optional Pro tier (a monthly and an annual auto-renewing subscription) via Apple's StoreKit 2. When you subscribe, restore a purchase, or when the app verifies your entitlement, your device communicates directly with Apple's servers. Perfilo receives only the entitlement status (active or inactive) and a purchase identifier. We do not see your Apple ID, payment method, billing address, or transaction history. Apple's handling of subscription information is governed by Apple's Privacy Policy.
You can revoke any of these at any time in iOS Settings > Perfilo. Perfilo requests no microphone, no location, no HealthKit, and no contacts permission, and there is no PDF or file import.
Perfilo is a personal recordkeeping and reference tool for U.S. federal contractors. It is not affiliated with, endorsed by, or connected to the U.S. government, the CPARS system, or any federal agency. It uses no government logo or mark, implies no official endorsement, and submits records to no government system. It does not provide legal advice, does not determine whether a CPARS rating is justified, does not predict the outcome of any review, and does not guarantee that any record will satisfy an agency, a board, or a court. References to FAR, the Contract Disputes Act, and CPARS procedure are reference-only.
Perfilo is a professional business tool intended for U.S. adults who manage federal contracts. We do not knowingly collect any information from anyone, including children.
You control the App’s local records; Calendar, shared files and prior backups are separate copies with their own retention. To delete all Perfilo data, delete the app (and remove it from any iOS Backups you have saved). There is no remote copy for us to delete.
Perfilo is published in English and marketed in the United States. Its reference content concerns U.S. federal procurement. The App does not route records through a developer-operated record server. Apple services, legal-page hosting, support correspondence and any sharing destination you choose may process information outside your country under their own policies. Those services are separate from the App’s local record storage.
If a future release ever changes how the app handles data — for example, if a later version ever introduced 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.
Deleting a contract also deletes its performance events and CPARS ratings; deleting a rating also deletes its rebuttal drafts and CDA claims after a successful save. There is no Recently Deleted or full-database archive import. Generated PDFs and letters cannot reconstruct the deleted record tree. Original system media, shared files, Calendar copies and earlier backups are separate from App record deletion.
Privacy questions: captainlongevity@gmail.com
On iOS 17 and later, the Calendar action requests write-only access and does not import existing events. Event titles, dates, notes and alarms created by the app are saved to your system calendar, which may sync to a calendar-account provider or be visible to people sharing that calendar. These Calendar copies are outside the app’s local database and App Lock; deleting an app record or uninstalling the app does not guarantee removal of every calendar or synced copy. Manage those copies in Calendar and the relevant account.
These legal pages are hosted on Vercel. Opening a page sends ordinary request information, such as the IP address, browser information and requested URL, to the host for delivery and security; see Vercel’s Privacy Notice. This website request is separate from App record storage. If you email support, we receive the address and information you choose to send so we can respond. Send only the details needed for that request.
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; publishing this document does not update an installed App.
The updated App checks contract, performance-event and rating form saves and confirmed deletion. A failed write keeps original stored fields, inline photo bytes, linked rating/rebuttal/claim history and the current open form for retry, without rolling back unrelated pending edits. New form text and chosen photos remain temporary until Save succeeds; Cancel does not commit a new record. Opening and closing the photo upgrade page keeps the open event form. The Pro response screen prepares missing rebuttal and claim rows in a checked save outside view rendering, with retry after a failed preparation. Opening this screen can therefore save initially empty organizer rows. Point additions, deletions, event citations, response-stage and claim-date changes are checked; a failed new point keeps its entry text. Claim notes remain live edits and attempt saving as you type, with Retry saving claim notes after failure. The latest in-memory text is not a restart-proof draft; PDF generation first requires a successful flush. A failed reminder or widget read keeps the earlier plan or snapshot. Notification scheduling, delivery, Calendar copies and sharing remain separate from database commits.
The stored claim date and its six-year arithmetic comparison are retained without changing existing values or treating an older entry as a verified accrual date. The App now labels this as recorded date + 6 years, not a legal filing deadline, in the organizer, generated PDF, Calendar action, reminders and widget. FAR 33.206 generally measures a contractor claim period from claim accrual, with possible shorter agreed periods and exceptions; the App does not determine accrual, exceptions or the applicable filing limit. Confirm the actual deadline and official process with a government-contracts attorney. Updating this App cannot relabel Calendar events, shared PDFs or notification copies already created by an older version; review those separately. No record is submitted to CPARS or a government system, and no database archive import or guaranteed recovery is added.
These changes require the updated App binary. Publishing this document does not update older installed versions.