When you use Repontage, we collect:

• Account information: name, email address, and authentication data when you sign up (including Google OAuth data if you choose that method, or a bcrypt-hashed password if you sign up or set a password with email). We never store your password in plain text and cannot retrieve it; a forgotten password must be reset.
• Project data: URLs you submit, fetched site content, optional business brief answers (product, audience and goal), the AI-generated analysis and marketing outputs you choose to create, and saved channel experiment records. Competitor URLs and fetched content may also be processed to generate a comparison you request.
• Public instant analysis: the homepage accepts public URLs without an account. We store the submitted URL, a normalized host-and-path cache key, generated analysis and timestamps so other visitors requesting the same public URL can reuse the analysis.
• Usage data: pages visited, features used, credit consumption, and AI model interaction patterns.
• Technical / abuse-prevention data: we log your IP address transiently against rate-limited endpoints (public instant analysis, free audit tool, registration, feedback widget, live-page tracking beacon) to enforce fair-use request limits. Uncached public analyses are limited to three per hour per IP address; cached replays do not use that limit. These records are automatically deleted on a rolling basis (see Section 4) and are never used to identify or profile you.
• Payment information: processed entirely by Paddle.com Market Limited; we do not store or have access to your full credit card details.
• Connected social accounts: if you connect X, LinkedIn, or Reddit for auto-posting, we store OAuth access/refresh tokens, your platform username, and the content you choose to post through the Service. You can disconnect any platform at any time from your dashboard, which deletes the associated tokens.
• Feedback: if you submit feedback via the in-app widget, we store your rating (1-5), optional message, category, and the page you were on. If you are logged in, feedback is linked to your account so we can follow up; you may also submit feedback anonymously.
• AI chat assistant history: conversations with the in-dashboard AI assistant are saved per project so they persist across sessions and devices. You can clear a project's conversation at any time from the chat panel, and it is permanently deleted when you delete the project.
• Campaign records: scheduled social posts and newsletter drafts (content, selected time, delivery status and counts), email flow definitions and enrollment progress, owner-assigned contact stages and tags, and the per-contact click activity described in Section 5.
• Outreach records: prospect email addresses, sequence step numbers and send times that you record in the workspace. Some draft and send history also stays in your browser storage; deleting server data does not erase copies you exported or saved outside Repontage.

We use your information to:

• Provide, maintain, and improve the Service.
• Analyze submitted public URLs, then generate individual marketing outputs only when you choose those runs.
• Track credit usage and enforce plan limits.
• Send service-related communications (account updates, billing notices, plan changes).
• Analyze service usage patterns to improve reliability and user experience.

Submitting a URL or asking the assistant for advice does not itself post social content, send campaign emails or activate a flow. Those operations require your explicit action and configured providers.

Your data is stored on Turso (libsql) databases with encryption at rest and in transit. AI processing is handled by third-party AI providers (DeepSeek, OpenAI or Anthropic, depending on the model you select). Fetched raw site content or excerpts, your URL, prompts and optional business brief answers may be sent to the selected AI provider to perform the requested analysis or generation. Assistant requests may also include conversation history, available output excerpts and recorded campaign counts. Public instant analysis uses DeepSeek V4 Flash; reusing that cached result does not send a new analysis request to your selected workspace model or change the model that produced the original result. Provider retention and data handling depend on the applicable API terms and configuration; contact us for details rather than assuming a training opt-out or retention setting from your model selection. We implement reasonable security measures to protect your personal information. However, no method of electronic storage or transmission is 100% secure.

Public analysis cache: public URL analyses are cached for reuse for up to 30 days. A valid cache may be reused by other visitors requesting the same normalized URL and by a workspace with a server-validated matching URL, without an additional analysis credit charge. This is a cache reuse period, not a promise that every stored cache record is automatically deleted on day 30. Do not submit confidential pages or personal data to the public tool. Contact us to request removal of personal data in a cached analysis; deleting a workspace does not itself delete the separate public cache.

Project data is retained indefinitely on all plans. Generated marketing content stays available as long as your account remains active. You can delete any individual project yourself at any time from the dashboard (delete button, two-step confirmation). This permanently removes that project's URL and all AI-generated content, including its live landing page.

Account deletion: you can permanently delete your entire account yourself at any time from Account settingsby typing a confirmation phrase. This immediately and permanently erases your profile, every project and its AI-generated content, waitlist leads, share/referral statistics, chat assistant history, queued and scheduled social posts and newsletters, email flow definitions and per-contact enrollment progress, campaign click attribution records, the credit usage ledger, connected social accounts, and your subscription record. We cannot recover this data once deleted. If you have a live subscription (active, trialing, past due, or paused), you must cancel it from the billing card first; the deletion request is refused until then so billing is never abandoned half finished. If you would prefer we process the deletion on your behalf instead, contact us and we will do so within 30 days. Paddle retains its own billing records as required by law even after your account is deleted, per Paddle's privacy policy.

