Private by design does not mean invisible to everyone. This policy explains what candidates, referrers, the operator and service providers can actually access.
Who is responsible
Arsen Arpachiev operates Referreo as an individual founder and is the controller of personal data processed for the platform. Referreo initially focuses on Vienna, Austria, and serves candidates and employees seeking professional introductions. The operator information below identifies the details still needed before commercial launch.
This policy covers referreo.com, account registration, employee verification, introduction requests, chat, balance activity, invitation rewards and optional CV feedback. The EU General Data Protection Regulation (GDPR) and applicable Austrian data-protection law apply. External employers, LinkedIn and other websites operate under their own privacy notices.
Information we process
Account information includes your account email, name, LinkedIn URL if supplied, sign-in method, account identifiers and security or consent records. Supabase Auth manages authentication; Referreo does not receive your Google password. Email-and-password credentials are handled through the authentication service, not stored as readable passwords in application profiles.
Employee information includes company, country, languages, availability, work email, verification links and confirmation history, domain-review records and verification decisions. A work email is used to verify inbox ownership and the relationship between an email domain and a company; it is not a public contact address.
Request information includes your submitted name, PDF CV, job links, message, optional LinkedIn URL, chat messages, request status, timestamps, CV-access records, decisions, decline reasons and any feedback you submit. Optional AI feedback also involves the CV, job description, target country and generated review.
Transaction information includes balance entries, payment and refund identifiers, request pricing snapshots, payment status, invitation attribution and reward records. Operational data can include IP addresses, browser and device information, access logs, delivery records, abuse reports and administrative access logs as recorded by the platform or its infrastructure providers.
Purposes and legal bases
We process information necessary to create accounts, verify employee profiles, deliver requests and chat, maintain balances and provide CV feedback you request to perform our contract with you, or take steps at your request before that contract (Article 6(1)(b) GDPR). Some fields are optional; without essential account, verification or request information, the corresponding feature cannot operate.
Security, fraud prevention, duplicate-reward checks, operational troubleshooting and handling complaints serve legitimate interests in running a reliable service (Article 6(1)(f)). Where applicable, financial recordkeeping and responses to lawful authorities are based on legal obligations (Article 6(1)(c)). Optional marketing emails rely on consent (Article 6(1)(a)).
Who can see what
While browsing, candidates see employee cards with company, verification status, country, languages and any published careers link, rather than an employee's name or work email. After a funded request is sent, the candidate can see the employee's first name while the request is pending; the full name and available LinkedIn details are released on acceptance. First-name visibility can remain after a decline or an expiry where the CV was viewed; it is not provided for an unviewed expiry.
Candidates are identifiable to the receiving employee from submission: that employee can see the submitted name, CV, role links, message and LinkedIn URL if provided. Referrer CV access is restricted to eligible open or accepted requests; opening access during a pending request records the first view because it affects the automatic expiry credit. A candidate opening their own CV, or an authorised administrative inspection, does not count as a referrer view.
The platform does not disclose account or work email addresses between candidates and employees. Chat is limited to the request participants and does not expose names through message labels. This is not a promise to redact information you put into a CV, message or LinkedIn profile yourself. Avoid including contact details or sensitive information you do not want the recipient to see.
The owner can access personal information where needed for administration, verification, safety and support; sensitive administrative request access is logged. CV access is therefore not limited exclusively to the employee: authorised administration, storage infrastructure and a requested AI review can also involve the file. Downloaded files or information voluntarily shared outside the platform cannot be recalled by changing a request status.
Work-email verification and invitations
Recognised company domains use an email-link confirmation. Unfamiliar domains require inbox confirmation and a human review; AI does not decide whether your work email is genuine. Administrators can inspect submitted work emails and domain evidence, approve or reject reviews, and revoke verification. Changing your company or revoking verification invalidates relevant existing links.
Invitation attribution associates an eligible new employee with an inviter. The inviter sees reward progress and eligibility outcomes, not the employee's work email. Corporate email identifiers and invitation history are used to prevent self-invites, repeated awards and other misuse; limited reward and anti-abuse records can remain after an account is deleted.
Optional AI CV feedback
Opening the CV-review feature for an eligible unsuccessful request can start a review. The server retrieves your submitted CV and role description, using a supported public job page or text you paste, and sends that material and the target country through the Lovable AI Gateway to an OpenAI model. The resulting feedback is stored for your account and is not published to employers or other candidates.
Feedback is advisory and may contain mistakes. It does not decide whether you are hired, whether an employee accepts a request or whether you qualify for a payment return. Employees make their own decisions. Do not include health, religious, political or other sensitive information in material submitted for review unless necessary and you understand its disclosure. This policy does not promise that provider data is confined to the EU or excluded from provider retention or training; those production settings and contractual safeguards need confirmation before launch.
Service providers and international processing
The implementation uses Supabase for authentication, database and CV storage; Stripe for card-payment and refund processing; Resend for platform email delivery; and the Lovable AI Gateway and OpenAI for requested AI feedback. The deployment is configured for Cloudflare hosting. Google receives information when you choose Google sign-in. Each provider receives information relevant to its function; payment providers may also process information under their own legal obligations.
Embedded Stripe payment components handle payment credentials; Referreo does not store full card numbers or card security codes. Platform emails are addressed to the recipient's own email, not to the other participant. The website also requests the Inter, Plus Jakarta Sans and JetBrains Mono fonts from Google Fonts, which can disclose network information such as your IP address to Google.
A Vienna launch does not by itself mean EU-only processing. Hosting regions, processor agreements, subprocessor lists and any transfers outside the EEA must be verified for the production setup. Where a transfer requires a safeguard, the operator must establish the applicable adequacy decision, contractual clauses or other lawful mechanism; this draft is not evidence that those arrangements have already been completed.
Cookies and browser storage
The app uses browser storage for sign-in sessions, your selected theme and saved introduction drafts. Drafts may contain text, links and CV file references; clear them when using a shared device. Blocking or clearing storage can sign you out, remove a draft or prevent a feature from remembering your choice.
A valid employee-invitation code may be stored in local storage and the first-party referreo_ref cookie for up to 30 days to attribute an invitation. A pending Google-sign-up marketing choice can be remembered for up to one hour while you complete sign-in. These mechanisms are distinct from marketing-email consent. Optional referral attribution must be assessed separately under the applicable Austrian rules on terminal-device storage; this notice is not a cookie-consent mechanism.
Payment components, hosting and authentication providers may use their own storage and security mechanisms. In the Lovable editor preview, error-reporting hooks can receive technical error information. This policy does not claim that an unverified deployment has no analytics or third-party tracking; the live-site storage inventory must be checked before commercial launch.
Service and marketing messages
Verification, account-security, request, chat, payment and balance messages support the service and do not depend on marketing consent. Product news and promotional platform updates require the separate optional opt-in. We record the consent source and timing, and withdrawal of consent.
You can change marketing preferences on Account or use the unsubscribe link in a marketing email without signing in. Withdrawal does not affect earlier lawful processing or stop essential service messages. We do not treat account registration, a paid request or agreement to these Terms as marketing consent.
Retention and account deletion
Attached CVs are scheduled for automatic deletion 60 days after acceptance or decline, or 60 days after the expiry deadline for expired requests. A support return does not restart that period. When the same uploaded file is attached to multiple requests, it is retained until all referencing requests reach their deletion date; an open request keeps its copy available. There is no separate self-service CV deletion control. Account deletion and statutory data rights remain separate. Cleanup runs when the configured scheduler invokes processing or during signed-in activity; interruptions may delay physical deletion.
Account, profile and related request information is generally retained while your account and the corresponding service records remain active. You can edit your details and request account deletion from Account. The deletion flow removes the account, associated profile and request content, chat, reviews and uploaded CVs through application cleanup and database relationships.
Deletion does not necessarily remove every record. Wallet and payment history, transaction identifiers, limited reward and anti-abuse records, and records needed for legal obligations or claims can remain. Retained identifiers may still be linkable to a person and should not be assumed anonymous. Retention is assessed by the record's purpose, applicable financial obligations and unresolved claims; statutory accounting periods do not justify keeping every CV or message for the same period.
Payment providers retain their own records under their policies and obligations. Copies already downloaded by a recipient, and any provider backups that exist, are not erased immediately by deleting an account. The operator must confirm production retention, backup and deletion schedules before launch; we do not promise a fixed purge deadline that the current implementation does not enforce.
Your choices and GDPR rights
Subject to the applicable conditions, you can request access, correction, erasure, restriction or portability of your personal data, and object to legitimate-interest processing. You may withdraw consent at any time. We may need proportionate identity verification and normally respond within one month; legally permitted extensions will be explained.
Use the operator contact details below once completed. You may complain to the Austrian Datenschutzbehörde at dsb.gv.at or another competent supervisory authority, without first contacting us. This does not limit your other legal remedies. Referreo is intended for adults; users must be at least 18 under the Terms.
Changes to this policy
The revision date identifies this version. Material changes to data use will be explained through an appropriate notice, and fresh consent will be sought where required. A revised policy does not itself authorise a new incompatible use of your information.
Operator information
Arsen Arpachiev — individual founder and operator of Referreo. No company has been incorporated.
Postal / service address: pending confirmation.
Support and privacy email: pending confirmation.