Terms

Romeo Apps sells fixed-price written diagnostics and bounded public-repository support using public or safely redacted evidence. A diagnostic or support pilot is not a guarantee that a repository maintainer, platform, device, or payment provider will accept a patch or change.

Romeo Apps is operated by Simone Maria Romeo. Stripe checkout may display the shortened operator name "Simone Romeo."

These terms are effective 27 July 2026. Delivery references to a business day mean Monday through Friday in the Europe/Rome timezone, excluding Italian public holidays.

What Is Included

A standard diagnostic includes a written feasibility decision, inspected-evidence notes, a recommended next action, and one short clarification pass for seven days after delivery. Services are written-only unless a separate written agreement explicitly says otherwise.

Closed OSS Proof Desk Pilot

The EUR 275 OSS Proof Desk validation pilot closed on 29 July 2026 after its validation threshold was not met. It is not available for purchase. The one-off OSS diagnostic remains a separate active service. Any future multi-credit offer will require new written terms and explicit buyer acceptance.

Anki Add-on Repair

The USD 55 unit covers one reproducible source-level Anki add-on failure: reproduction notes, the smallest safe patch that fits the accepted path, focused validation, a written handoff, and one factual clarification pass for seven days. It excludes new feature suites, rewrites, store publishing, private collections, credentials, remote desktop access, unsupported forks, and third-party merge guarantees.

Romeo Apps reviews the checkout intake within one business day. If it is safe, complete, and within this unit, Romeo Apps sends written scope acceptance. The three-business-day delivery clock starts at the latest of cleared payment, complete safe intake, and that written acceptance. If one clarification is needed, the order is held for up to five calendar days. If complete safe evidence is not supplied within that hold, or the target is unsafe or outside this unit, Romeo Apps issues a full refund before implementation. Scope is never converted without separate written buyer acceptance.

After written acceptance, the agreed repair packet is the deliverable. Upstream rejection or an unsupported buyer environment does not by itself create a refund right. If Romeo Apps cannot deliver the accepted packet for reasons under its control, the order is refunded in full.

Home Assistant Integration Repair

The USD 95 unit covers one public repository at one pinned commit, one custom integration, one named Home Assistant version, one integration version, one device or model, one reproducible source-level defect, and one root cause. The deliverable includes reproduction notes, the smallest accepted source patch, focused baseline-fail and patched-pass validation, available tests and static checks, update and rollback instructions, residual limits, and one correction round limited to the accepted defect and versions.

Every order receives a fresh written fit review. Romeo Apps accepts only work that can be safely completed within four active engineering hours including the correction reserve. The three-business-day delivery clock starts at the latest of cleared payment, complete safe intake, and written acceptance. If the target is unsafe, excluded, cannot be deterministically validated, depends on unavailable hardware-only proof, or exceeds the effort cap, Romeo Apps refunds the order in full before implementation.

Home Assistant Core changes, new integrations, dashboards, automations, cloud API reverse engineering, firmware or vendor blobs, credentials, remote access, private home data or configuration, device procurement, electrical or physical work, security or regulated work, paid dependencies, production deployment, and guaranteed upstream merge are excluded. Source-level validation is not a claim of physical-device success. Hardware behavior is reported as confirmed only after the buyer safely validates the exact delivered revision on the named device.

WordPress Staging Fix

The EUR 95 unit covers one accepted existing WordPress defect or small behavior change on a buyer-owned staging copy, capped at three active engineering hours including one correction reserve. The deliverable includes baseline reproduction, the smallest safe source or configuration change, focused automated checks, real WordPress workflow validation, relevant desktop and mobile browser evidence, changed-file and residual-limit notes, rollback steps, and one correction limited to the accepted result.

Before payment, the buyer sends a safe fit-check brief containing only a public or staging URL, expected and actual behavior, relevant versions, the plugin or theme involved, backup confirmation, and whether private, customer, or regulated data is involved. Romeo Apps reviews that brief within one business day and replies once with either written fit confirmation plus the frozen before-and-after acceptance test, or a no-fit response. A no-fit response costs nothing.

The buyer uses the EUR 95 checkout only after written fit confirmation, unless Romeo Apps has already supplied the same written approval through another verified thread. Work starts only after payment has cleared, safe staging access and backup ownership are confirmed, and the acceptance test remains frozen. The three-business-day delivery clock starts at that point. If a payment arrives without current written fit confirmation, no implementation begins; Romeo Apps either completes the fit review from safe evidence or refunds the order in full.