IP address logs: IP addresses recorded for rate-limiting and abuse prevention (Section 1) are retained for a maximum of 24 hours before automatic deletion, with occasional exceptions up to a few days depending on when a background cleanup cycle runs.

We do not sell your personal information. We may share data with:

• Service providers: Paddle (payments), Vercel (hosting), Turso (database), DeepSeek, OpenAI and Anthropic (AI APIs), Google (OAuth authentication).
• Connected social platforms: X, LinkedIn, and Reddit, solely to publish content you explicitly request us to post on your behalf via those platforms.
• Legal obligations: when required by law, court order, or to protect our legal rights.

Public share reports: once a project has completed, its report at repontage.com/s/{id}is accessible to anyone who knows the project link, without logging in. It can show the project URL and available AI-generated report outputs and collect waitlist signups. Reports are excluded from search engine indexing, but are not access-controlled. “Create share link” retrieves this existing URL; it does not enable a separate sharing permission. Do not treat a completed project report as confidential. Report sharing is separate from the hosted landing-page approval described below.

Hosted landing page:newly generated pages are private drafts. Only the owner can open the preview; it does not run analytics, collect leads or trigger campaign sends. Choose “Publish page” to approve a content and theme snapshot at the public, search-engine-indexable URL repontage.com/site/{id}. Later draft edits do not change that snapshot until you choose “Update published page.” “Unpublish page” removes the public snapshot and disables hosted-page lead collection and traffic counting without deleting the project or draft. Earlier automatic projects keep their existing public behavior unless you explicitly change their publication state. Public pages record aggregate view and call-to-action click counts and, when a traffic-source tag is present, a per-channel breakdown. These counters do not store an individual visitor identity; temporary IP rate-limit records are described in Sections 1 and 4. Repontage collection requests from downloaded copies use the same hosted-page approval check. Independently hosted copies and data already sent to external providers cannot be recalled by unpublishing in Repontage.

