PaidUp Privacy Policy

1. Who is responsible

ACG Services LLC, doing business as RiloByte (“RiloByte,” “we,” “us,” or “our”), is responsible for the PaidUp information-handling activities described in this Privacy Policy.

PaidUp is offered only to people in the United States who are at least 18 years old and is not directed to children.

2. Scope

This policy covers the PaidUp website, browser application, licensing service, and related customer-support activities. Payhip separately provides checkout, order fulfillment, customer delivery, and license generation. Cloudflare provides hosting, request handling, security, and database infrastructure. Those providers also process information under their own privacy policies.

3. Bill information stored in your browser

PaidUp stores customer-entered bill information locally in the customer’s browser. This may include bill names and amounts, due dates and recurrence settings, autopay indicators, customer-entered payment-method labels, reminder selections, paid or unpaid status, recorded payment amounts and dates, snooze state, payment history, and display information associated with bill records.

PaidUp also stores the selected weekly recap day and whether the welcome screen has been dismissed.

The implemented PaidUp V1 application does not transmit this bill information to the production licensing database or to Payhip. It is not automatically synchronized between browsers or devices.

Local information remains in the browser until it is changed, overwritten, or removed through application or browser behavior. Clearing browser storage, resetting or losing a browser profile, using certain private-browsing modes, or losing the device may remove it permanently. Other users of a shared device, browser extensions, device backups, device-management software, or other software on the device may be able to access browser-local information depending on the customer’s environment.

4. Installation and licensing information

PaidUp creates a random installation identifier in browser local storage. During activation or recovery, the browser sends that identifier and the entered license key to PaidUp’s same-origin licensing API.

The production licensing database stores:

• the PaidUp product identifier and device limit;
• a keyed hash and an encrypted copy of the license key;
• license status and verification timestamps;
• a keyed hash of each installation identifier;
• device-slot assignments and activation, last-seen, and deactivation timestamps;
• keyed hashes of session tokens and session creation, last-seen, expiration, and revocation timestamps; and
• rate-limit records described below.

The licensing database schema does not store customer bill information, buyer names, buyer email addresses, or payment-card details. Encryption and keyed hashing reduce exposure but do not necessarily make licensing information anonymous.

5. Essential license-session cookie

After successful activation, PaidUp places an essential cookie named __Host-paidup_license in the browser. It contains a random session token used to confirm that the browser has an active PaidUp license session. It is configured as HttpOnly, Secure, SameSite=Lax, available throughout the same site, and subject to a maximum lifetime of 180 days. Only a keyed hash of the session token is stored in the licensing database.

The cookie is cleared when the customer successfully deactivates the current browser. It may also expire or be removed through browser controls.

6. Rate limiting and security information

For activation and recovery requests, PaidUp obtains the network address supplied with the request and combines it with the installation identifier to generate a keyed rate-limit hash.

The licensing database stores the resulting hash, the action attempted, a 15-minute time bucket, the number of attempts, and an expiration timestamp. The application does not store the raw network address or raw installation identifier in the D1 rate-limit record.

PaidUp also processes ordinary request information needed to deliver and secure the service. Cloudflare may process IP addresses, traffic-routing information, security information, and other request metadata as part of providing its services.

7. Payhip purchases and license verification

When a customer purchases PaidUp, Payhip and the selected payment provider process the checkout and transaction. Through the Payhip seller account, RiloByte may receive or access information needed to fulfill and support an order, including buyer email, product and order details, transaction status and amount, applied coupon information if applicable, delivery status, and generated-license information and status.

PaidUp and RiloByte do not receive or store complete payment-card credentials through the PaidUp application. Payment information is handled by Payhip and its configured payment providers under their own policies.

When a customer activates PaidUp, the Worker sends the entered license key to Payhip’s license-verification API. A Payhip product authentication secret is sent server-to-server. Payhip returns information used to determine whether the license is enabled and associated with PaidUp. The browser’s PaidUp session token and customer bill records are not sent to Payhip by the implemented licensing code.

Payhip’s privacy policy is available at payhip.com/privacy.

8. How information is used

RiloByte uses the described information as reasonably necessary to:

