Privacy Policy

About this policy

This policy describes how the team operating 0mrr handles information when you browse, list a startup, buy sponsorship or contact us. For privacy questions and requests, email waihlongchoong@gmail.com.

What we collect and why

Project and sponsorship information

Names, website URLs, descriptions, logos, optional social profiles, advertising choices and contact email addresses. We use these to create listings, run purchased ads and provide management access.

Revenue connections

A restricted, read-only Stripe key, the connected account identifier and scope, calculated MRR snapshots and verification status. Verification processes supported account, product, price, subscription and related customer records. These support revenue checks and refreshes; customer-level records are not part of your public listing.

Payments and delivery

Order amounts, payment status, Stripe transaction identifiers, advertising dates and fulfilment records. Stripe collects payment details through its checkout; 0mrr does not store your full card number or card security code.

Management and support

Email addresses, access-token and session hashes, email delivery records, changes made to projects and messages you send us. We use them to provide secure access, investigate problems and protect existing records.

Visitor and advertising measurements

Pseudonymous browser identifiers, visit timestamps and aggregate visitor counts, plus ad impressions and clicks associated with a campaign, placement and time. These help show audience size and ad delivery. A browser identifier is not a verified person or a cross-device identity.

Startup website clicks

We count deliberate clicks on a startup’s website link. Repeat clicks count again; these totals are clicks, not distinct visitors or confirmed arrivals. Each click has a random event ID to avoid counting a network retry twice. We do not attach a visitor identifier to these click records or set a separate click-tracking cookie.

Network information, including IP addresses and browser information, may be processed to deliver the site, limit abusive requests and identify bots. Our application uses hashed identifiers for its rate-limit records. Hashing is a protection; it does not make every record completely anonymous.

What other visitors can see

Public: your published startup name, website, description, displayed revenue, verification status and date, joining date, cumulative website click count and its tracking start date, and social information you choose to show. Active sponsor material and aggregate ad statistics may also be public.

Private: management and contact emails, restricted Stripe keys, management tokens, and internal order and security records are not included in public project responses. Stripe keys are encrypted on the server; access tokens and sessions are stored as hashes.

The founder privacy option hides your X profile; it does not make your startup name, website or MRR private. Public information can be viewed or copied by others. Hiding it on 0mrr cannot remove copies someone else has already made.

Cookies and browser storage

Management sessions · up to 7 days

Essential session cookies keep authorised startup and sponsorship access available in your browser. Management email links are single-use and expire after 30 minutes.

Visitor counting · up to 365 days

A first-party cookie helps estimate distinct browsers for today, seven days and all time. It may be renewed on return visits. Clearing cookies, switching browsers or using another device can count as another visitor.

Ad measurement · up to 1 day

A separate first-party cookie helps deduplicate ad impressions and clicks. We store a purpose-specific hashed browser identifier with the events.

Browser preferences and saved drafts

Local storage remembers dismissal of the welcome dialog. Session cookies support access to saved drafts and checkout records held on our server. Restricted Stripe keys are not saved in persistent browser storage.

Our visitor, advertising and startup website click measurement honours browser Do Not Track (DNT) and Global Privacy Control (GPC) signals by skipping collection. You can also control or clear cookies in your browser. Blocking essential session cookies may prevent management features from working.

These signals apply to our measurement. They do not prevent the network requests needed to load the website, process a payment or open an external link.

Services involved in running 0mrr

• Stripe processes payments and provides the connected records used for revenue verification. Its own privacy terms apply to its services. Read Stripe’s Privacy Policy.
• Mailgun is our selected provider for management and access-recovery emails. Email delivery involves the recipient address, message content and delivery information. These are service emails, not a newsletter. Read Mailgun’s Privacy Policy.
• Hosting and infrastructure providers process information needed to serve the website, store records and maintain security. Service-provider processing may take place outside your country.
• Website icons and external hosts: 0mrr reads the public website you provide to find and temporarily cache its icon. These automatic icons are served through 0mrr. Custom sponsor images load from their external host, which may receive your browser’s connection information, such as your IP address. Clicking a project, ad or social link opens a service with its own policies.

We do not use submitted management emails as a marketing mailing list or sell them to advertisers. We may disclose information when necessary to investigate abuse, protect the service or respond to a legal requirement.

How long information stays

We keep project, connection, order and management records to provide the service, maintain revenue history, resolve issues and meet applicable record-keeping obligations. These records do not currently have one automatic deletion deadline.

Routine maintenance removes raw ad events and startup website click event IDs older than 30 days. Aggregate startup website click totals are retained with the project. Aggregate ad statistics, visitor identifiers and visitor totals can be retained longer. Expired access tokens and sessions are cleared by maintenance after an additional grace period; expiry does not mean instant deletion of every stored record.

Hiding a startup changes its public visibility. It does not delete its payment or revenue history, and it does not itself stop revenue refreshes. Revoke the connected key in Stripe to stop future access through that key, and contact us to request deletion of information we hold.

Your choices and privacy requests

Use Manage startup to change your public details or hide a project. You can revoke a key in Stripe at any time and manage cookies through your browser.

To ask about access, correction, deletion or other privacy rights available to you, email waihlongchoong@gmail.com. We may need to verify that the request concerns your records. Some information may need to be retained for payment records, security or legal obligations.

Do not email us your Stripe secret key, full payment-card details or a private management link. A project URL and a description of your request are a useful starting point.

Changes and questions

We will update this page when our practices change and show the revised date above. You can find our public support channels on Contact us and our service conditions in the Terms & Conditions.