Waitlist email capture:the live landing page and the public share report page each include an optional “Notify me”/launch-notification email form. If a visitor submits their email, we store it (associated with your project, together with the channel that referred the signup when the browser provides one: a traffic-source tag on the link, or the referring page's domain) so you can see, group, and export the list of interested visitors from your dashboard Share panel, and so you (the project owner) can send them project updates and launch announcements directly through the Service (“newsletter broadcasts”), delivered via our email infrastructure or your own prefilled Gmail/Outlook draft when email delivery is not configured. Every broadcast we deliver on your behalf includes a one-click unsubscribe link pointing to our public /unsubscribepage; opting out is permanent and cannot be reversed by resubmitting the waitlist form, and future broadcasts automatically skip opted-out addresses. We deduplicate repeat submissions from the same address, we do not use these emails for our own marketing purposes, and we do share these addresses only with you and the delivery providers or webhook destinations described below. You can delete an individual visitor's email, flow enrollments and linked click records from the Contacts panel (two-step confirmation), or delete this data in bulk at any time by deleting the project. If you are the visitor and want your captured email deleted rather than just excluded from future sends, contact us at support@repontage.com Clicking “Unsubscribe” stops future broadcasts but, by itself, does not delete the stored address.

Automated email flows:a project owner may turn on a pre-built background sequence (a welcome series sent after signup, a re-engagement nudge, or a launch-day countdown) that then emails your waitlist address automatically on a schedule, without the owner clicking send each time. Every flow email carries the same one-click unsubscribe link. Future sends skip an address after its opt-out is saved; a message already accepted by an email provider cannot be recalled. A re-engagement step additionally skips you automatically once you have clicked a recent flow or newsletter link, using the per-contact signal described below. We store each flow's definition and, per contact, which step you have reached and when the next one is due; this data is deleted when the project owner deletes the project. Flow sends use the same infrastructure and fallback behavior (SMTP when configured, otherwise the sequence simply waits) as newsletter broadcasts.

Campaign click attribution:links inside flow and newsletter emails route through a tracking redirect so we can record that a click happened and which campaign it came from, then forward you to the live page. For flow and newsletter emails, the link also carries a cryptographic key (an HMAC keyed to your project and email address) so a re-engagement step can check “did this contact click anything recently” without storing your email address in the click log itself; the key, campaign channel, optional scheduled-post reference, and timestamp are recorded. This is pseudonymous personal data, not anonymous data: the project owner can view a contact's click history and flow progress and assign stages or tags in Contacts. These signals support email timing and suggestions, not decisions with legal or similarly significant effects. Linked records are erased with the contact, project or account. Contact us to request access, objection, restriction or erasure of this activity; unsubscribe also stops future marketing sends.

Email delivery and owner-configured webhooks: recipient addresses, message content and delivery metadata are sent to the SMTP provider when email delivery is configured. If an owner saves a lead-notification webhook, new lead email addresses, signup sources and timestamps, and project identifiers may be sent to that destination (for example Slack, Discord or Zapier). Those recipients have their own privacy practices; the owner is responsible for selecting a lawful destination. The owner controls the purpose of their lead campaigns; Repontage processes that campaign data to provide the service. Copies already sent to an external provider are not erased by deleting records in Repontage.

Optional visitor analytics (Google Analytics 4 / Meta Pixel):you may choose to enter your own GA4 measurement ID or Meta Pixel ID for a project. If you do, that tracking snippet is injected into your project's live landing page and will set third-party cookies and share visitor data (such as page views and clicks) directly with Google or Meta according to their own privacy policies. This feature is off unless you actively enter an ID. On pages rendered by Repontage, the configured snippets remain inactive until the visitor chooses “Allow analytics.” The visitor can decline or reopen “Analytics settings”; withdrawing a prior opt-in reloads the page to stop running tags, but cannot recall data already sent. A change to the configured snippets requires a new choice. You remain responsible for your providers' configuration, lawful processing and any additional notices required for your project. Repontage does not receive or store the analytics data these tags collect; it flows directly from the visitor's browser to Google/Meta.

Referral attribution:when a visitor signs up after opening one of your share links, we record which project link referred them so you can see how many signups your share link drove. Only the project id is stored on the new account. No other visitor data is collected. This attribution respects the visitor's cookie preferences where a cookie is involved.

Share reach analytics:when someone views your public report page or clicks its signup button, we record an aggregated view or click count for the project. If the visit arrived with a source tag (added by the sharing buttons we provide) or a referring site header, we store that source label (for example “x” or a referring domain) in an aggregated per-channel counter so you can see which platform drove the traffic. No personal data about the visitor is stored; these are simple counts per source.

We use the following types of cookies:

• Essential cookies: authentication, session management and security, including a signed Google signup acceptance receipt that expires after 15 minutes. This records Terms acceptance and Privacy Policy acknowledgment, not permission for optional marketing or analytics.
• Optional measurement: Vercel Analytics and Speed Insights are enabled only after “Accept all” or the optional settings toggle. These services measure usage and performance without tracking cookies.
• Optional referral cookies: accepting optional measurement also permits a share-link referral cookie used during Google signup; essential-only and decline choices do not permit it.
• Browser storage: cookie preferences and workspace settings are saved locally. Generated pages save a separate, project-specific visitor analytics choice. Browser storage may also hold offline chat or draft history.

Repontage's service pages do not use advertising cookies; a project's optional Google/Meta tags are covered separately above. You can manage service cookie preferences at any time by clicking “Cookie Settings” in the footer, or by adjusting your browser settings. Disabling essential cookies may prevent the Service from functioning properly.

Depending on your jurisdiction, you may have the right to access, correct, delete, or export your personal data, and to object to or restrict certain processing. You can exercise access, correction (display name), deletion, and export (account and project records as a JSON download) yourself at any time from Account settings, with no waiting period. For anything you cannot do yourself, contact us at support@repontage.com. We will respond without undue delay, normally within one month, or sooner where applicable law requires. The self-service export bounds some high-volume lists; contact us for records not included in that download.

Legal basis for processing (GDPR, Art. 6): we process account and project data to perform our contract with you (providing the Service), based on your consent (where required, e.g. marketing communications), and on our legitimate interest in operating, securing, and improving the Service.

EU/EEA/UK users: if you believe we have not adequately addressed your concerns, you have the right to lodge a complaint with your local data protection supervisory authority.

Korean users (개인정보보호법): you may request access, correction, deletion, or suspension of processing of your personal information by contacting us, and you may also file a complaint with the Personal Information Protection Commission (privacy.go.kr) or the Personal Information Dispute Mediation Committee.

Personal information manager (개인정보 보호책임자): pursuant to Article 31 of the Korean Personal Information Protection Act, our designated personal information manager can be reached at support@repontage.com for all inquiries regarding the processing of your personal information and the exercise of your rights.

Vercel, Turso, DeepSeek, OpenAI, Anthropic, Google, Paddle and configured delivery providers may process data outside your country, including in the United States, China and Europe. The data categories and purposes are described above. Contact us for the applicable recipient, location, retention and transfer information or to object to a transfer. You can avoid optional social connections, analytics and webhooks; necessary hosting and AI processing may be unavailable if you refuse those transfers. Terms acceptance is not separate consent to international transfers, and does not waive your rights.

The Service integrates with third-party services including Google OAuth, Paddle, and third-party AI providers (DeepSeek, OpenAI, Anthropic). Each has its own privacy policy. We encourage you to review their policies. We are not responsible for their practices.

The Service is not intended for users under 16. We do not knowingly collect data from children. If we learn we have collected such data, we will delete it promptly.

We may update this Privacy Policy from time to time. Material changes will be communicated via email at least 14 days before taking effect.

For privacy-related inquiries or to exercise your data rights, contact us at support@repontage.com.