Know what
you are sharing.

Anonymous and contact forms

An anonymous form does not request an email address through an email field or attach a signed-in audience identity to your response. Free-text answers are not automatically anonymised: if you write your name, email or identifying details, the owner will see them.

Contact forms and coming-soon resource requests ask you to agree to the stated use of your details. We store the submitted answers, the form and question labels, the consent wording where applicable, and the submission time. The owner can read and export these records. Requesting a specific resource is not an automatic newsletter subscription.

Where email delivery is available, a Premium page owner can have Did It Land email a requested resource to you once it’s ready. We first email you a link to confirm your address for that one resource; nothing is emailed to you automatically unless you confirm, and the owner reviews the message before it is sent. Every email has an unsubscribe link. Unsubscribing stops all Did It Land emails to that address; to honour it we keep a one-way hash of the address, not the address itself. If an email to you bounces permanently or is reported as spam, we stop emailing that address the same way. Our email service tells us whether each email reached your mail server, and the owner sees that. There is no open or click tracking.

What stays on your device

Your selected takeaway blocks are stored in this browser so they can remain selected on a later visit. Checklist ticks last for the current visit. The editor also uses browser storage for draft recovery and locally saved demos. Browser settings or clearing site data can remove this information.

Downloading a takeaway file creates a file on your device. Copying an AI brief places the selected content and its source links on your clipboard. You choose where to paste or share it.

Public pocket cards and offline copies

An owner can publish their own contact details on a compact pocket card. Those details are public and separate from private audience submissions. A contact QR embeds the published details only when the owner enables it; downloaded contact files and scanned copies cannot be recalled.

Home-screen installation does not automatically save an offline copy. If the owner permits it, Save card offline explicitly stores this public card, its QR codes and contact file in your browser for seven days. No drafts, sign-in information, inbox data, audience forms or submissions are saved or queued. External portraits are replaced with initials in the saved copy.

Online checks refresh published changes without extending the seven-day window and remove withdrawn cards or removed offline permission. Remove saved card clears the local copy. Browser storage can be cleared or evicted, and a disconnected copy cannot be withdrawn instantly.

Page visits and clicks

When you open a published page, it adds one to that page’s view count for the day. If you arrived by scanning the owner’s QR code, it also adds one to the day’s QR count; the code carries a short tag for this, which the page then removes from your address bar. Opening a link, button or other marked item on the page adds one to that item’s click count for the day.

That is all that is recorded: a page, a calendar day, what kind of action it was, and a running total. No cookie is set and none is sent with these counts. Nothing is kept in your browser for them. We don’t store your IP address, device or browser details, location, the site you came from, or a visitor ID, and we don’t estimate unique visitors. The counts can’t be connected to a form you submit or to any other visit, including your own later ones.

If your browser sends Do Not Track or Global Privacy Control, the page counts nothing at all for your visit. Requests that look automated are ignored. Owners see daily totals for their own pages only. Totals are kept for up to 13 months, then deleted.

Resource interest and abuse prevention

When you download a selected pack or copy an AI brief from a live page with collection open, the app can count saves for those blocks. Owners see aggregate block counts, in total and per day. Those counts are not connected to contact submissions and do not measure understanding or unique visitors.

The server processes request information to limit repeated submissions and inflated counts. Its abuse-control records use temporary hashed request buckets, and resource-save replay checks use hashed random request identifiers. The application does not store a raw IP address in these records or the audience submission table. Random submission identifiers help prevent duplicate responses on retries.

Hosting infrastructure may process technical request information separately. Third-party links and remotely hosted images on an owner’s page are served by their respective providers, which receive the requests needed to open or display them.

Accounts, drafts and AI

Page owners sign in using their email address. Authentication uses session cookies. Drafts and inboxes require the owner’s signed-in account; publishing makes the chosen page content available through its link. A public page link is meant to be shared, not treated as a private access code.

The new page experience does not automatically send page content or audience responses to an AI provider. If you export a file or copy a brief into your own agent, that is a separate sharing decision governed by the service you choose.

Payments

Premium payments are processed by Stripe. Checkout shares your account email and an internal owner identifier with Stripe to connect the subscription to your account. Did It Land stores Stripe customer and subscription identifiers, billing status and renewal information. We do not receive or store your full card number. Audience submissions and contacts are not sent to Stripe.

Managed Payments purchases are sold through Link, Stripe’s merchant of record service. Stripe processes billing and payment details, handles applicable transaction taxes and sends payment receipts. Billing records may be retained for accounting and legal obligations after an app account is deleted.

Uploaded files

Owner uploads are stored in private Supabase storage. A file is available to visitors while at least one published, non-archived page in that owner’s account uses it. Files are not protected by email collection: published resources can be shared freely. Draft-only files require the owner’s signed-in account.

Download links use temporary storage URLs valid for 60 seconds. Taking all pages using a file offline stops new public links, but already-issued URLs may work until they expire. Copies already downloaded or printed cannot be recalled. Storage and hosting providers process the requests needed to deliver files.

Uploaded images are resized and re-encoded with embedded metadata removed. PDFs retain their original contents and metadata; they receive basic format checks, not virus scanning. Only upload material you have permission to share, and check it for personal information before publishing. Removing an attachment or archiving a page does not delete its library file. Owners can permanently delete files once no saved draft or published page uses them.

Keeping and removing information

Closing collection stops new responses while leaving the published resources available. Unpublishing or archiving a page keeps its content and existing submissions; these actions do not delete those records. The current app does not set a general automatic expiry for saved pages or submissions.

For a question about information you sent to an owner, use the contact details they chose to publish on their page. Anonymous submissions may be difficult to identify without the details of the response. Owners can use the signed-in app feedback control to raise an account or data-handling request.

Owners can delete their account from Settings. That permanently removes their pages, submissions, save counts and uploaded files.

Anyone can report a page with the link at the bottom of it. A report stores the page, the reason and any details or email address you choose to add. It does not store your IP address, and the page owner is not told who reported it.

Earlier pitch tests and app feedback

Anonymous responses collected by the earlier pitch-testing version remain separate from this page system and are not linked to newly collected email addresses. Feedback sent by a signed-in owner about the app itself is attributable to that owner so the team can follow up. It is a separate feedback system from audience forms.