Privacy Policy

This policy explains what [LEGAL ENTITY NAME], [ENTITY DESCRIPTION, e.g. an Ohio limited liability company], doing business as Pactframe, [MAILING ADDRESS] ("Pactframe", "we") collects when businesses send agreements through Pactframe, the Whop app, and signers open, sign and pay for them. It is part of our Terms of Service.

Who decides. For agreements and the personal data in them, the business that sent the agreement decides why and how the data is used; we process it for that business (in GDPR terms, the business is the controller and we are its processor; under U.S. state laws, we are its service provider). For our own operations, such as security, abuse prevention, legal compliance, support and our records of who accepted our terms, we decide (we are the controller). Whop decides for your Whop account, sign-in and payments (an independent controller under its own policy). If you're a signer, the business's own privacy policy also applies.

What Pactframe does

Pactframe lets a Whop business write an agreement, send it, collect electronic signatures, set up billing through Whop, and produce a signed PDF with a signing certificate. Staff use it inside Whop's dashboard. Signers open it from an email link and sign in with Whop.

What we collect

From signers

• Who you are: name, email address and optionally phone, job title and the business you sign for (entered by the business or by you).
• Signing record: your typed signature, the exact consent texts you accepted, when the link was issued and first requested (which can include automated mail scanners), and when you signed.
• Visits to the agreement page: unless the business turns off client activity, each time you view the agreement page after signing in (when the page was on screen, and for how long) and each time you open or download its PDF. The business sees these in the agreement's client journey.
• Device data at signing and consent: IP address and browser user agent.
• Whop sign-in: your Whop account ID and confirmation that your Whop account's verified email matches the address the agreement was sent to. We use Whop's access token once and don't store it; if Whop issues a refresh token we keep it encrypted for at most 10 minutes while we revoke it. If you sign in with a different Whop account, we keep its email encrypted in a cookie for 10 minutes to show you which account was used.
• Payment details, from Whop: if you save a payment method or pay, Whop-issued IDs (setup, member, payment method, payment, membership), the payment method's display name (for example "Visa •••• 4242"), your billing address, amounts, currency, tax, status and decline reasons. For a payment you confirm on the page, we send your IP address to Whop with the charge and keep a copy of that request. Whop's event messages about payments are stored without the card's last four digits, card issuer number, expiry, billing address or phone number (they can still include the card brand and an email address), and are reduced to IDs 30 days after we process them. We never receive or store full card or bank account numbers; Whop and its payment partners (which can include Plaid for bank accounts, Apple Pay and Google Pay) collect those directly in their own forms on the payment step.
• The business's Whop account: unless the business turns off client activity, we tell the business's Whop account when you view the agreement, sign it or save a payment method, with your Whop account ID, the time, and your IP address and browser user agent, so it appears in the business's Whop customer record. We don't send your email address, phone number or the agreement's link.
• Email delivery records: the address we sent to, the message type and the delivery status (for example delivered, bounced or marked as spam).

From businesses and their staff