• fulfill PaidUp purchases and deliver licenses;
• verify that a license is valid and enabled;
• enforce the two-active-installation limit;
• create and validate licensed browser sessions;
• support device deactivation and replacement;
• periodically revalidate licenses with Payhip;
• prevent excessive activation and recovery attempts;
• provide customer support and respond to refund or privacy requests;
• diagnose failures and protect PaidUp’s security and integrity;
• resolve disputes and maintain appropriate business records; and
• comply with applicable legal obligations.

9. Retention

Customer bill information is retained locally in the customer’s browser until it is changed, overwritten, or deleted locally.

RiloByte retains licensing and operational records for as long as reasonably necessary to operate PaidUp, administer and verify licenses, enforce installation limits, prevent abuse, provide customer support and security, resolve disputes, maintain appropriate business records, and satisfy legal obligations. Retention may vary according to the type of record and the reason it is maintained. PaidUp does not promise a fixed automated deletion schedule that its current implementation does not provide.

Licensing sessions have a configured 180-day expiration. Expired session records become eligible for application cleanup seven days after expiration. Rate-limit records expire after their applicable time window and become eligible for cleanup. The current application performs expired-record cleanup probabilistically during activation activity. License and historical device records do not currently have an automatic deletion period.

Payhip and other service providers retain information according to their respective systems, policies, configurations, and legal obligations.

10. Revalidation, replacement, and disabling

PaidUp ordinarily revalidates an active license with Payhip after 24 hours. If Payhip is temporarily unavailable, PaidUp may allow a temporary grace period of up to seven days from the most recent successful verification.

If Payhip reports that a license is disabled or invalid, PaidUp records the disabled status and revokes active licensing sessions. Device replacement deactivates the active installation that has gone unused the longest and revokes its sessions. Customer-initiated deactivation marks the current installation inactive and revokes its sessions. These operations do not automatically delete bill information stored locally in the affected browser.

11. Service providers and analytics

Information may be processed through Cloudflare, which provides Worker hosting, request handling, network security, and D1 licensing-data storage; Payhip, which provides checkout, customer delivery, order administration, license generation, and license verification; Payhip’s configured payment providers; and the applicable email service provider used for customer-support and privacy communications.

PaidUp V1 does not include application-level advertising trackers or third-party behavioral analytics. Service providers may process operational information under their respective privacy practices. Cloudflare’s privacy policy is available at cloudflare.com/privacypolicy.

12. Security

PaidUp uses safeguards including encrypted license-key storage, keyed hashes for license, installation, session, and rate-limit identifiers, secure HTTP-only session cookies, same-origin checks for state-changing licensing requests, and activation and recovery rate limits.

No storage or transmission method can be guaranteed completely secure. Customers should protect their devices, browser profiles, email accounts, and license-delivery messages.

13. Customer choices and privacy requests

Customers may edit or remove locally stored bill information using application or browser controls, clear local browser storage and cookies, deactivate an active browser installation, and contact RiloByte concerning applicable privacy requests.

Clearing browser-local data may permanently remove bill information and may cause PaidUp to treat that browser as a new installation. Clearing only the licensing cookie may require activation or recovery without deleting bill records.

Depending on applicable law, customers may have rights concerning access, correction, deletion, portability, or other handling of personal information. These rights are subject to applicable legal conditions and exceptions.

Privacy requests may be sent to acg.services.in@gmail.com. RiloByte may request reasonable information, such as the purchase email or order information, to verify the requester and locate relevant records. Do not send passwords, complete payment-card information, license keys, or other unnecessary sensitive information by email.

14. United States availability and international processing

PaidUp V1 is offered only in the United States. Cloudflare, Payhip, payment providers, and the applicable email service provider may process information in locations outside the customer’s state or country as described in their respective privacy practices.

15. Changes and contact

This policy may be updated to reflect changes in PaidUp, legal requirements, or information-handling practices. The effective date will be revised when the policy changes, and notice of material changes will be provided where required by applicable law.

ACG Services LLC d/b/a RiloByte
Privacy and customer-support email: acg.services.in@gmail.com

Do not send passwords, license keys, complete payment-card information, or other unnecessary sensitive information by email.