zpe.vc / legal

Privacy notice and terms

Two documents, one page. The notice says what is stored about a person and for how long. The terms say what this operator promises when you use an app here. Both were written from the code that enforces them, on 2026-10-31.

Reading order: the notice, then the terms. For what a page can see about your own request, that is a separate tool at zpe.vc/privacy.

Reaching the operator: the contact form at zpe.vc/contact.

Privacy notice

What this notice covers

It covers everything zpe.vc stores about a person: an account, a message, a payment. It does not cover what a payment provider keeps under its own policy, and it does not cover an app that someone else operates on their own domain.

What a visitor can see about their own request is a different question, answered live on the transparency page at zpe.vc/privacy. That page is a tool, not a legal notice, and it is not this.

Accounts

One door at auth.zpe.vc holds the login for every app here. It stores the account identifier, the credential you sign in with, and a session cookie scoped to .zpe.vc, HttpOnly and Secure.

There is no self-serve delete and no self-serve export today. Ask through the contact form and the operator removes the account and its rows by hand, and the answer says what was removed and what was kept.

Payments

Payments go through one layer, zpe-pay. It is not the merchant. The payment provider configured on the selling account takes the money; that layer starts a charge, checks the provider’s signed message, and records the outcome.

Thing	Kept	How long
The charge	the amount, the currency, a short description, the selling app’s own reference, the provider’s reference, the outcome the provider reported (paid, failed or refunded), and the times it moved.	at most 24 months
The selling account’s provider credential	sealed before it reaches the database. A read returns the provider’s name, whether it is on, the account’s label and the last four characters. The key itself is never returned.	while the account keeps it configured
The provider’s own messages	the event id only, so one signed message cannot be applied twice and a retry cannot count a payment twice.	90 days
Card numbers, CVC, bank details, billing address	nothing, ever. The provider’s own checkout collects them on the provider’s own domain, and this site never sees them.	not stored

Thing

Kept

How long

The charge

the amount, the currency, a short description, the selling app’s own reference, the provider’s reference, the outcome the provider reported (paid, failed or refunded), and the times it moved.

at most 24 months

The selling account’s provider credential

sealed before it reaches the database. A read returns the provider’s name, whether it is on, the account’s label and the last four characters. The key itself is never returned.

while the account keeps it configured

The provider’s own messages

the event id only, so one signed message cannot be applied twice and a retry cannot count a payment twice.

90 days

Card numbers, CVC, bank details, billing address

nothing, ever. The provider’s own checkout collects them on the provider’s own domain, and this site never sees them.

not stored

The layer hands the selling app a charge and its outcome, and nothing about a person: no name, no email, no address crosses it. Whatever an app collects itself is that app’s record, described on that app’s own page.

Nothing on this domain deletes a charge on a schedule yet, so 24 months is the ceiling a record may live to, not a countdown you can watch.

Messages and ideas

A message sent through the contact form is kept so it can be answered, with the address it came from, until the thread is closed and then for at most twelve months.

An idea submitted to the forge is kept thirty days with no address attached, which is what its own page says.

Who may read it, and how long a request takes

The signed-in account, through its own console. An operator acting on a support request, which is recorded. A provider, for the payment it processed.

A written answer to a request about your own data arrives within thirty days, and it names what was held and what was removed.

Your rights

Ask for a copy of what is held, ask for it corrected, or ask for it removed. Ask through the contact form at zpe.vc/contact and the request is carried out by hand. Refusing is only for a record that a payment provider or the law requires to be kept, and the refusal names which.

Terms of service

Who these terms are between

zpe.vc is operated by Zero-Point Energy Ventures, a sole proprietorship. In this document "we" means that operator, and "you" means anyone who signs in, buys or uses an app on this domain.

Apps on this domain are built and operated by us, except where an app’s own page names a different operator. Where it does, that operator’s terms apply as well, and that operator is the seller.

Accounts

You are responsible for the account and for what is done with it. Tell us at the contact form if a credential is lost or an account is being used by someone it should not be.

Payments

Payments are executed by the provider configured on the account that sells the thing, under that account’s own credentials. Our software starts the charge, verifies the provider’s signed message and records the outcome as paid, failed or refunded.

We are not the merchant of record. We do not set prices, we do not take custody of funds, we do not route money to ourselves, and we do not see or store card numbers: the provider’s own checkout collects them.

A refund is requested through the same provider, on the selling account’s instruction, and the charge records it as refunded.

Buying from an app means that app’s price, refund rights and delivery terms apply, not ours.

Acceptable use

Do not attack the service, probe it for other accounts, or use it to get around a payment provider’s own rules. Do not resell access to an app unless the app says you may. We may suspend an account that does either, and a suspended account keeps its records.

Availability, change and withdrawal

We build what runs here and we operate it, so apps change. An app can be withdrawn or replaced. Where a paid thing is withdrawn, we say so on the app’s page and refund what was not delivered. This document contains no uptime promise.

Liability

To the extent the law allows: the service is provided as it is, no warranty is given, and our total liability for any claim is limited to the amount you paid us for that app in the twelve months before the claim. We are not liable for a payment provider’s failure, for an app someone else operates, or for data you lost while holding the only copy.

Ending it

Deleting an account removes its rows, including its charges, except what a provider’s own rules or the law require to be kept. There is no self-serve delete today, so ask through the contact form and it is done by hand. We can close an account that breaks the acceptable-use section, and that account keeps its records until the retention period ends.

Changes, law and contact

The date on this page is the version. A material change is announced here before it takes effect, and using the site after that date means the new version applies. These terms are governed by the laws of the operator’s principal place of business, and the courts there.

Contact, for a support request, a notice or a legal question: https://zpe.vc/contact. Version 2026-10-31.