Privacy

Romeo Apps uses Stripe-hosted checkout for payment and intake fields. Stripe processes checkout details under its own payment and privacy terms.

Simone Maria Romeo is the controller for Romeo Apps purchase, delivery, support, withdrawal, and first-party website records. The controller's legal contact details are on the business information page. Privacy requests can be sent to romeo@romeoapps.com.

What We Use

We use the target link, wanted outcome, deadline or constraints, checkout email, and any public or redacted evidence you provide to deliver the diagnostic and support one short clarification pass.

Downloadable Local Software

Home Assistant Backup Browser, NAS Diagnostic Export Inspector, Takeout Export Reconstructor, Router Support-Data Inspector, Network Support Bundle Inspector, and Portable XCResult Viewer and HTML Exporter process the source files you choose on your own device. The shipped applications do not upload those backups, archives, logs, support packages, exports, or result bundles to Romeo Apps. Generated reports and reconstructed files also remain on your device unless you independently choose to share them.

The product pages are ordinary first-party web pages. The web server may record standard security/access facts such as time, requested path, IP address, user agent, and response status. A product-page checkout click requests one product-specific static signal path so Romeo Apps can count aggregate first-party purchase intent; it does not contain a customer filename, archive content, email address, or cross-site advertising identifier.

For software checkout, Stripe processes payment and the checkout email. Romeo Apps receives the Stripe Checkout Session, Payment Intent, event identifiers, purchased product, amount/currency, normalized checkout email, entitlement state, delivery attempts, download count and last-download time, withdrawal requests, and refund/dispute state. Recovery and withdrawal-link requests accept the same email and product identifier and always return a non-enumerating response. A withdrawal is executed only after a private email capability is confirmed. Private links expire and are sent through the dedicated Romeo Apps delivery mailbox. API request bodies and private tokens are not written to normal access logs.

Purposes and Legal Bases

Purchase, entitlement, delivery, recovery, support, and withdrawal records are used to perform the contract and requested pre-contract steps. Accounting, tax, consumer-rights, refund, and legally required recordkeeping use is based on legal obligations. Narrow security, fraud-prevention, service-integrity, and dispute records are used for Romeo Apps' legitimate interests where those interests are not overridden by the individual's rights. Optional marketing is not bundled into software checkout and would require its own valid basis.

Recipients and Transfers

Necessary records may be processed by Stripe for checkout, payment and refunds; the Romeo Apps hosting and transactional-email providers for secure operation and delivery; and professional advisers or public authorities where legally required. These providers receive only the fields needed for their role. Some providers may process data outside the EEA under their published transfer safeguards. Romeo Apps does not sell software-buyer data or use it for cross-site advertising.

Required Data and Automated Decisions

Product, payment, and checkout-email fields are required to complete and deliver a purchase; without them, automated checkout and recovery cannot operate. Optional support details are not required unless needed to diagnose a request. Romeo Apps does not make a solely automated decision with legal or similarly significant effects about software buyers. Automated integrity and anti-abuse checks can pause a delivery for human review but do not remove mandatory consumer rights.

What Not To Send

Do not send passwords, private keys, wallet keys, production credentials, live customer data, regulated records, or private data you are not authorized to share.

Home Assistant Repair Evidence

Home Assistant Integration Repair checkout is limited to a public repository or issue URL, software and device versions, and a short description of the failure and safe evidence available. Do not submit access tokens, private configuration, logs containing secrets or household data, IP addresses, device identifiers, executable attachments, firmware, vendor blobs, or remote-access details. Any later evidence must be minimized and safely redacted before written acceptance.

WordPress Staging Fix Evidence

The WordPress Staging Fix fit-check email is limited to a public or staging URL, expected and actual behavior, WordPress and PHP versions, the plugin or theme involved, confirmation of a current staging backup, and whether private, customer, or regulated data is involved. Do not send passwords, access tokens, private archives, database dumps, customer or form data, payment data, production credentials, or executable attachments. Checkout follows only after written fit confirmation. Any later staging access is provisioned separately, after payment, and must use least privilege.

Shopify Theme Repair Evidence

Shopify Theme Repair checkout is limited to the purchasing business and country, a public storefront or safe theme brief, the theme and relevant version, and the failed behavior plus expected result. Do not submit passwords, collaborator codes, access tokens, private theme archives, product or customer records, orders, payment data, analytics, app data, production credentials, or executable attachments at checkout.

After written fit acceptance, a buyer-provided minimized theme archive is preferred. If store access is genuinely required, the buyer sends an official Shopify collaborator invitation limited to Online Store and Themes on a development store or duplicate unpublished theme. Romeo Apps does not request or use Orders, Customers, Finance, Payments, Analytics, Apps, user management, or live-theme publication permissions. Access is revoked at delivery or earlier on request. Private theme source and working copies are deleted no later than 30 days after the seven-day correction window closes, unless a narrower record is required for accounting, fraud prevention, or a documented dispute.

Retention

Service intake, redacted evidence, delivery records, and support email may be retained for up to 90 days after the clarification window closes, then removed when they are no longer needed. Payment and transaction records may be retained longer where required for accounting, tax, fraud prevention, or dispute handling. You may request deletion of eligible service data at any time.

Software entitlement and delivery records are retained while needed to provide purchase recovery, security, refunds, accounting, tax, fraud prevention, and dispute handling. Eligible contact or delivery data can be deleted on request, but deletion may end automated recovery and does not remove records that Romeo Apps or Stripe must lawfully retain.

Your Rights

Depending on applicable law, you may request access, correction, deletion, restriction, portability, or objection, and may withdraw consent where consent is the legal basis. You may also complain to the competent data-protection authority; in Italy this is the Garante per la protezione dei dati personali. A request is verified proportionately before account or purchase information is disclosed or changed. Statutory rights are not conditional on accepting marketing.

Accounts Receivable Audit Records

The B2B Accounts Receivable Evidence Audit uses checkout only for safe scope facts. Do not place invoice, customer, bank, card, credential, or personal data in checkout. Romeo Apps receives records that are not truly anonymous only after written fit acceptance and execution of the Article 28 data-processing addendum and order-specific schedule.

For that audit, the purchasing creditor is the controller and Romeo Apps is the processor. Processing is limited to the documented factual audit instructions. The controller must minimize and redact records, confirm its authority to share them, and exclude consumer, identity, banking, sensitive, and unrelated data. Working copies are returned or deleted at the controller's choice no later than 30 days after delivery unless a narrower record must be retained for accounting, fraud prevention, or a documented legal dispute. The order schedule controls approved subprocessors, transfers, security, access, return, and deletion.

Contact

Email romeo@romeoapps.com for privacy, deletion, software delivery, withdrawal, or support requests connected to a purchase. Postal details are on the business information page.