Privacy Policy

When you sign up, we receive your email address, name, and profile photo from Clerk (our authentication provider) or the sign-in provider you choose (Google or Facebook). From Facebook or Google we receive only your name, email address, profile photo and an account ID — never your password, contacts, posts or messages. We store a unique user ID. We use this to identify your account, send transactional emails, and personalise your workspace.

Everything you write in BlnkSpace — documents, blocks, database rows and cells, product listings, variants, category pages, email templates, contact lists, campaign records — is stored in our database. We do not read your content, sell it, or use it to train AI models.

Images you upload (product photos, hero backgrounds, carousel images, avatars) are stored in AWS S3 under a path that includes your user ID, served via Amazon CloudFront CDN. We store each file's size, MIME type, context, and CDN URL for storage limit enforcement.

When you upgrade to a paid plan, Stripe processes your payment. We store your Stripe customer ID and subscription ID. We never see or store your card number, expiry, or CVV — those stay with Stripe. We store your plan tier, subscription status, and renewal date.

If you connect Stripe to accept payments, we store your Stripe Connect account ID. When a buyer completes checkout, Stripe sends us their shipping address, phone number, email, and order details as an order record. We do not store buyer card details.

Stripe verifies sellers' identity and business details directly. We do not receive or store your identity documents, bank details or Stripe login, and we do not hold any Stripe API key for your account. We store only the status Stripe reports for your account: whether it can take payments and payouts, whether onboarding is complete, and Stripe's reason code if payments are disabled. We use this to show you what to fix and to stop buyers starting a checkout that would fail.

If a buyer disputes a payment (a chargeback), Stripe sends us the dispute's amount, currency, reason, status and evidence deadline. We keep this record to notify you, to end paid-page access if the buyer wins, and to monitor dispute levels on the platform.

If you report a store or page using our report form, we store the page address, the category and details you give us, and your account ID, so we can investigate and follow up. We do not share your identity with the person you reported.

We track: published page count, storage used, and monthly AI interaction count per user — for plan enforcement and your usage dashboard. Not used for advertising or profiling.

Live cursor positions and real-time edits are synchronised through our Hocuspocus server on Railway. This data is ephemeral — cursor positions and keystrokes are not persistently logged. Finished document state is saved to our main database.

Infrastructure providers (Neon, Railway, AWS, Vercel) automatically collect server logs including IP addresses, request paths, timestamps, and HTTP status codes, used for debugging and security monitoring.

• Access — request a copy of the personal data we hold about you
• Correction — request correction of inaccurate data
• Deletion — request deletion of your account and personal data
• Portability — request an export of your data in a machine-readable format

• Restriction — request we stop processing your data in certain circumstances
• Objection — object to processing based on legitimate interest
• Withdraw consent — where processing is based on consent, withdraw at any time
• Lodge a complaint — with your local data protection authority

• Know — the categories of personal information collected and their purposes
• Delete — request deletion of your personal information
• Opt out of sale — we do not sell personal information, so this does not apply
• Non-discrimination — we will not discriminate for exercising your rights

• Access and correction — request access to or correction of your personal data
• Withdraw consent — withdraw consent to process your personal data
• Limit processing — request we limit how we process your data

Depending on the feature you use, this may include reading your inbox messages, sending mail on your behalf, and marking messages as read/unread or moved to trash. We request only the Gmail permissions needed for the features described above — never more.

We do not store your emails. Every time you open the Gmail tab or view a message, BlnkSpace fetches it directly from Google for that request and does not save a copy to our database. Your Google access token is held by Clerk, our authentication provider, and is never written to BlnkSpace's own database, files, or logs. We do not use your Gmail data for advertising, and we do not use it to train AI or machine-learning models of any kind.

If you use a reseller (white-label) account and a reseller opens a support session on your account (“viewing as you”, described in our reseller documentation), your connected Gmail is specifically excluded from that session — it is never accessible to anyone other than you.

You can disconnect Gmail at any time from your Google Account's third-party access settings, or by removing the connection from your BlnkSpace account settings. Once revoked, BlnkSpace immediately loses the ability to read or send on your behalf — there is nothing further to delete on our end, since we never stored a copy of your mail.

When you connect, Facebook asks you which Pages and Instagram accounts to share and which permissions to grant. For each one you select we store its name, ID and picture, the access token Facebook issues for it (encrypted with a key specific to your account), and the name and ID of the Facebook account that connected it. We also keep a log of connection changes so you can see what happened to your accounts. We never receive your Facebook password. When you open the Comments or Messages inbox, BlnkSpace fetches comments and Messenger / Instagram direct messages from Meta for that moment only; we do not store their content, only a note that a reply was sent and by whom. We use this data only to provide the Social feature to you; we do not sell it, use it for advertising, or use it to train AI models.

If you switch on an Auto-reply rule, BlnkSpace receives a notice from Meta each time someone comments on, or messages, the connected Page or Instagram account. The text is compared with your keywords in memory and then discarded; we do not store it. We store only a short log: the account, the kind of event, an ID used to avoid replying twice, the sender’s Meta-assigned ID (never their name), the length of the text and whether a reply was sent, kept for up to 30 days (the record of which rule replied to which ID is kept until you delete the rule or the account). The reply goes out under your Page or account name and includes a line saying it is automated unless you remove it. People who reply STOP are never answered. Only you can create or change these rules; a reseller can view them only if you have allowed that reseller access to the account.

If your account is managed by a reseller or agency, they cannot see or use your connected accounts unless you tick the box allowing that reseller to post to and view a specific account. You can untick it at any time, and the permission does not carry over to any other reseller. Only you can connect or disconnect accounts, and the activity log shows you anything done through a reseller.

You can disconnect any account from the Social page, or remove BlnkSpace in your Facebook Apps and Websites settings (for Threads: Threads settings → Account → Website permissions). Either way, we delete the stored tokens and details straight away. Deleting your BlnkSpace account deletes all of this immediately, and we also withdraw our access at Facebook. See Delete Your Data.

Published sites on BlnkSpace are listed in our public site directory at /directory. For each site it shows the page title, description, cover image, a link, the creator's name or username from their BlnkSpace profile, and verification badges (verified email, verified phone, verified domain, new account). It never shows your email address or phone number. A creator page lists every directory-listed site by the same creator, so visitors can see who published a site. To remove a site from the directory, unpublish it or contact privacy@blnkspace.app.

To keep the directory useful and safe, we automatically visit published sites, analyse their public content (for example length, duplication, repeated keywords and links), and rank or lower the visibility of sites that appear to be spam, mass-produced, duplicated or abusive. These decisions are made by software, affect only how a site appears in the directory, and are re-evaluated regularly. They have no legal or similarly significant effect on you. Site owners can see their standing and the reasons in their site settings, can ask for a re-check, and can ask for human review at appeals@blnkspace.app.

On published sites we count visits and how long a page stays open, to help rank the directory. We do not use cookies for this. A one-day anonymous hash, made from your IP address and the date using a secret key, is used to count unique visitors; it cannot be linked across days and is deleted within 2 days. We keep only anonymous daily totals. Automated visitors (bots) are ignored. We do this on the basis of legitimate interest; to object, contact privacy@blnkspace.app.

Signed-in users can report a listed site. We store the report with the reporter's account ID, and we do not tell the site owner who reported. While a report is open we also keep a one-way scrambled form of the reporter's network address (never the address itself) to stop one person filing many reports; it is cleared when the report is resolved or expires. We keep an automated record of how reliable each reporter's past reports have been, and may limit reporting for accounts that repeatedly file false reports. Copyright and trademark reports are handled separately by our team.