A precise first check.

Contact support

Email support@ropely.io with the page, workspace/run reference and what you expected. Do not email passwords, API keys or full customer exports. For privacy requests use privacy@ropely.io.

Sign-in email has not arrived

Check spam and the delivery status on the sign-in page. Temporary delivery failures retry automatically, using the same code. Codes expire 15 minutes after the request; retries do not extend that time. Request a new code in the same browser if yours expires. Provider acceptance is not a receipt confirmation. If you contact support, include the approximate request time and the status shown, never the code itself.

Supported starting point

One Stripe account and one application grant ledger. Single-line, one-time Checkout purchases with a shared purchase reference. Quantity greater than one is allowed.

Evidence before conclusions

Missing identifiers, incomplete exports or unknown payment times mean a purchase could not be checked. They do not prove a missing grant.

Additional evidence checks

Recurring evidence accepts explicit period allowances and payment-to-access snapshots, up to 500 expectations and 2,000 application records. Exact UTC periods, carryover evidence, complete ledger coverage and trial/grace policies are required. Inputs and results stay together and can be exported. These are operator-declared snapshots, not automatic subscription monitoring.

Paddle Billing has a read-only connector for up to 100 one-time transactions in a 30-day window, with exact price and ledger references. Its real sandbox acceptance is pending. Adjustments, subscriptions and prorations are inconclusive. Live Paddle access remains disabled until activation.

Team & handoffs shows owner/member permissions, source organization, workload and assignment history. Removing a teammate returns their purchase findings to the unassigned queue. Custom roles and SSO are outside this scope.

Outside the first release

Automatic financial prorations, general multi-line Stripe carts, automatic repairs and usage metering. Recurring balance checks require an explicit supported snapshot contract. Refunds and disputes require review instead of a guessed credit-revocation policy.

What leaves my database?

The PostgreSQL exporter runs in your environment with your source role. It sends purchase-scoped grant snapshots to Ropely. Your source database credentials stay in that environment. Ropely retains imported evidence and saved checks; read-only access does not mean no data is stored.

Does Ropely fix grants?

No. Correct the grant in your application, then run another check. A review or accepted exception records a decision without changing the result.

Can I use this in production?

Create an account to prepare your workspace. Choose a paid plan or agree an assisted-pilot scope before running checks. Review customer-data responsibilities before supplying records. Ropely uses read-only evidence and never repairs source systems. Paddle remains a preview pending provider acceptance.

Where do I recover from a failed setup?

Your workspace Setup checklist resumes from committed imports and saved rules. Review validation on the import page, failed fetches in Connections, and delivery errors in Application ledger. Previous results retain their own evidence and timestamp.