• Business: Whop business ID, name, legal name, country, logo, brand color, contact email, signatory name and title, tax registration types (we read registration details from Whop but don't store the numbers), payment-method settings, and team access levels. Some of these are filled in from the business's Whop account when the app is first opened.
• Staff: Whop user ID, name, email and Whop role of staff who use the app, what they do in it (an activity log such as "Sent by", "Revoked by"), and their table display preferences. To check a person's role we read the business's team list from Whop without storing it. The sender's name and email appear on the signing certificate.
• Content: agreements, templates, products and prices, and client names, emails and phone numbers.
• Terms acceptance: who accepted our terms for the business (Whop user ID, name, email, role), which version, the text shown, when, and from which IP address and browser. Signers' acceptance at sign-in is recorded the same way.
• Support: emails you send to support@pactframe.app and our replies.

From everyone who uses Pactframe pages

• Service logs: for each request, the page route (never the private link), the result and timing, the Whop business and staff user ID when signed in to the dashboard, and the device type (iOS, Android, desktop) derived from the browser. Our pages also send short technical events (load timing, errors) tagged with a random per-tab ID. Pactframe writes no names, emails or IP addresses into these log lines; they are kept for 7 days. Our host also processes IP addresses and request details for security and delivery under its own terms.
• Cookies and browser storage: only what Pactframe needs to work. On agreement pages: a sign-in session cookie (ends after 30 minutes of inactivity and at most 12 hours), and short-lived cookies (10 minutes) that protect the Whop sign-in and keep an unsent signing form if you're interrupted. In the browser tab: a random ID for the technical events above, and, during a bank check, the ID of the payment being confirmed. In the dashboard: an unsaved copy of a template you're editing, on your device (cleared after about 30 days, the next time the editor opens). Pactframe itself uses no advertising or analytics cookies. Whop (for sign-in and its referral program) and the payment providers on the payment step (Whop's payment form, Plaid, Apple Pay, Google Pay and card-authentication pages) use their own technologies under their own policies.

Why we use it

• To send agreements, sign people in, record signatures and consents, and produce the signed PDF and evidence package, as the business instructs (performing the service; the business's contract with its signers).
• To send emails about agreements: invitations, reminders, signed copies and payment notices, and notices to the business about its agreements, its account and these policies. No marketing email.
• To set up and track billing through Whop, as the business instructs.
• To keep Pactframe secure, prevent abuse and fix problems (legitimate interests).
• To meet legal obligations, keep records of terms acceptance and respond to lawful requests.

We don't sell personal data, share it for cross-context behavioral advertising, use it to train AI models, or use it for automated decisions with legal effects or for profiling. We use Whop data only to provide Pactframe to the business it relates to.

Where it's stored, and who processes it (subprocessors)

Payment providers that Whop uses on the payment step (such as Plaid, Apple and Google) receive payment details directly from you, under Whop's arrangements and their own policies.

Data is stored in Cloudflare's default locations, which are chosen near where the database was created (the United States for Pactframe), and may be processed in other countries where Cloudflare operates, under Cloudflare's Data Processing Addendum, which includes the EU Standard Contractual Clauses for transfers. Signed PDFs, evidence files and exports are private. Ordinary downloads require an authorized session. Some downloads use a single-use link that expires after 2 minutes; anyone holding that link can use it during that time. The end-of-use export (Terms section 8) needs a Whop sign-in as the business's owner on record. Business logos are public at a fixed address so emails can show them, and email programs may cache them. We'll email businesses and update this list at least 14 days before adding or replacing a subprocessor.

Who sees it

• The business that sent the agreement sees the agreement, each signer's status and signing record, payment status and the signed PDF and evidence package.
• Everyone on the same agreement receives the same signing certificate, which shows each signer's name, email, typed signature, times, Whop account ID, IP address and browser, and the sender's name and email. This is what makes the record checkable.
• Whop receives what's needed for sign-in and payments, under Whop's privacy policy.
• Our subprocessors, as listed above.
• Pactframe's operator ([LEGAL ENTITY NAME]), only when needed for support, security, fixing problems or legal reasons.
• Authorities, courts or parties to a legal case, when the law requires it (see Terms section 13).
• A buyer or successor of Pactframe, under this policy.

How long we keep it

• Agreements, signatures, consents, evidence, payment records, activity logs and terms-acceptance records: while the business keeps Pactframe installed. We delete them from our live systems within 30 days after the business uninstalls Pactframe from Whop, after we end its access or stop offering Pactframe, or after a verified request from the business or Whop. The exceptions are records the law requires us to keep, and specific records we must preserve for a legal obligation (Terms section 8). Afterwards we keep only a record that the deletion happened: the Whop business ID and the dates. For a sole proprietor, that ID can identify a person.
• Payment event details from Whop: reduced to IDs 30 days after we process them. Email delivery event details: emptied 30 days after receipt.
• Sign-in data: sign-in attempts are removed about an hour after they expire. A session stops working after 30 minutes idle or 12 hours; its record is removed within about a day after its 12-hour limit or sign-out.
• Download links: expire after 2 minutes; the files behind them are removed by a scheduled clean-up within a day.
• Other working data: payment setups that were never saved, or were replaced, are removed 30 days after their last change; agreements nobody signed that were revoked or replaced are deleted, with their recipients, sign-ins, consents and emails, 90 days after that; Whop event messages that were never processed are reduced to IDs 90 days after receipt; unused download files are removed within a day.
• Backups: our database host keeps a 30-day point-in-time history that can't be turned off, so deleted data leaves it within a further 30 days. We never restore deleted data into service. We keep no copies of deleted files. Copies already emailed or downloaded, and Whop's own records, are outside our control.
• Service logs: 7 days. Support email: as long as needed to handle the request and keep a record of it. Once we delete it, Google removes it from its systems on its own schedule (about two months, longer in its backups). Please don't send agreement contents to support.

Keep your own copy of the signed PDF. Links stop working once the agreement is revoked or deleted.

Your rights

Depending on where you live, you may have the right to access, correct, delete, restrict or object to the use of your personal data, to receive a copy, to withdraw consent, and to complain to a data-protection authority. Some U.S. states give rights to know, delete, correct and opt out of sale or targeted advertising (we do neither), without discrimination.

• Signers: for your agreement data, the business that sent it decides. Send requests to that business (its contact details are on the agreement page and in its emails). If you contact us, we'll pass your request to that business and help it respond. You verify by signing in with Whop as the invited email. For records other than signed agreements, if the business doesn't show a reason to keep your data within 14 days, we delete it within 30 days of verifying your request. A signed agreement is a shared record of every party, so it is never edited: it is deleted as a whole if the business agrees, and otherwise kept only where there is a lawful reason, which we'll explain to you. For data we control ourselves (your acceptance of our terms, security logs, support emails), we answer you directly.
• Businesses and staff: contact us below.

We'll verify a request before acting on it and respond within the time the law requires (normally within 30 days).

Security

We use encrypted connections (HTTPS with HSTS), private storage, encrypted link tokens, hashed session IDs, signed verification manifests, secure HTTP-only cookies, strict content-security rules, and role-based access: the business's staff by their access level, signers to their own agreement, and Pactframe's operator only as described above. No system is perfectly secure. If we become aware of an actual or suspected security breach affecting your data, we will notify the affected business without undue delay, Whop immediately (within 24 hours at most, as Whop's terms require), and, where the law requires, you and regulators.

Children

Pactframe is for businesses and adults. It isn't meant for anyone under 18, and we don't knowingly collect their data.

Changes

We'll post changes here and update the date and version; past versions stay at pactframe.app/privacy/<version>. For material changes we'll notify businesses in the app and by email at least 14 days before they apply. We won't use data we already hold in a materially different way without the consent the law requires.

Contact

Privacy questions and requests: support@pactframe.app (subject "Privacy"), or by mail to [LEGAL ENTITY NAME], [ENTITY DESCRIPTION, e.g. an Ohio limited liability company], doing business as Pactframe, [MAILING ADDRESS].