One correction may be requested within seven calendar days after delivery only when the frozen accepted behavior still fails on the accepted versions and staging environment. Changes caused by later content, configuration, dependency, version, hosting, or environment changes are outside that correction. New sites, redesigns, migrations, feature suites, open-ended maintenance, production-only changes, launch, DNS, hosting, email, payment setup, malware or security incidents, regulated or customer data, paid dependencies, unsupported forks, and guaranteed upstream merge are excluded. Scope is never expanded without separate written buyer acceptance.

Shopify Theme Repair

Version 2026-07-27. This B2B service is offered only to a person buying wholly for a business, trade, or professional purpose, not as a consumer. The EUR 180 base unit covers one accepted Shopify theme defect or small storefront behavior change on a buyer-owned duplicate unpublished theme or safe development store, capped at four active engineering hours including one correction reserve. Stripe may offer a disclosed local-currency conversion at checkout; the buyer can select EUR. The deliverable includes source and dependency inspection, baseline reproduction, the smallest safe Liquid, JavaScript, CSS, JSON, or theme-configuration change, Shopify Theme Check, relevant focused tests, real desktop and mobile storefront evidence, changed-file and residual-limit notes, rollback steps, and one correction limited to the accepted result.

Romeo Apps reviews checkout intake within one business day. Written acceptance is sent only after payment has cleared, safe intake is complete, buyer authority and duplicate-theme or development-store ownership are confirmed, and the before-and-after acceptance test is frozen. If clarification is needed, the order is held for no more than five calendar days; missing safe evidence after that hold triggers a full refund before implementation. The three-business-day delivery clock starts when written acceptance is sent. If the target is unsafe, excluded, cannot be validated on the primary storefront surface, or exceeds the effort cap, Romeo Apps refunds the order in full before implementation.

One correction may be requested within seven calendar days after delivery only when the frozen accepted behavior still fails on the accepted theme, versions, and safe environment. If Romeo Apps accepts the repair but cannot deliver the accepted packet for reasons under its control, the order is refunded in full. Live-theme publication, checkout or payment changes, Shopify app or Admin API work, paid apps, redesigns, migrations, new stores, content production, product or customer-data handling, SEO campaigns, analytics or advertising setup, domain or DNS work, production credentials, open-ended maintenance, unsupported forks, and launch guarantees are excluded. Scope is never expanded without separate written buyer acceptance.

B2B Accounts Receivable Evidence Audit

The EUR 75 audit covers one creditor, one business customer, one known governing law, English or Italian, up to five related overdue invoices, no more than 30 source pages, and a six-page output ceiling. The output is limited to a factual source chronology, invoice and evidence field cross-checks, missing or mismatched record flags, a factual payment and promise tracker, one neutral three-stage client-review reminder sequence using positions supplied by the creditor, and a descriptive handoff index.

The creditor decides validity, meaning, tone, recipients, timing, interest, fees, settlement, legal rights, and every next action. The creditor reviews and sends every communication from its own systems and receives payment directly. Romeo Apps does not contact the business customer, collect debt, negotiate, threaten action, calculate entitlement, interpret contracts, recommend enforcement, give legal advice, handle funds, or guarantee payment.

Consumer debts, public authorities, disputes, set-offs, credit notes, insolvency or restructuring, guarantees, assignments, litigation, limitation questions, cross-border conflicts, uncertain governing law, excessive or sensitive data, and any request to decide legal rights are excluded. If intake reveals an excluded matter, the audit stops and the order is refunded before processing or, if discovered only after processing begins, the unused portion is refunded and no excluded output is produced.

Checkout contains safe scope facts only. Do not submit invoice, customer, bank, card, credential, or personal data there. Records that are not truly anonymous are accepted only after written fit confirmation and execution of the Article 28 data-processing addendum and order schedule. The three-business-day clock starts after cleared payment, written fit acceptance, executed data terms where required, and complete safe intake.

Digital Skill Packages

A digital skill-package purchase covers the version and files named on its product page. Delivery is by email to the checkout address within the stated window. Skill packages contain instructions and examples, do not guarantee payment or selection, and do not replace legal, tax, security, or regulated professional advice.

Timing

A stated delivery clock begins only after Romeo Apps has accepted the scope and received the complete public or safely redacted evidence needed for that item. The clock pauses while required buyer evidence, decisions, approvals, or third-party access are outstanding.

Evidence Boundary

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

Refund Fit

If the checkout target is unsafe, impossible to inspect, materially incomplete, or outside the selected service, Romeo Apps will ask once for safe clarification, offer a separately accepted scope conversion, or refund the order. The Anki Add-on Repair, Home Assistant Integration Repair, WordPress Staging Fix, Shopify Theme Repair, and B2B Accounts Receivable Evidence Audit clauses above control those services. A digital skill-package order is refunded if Romeo Apps cannot deliver the purchased files to the checkout address; support is available for a corrupted or incomplete archive.

Contact

Email romeo@romeoapps.com for support or payment questions.