Privacy Policy

Welcome to Ordana. We are committed to protecting your privacy and ensuring the security of your personal information. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our startup collaboration platform.

Ordana ("we," "us," or "our") operates the Ordana platform, including the websites joinordana.com, platform.joinordana.com, admin.joinordana.com and ordana.me (collectively, the "Service"). This policy applies to all users of our Service, including startups, founders, collaborators, and visitors. Ordana, a business registered in Sweden, Domarevägen 21, 237 31 Bjärred, Sweden, is the controller of the personal data described in this policy.

When Ordana sells a widget inside another startup's product (Section 2.8), Ordana also processes a limited amount of data about people who are not Ordana users: the end users of the product that embeds the widget, and the people who buy it.

By accessing or using our Service, you acknowledge that you have read, understood, and agree to be bound by this Privacy Policy. If you do not agree with our policies and practices, please do not use our Service.

2.1 Personal Information

We collect personal information that you voluntarily provide to us, including:

• Account Information: Full name, email address, password (encrypted), and country of residence
• Profile Information: Professional title, bio, avatar, and social links
• Business Information: Startup name, description, website, objectives, target clients, and resource needs
• Contact Information: Email addresses for communications and notifications

2.2 Financial Information

To facilitate revenue-sharing payments, we collect:

• Stripe Account Information: Connected Stripe account IDs, onboarding status, and verification status
• Payment Details: Invoice amounts, payment history, and transaction records
• Subscription Information: Plan tier, billing period, and Stripe customer ID
• Widget Buyers: When Ordana sells a widget, the buyer pays Ordana through Stripe. We keep the Stripe customer ID, the amounts paid, the VAT or sales tax charged, the billing country and address needed to calculate that tax, any VAT number the buyer gives, and the receipt. Card details are handled by Stripe only.

Note: We do not store complete credit card numbers, bank account details, or other sensitive financial credentials. All payment processing is handled securely by Stripe.

2.3 Technical Information

We automatically collect certain technical data when you use our Service:

• Device Information: Browser type, operating system, device type
• Usage Data: Pages visited, features used, timestamps, and session duration
• Feedback & Support Reports: If you submit feedback through an in-app prompt (for example when something appears not to be working), we collect your message together with the page URL and the interface element involved
• IP Address: For security, fraud prevention, and contract signing verification
• User Agent: Browser and device information for compatibility and security

2.4 Collaboration Data

When you participate in collaborations, we collect:

• Collaboration plans, deliverables, milestones, and timelines
• Messages and communications between collaboration partners
• Digital contract signatures and signature metadata (IP address, timestamp, legal name)
• Review decisions, disputes, and resolution records
• Risk assessments and mitigation plans

2.5 Uploaded Documents

You may upload documents such as pitch decks, business plans, or other files. We store these securely and only process them as necessary to provide our services (e.g., AI-powered matching).

2.6 Credibility Research Data

When an active or pending collaboration partner runs a "credibility check" on you (a feature available on the Assisted plan and above), we combine multiple categories of data into a stored report:

• Stripe-verified identity: your legal or business name, country, business type (individual / company), verification status, and the URL you registered with Stripe. Retrieved by our backend from Stripe's API at the moment the check runs.
• Your Ordana profile claims: your startup name, elevator description, AI tags, immediate resource needs, listed website, the content of your website automatically scraped at signup, and excerpts (up to three documents) from any files you uploaded to your startup profile.
• Direct fetches from your stated website: we perform automated GET requests against the website URL listed on your Ordana profile and a small number of common paths (e.g. "/about", "/services", "/case-studies") plus internal links our crawler discovers from your homepage. We extract readable text and contact email addresses from the returned HTML. Only pages that are publicly served are read.
• Public web search results: we run semantic web searches against a third-party search index using your business name, your stated services, and (in some cases) the legal name from your Stripe KYC, to surface external evidence such as LinkedIn profiles, press coverage, or complaints filed against the business.
• An AI-generated synthesis combining all of the above into a structured report (claim verification, identity legitimacy, red-flag scan), and a numerical trust-score delta applied to your account.

Sub-processors. The following third-party providers receive the personal data described above as part of running a credibility check:

• Stripe, Inc. — payment infrastructure provider. We query Stripe's Accounts API to retrieve your Stripe-verified identity fields. Stripe is subject to its own privacy policy and processes data in compliance with applicable EU adequacy frameworks.
• Exa Labs, Inc. — third-party semantic web-search provider. We send queries containing your business name and, where relevant, your stated services or signatory name, in order to retrieve public web evidence. Exa's privacy policy applies to its processing of these queries.
• Anthropic PBC (Claude API) and Google LLC (Gemini API). The fetched site content, your Ordana profile claims, your Stripe-verified identity fields, and the Exa search results are sent to our AI providers' large-language-model APIs (Anthropic's Claude, with Google's Gemini as backup; see 5.2) so that an AI model can synthesize the report. Each processes this data on Ordana's behalf as a sub-processor under its standard API terms.

Visibility. Each report is visible only to (i) the partner who initiated it, (ii) you (the subject of the report), (iii) any other active members of the same collaboration or scenario, and (iv) Ordana administrators. Reports are scoped to a specific collaboration or scenario and are not used for general matching, marketing, or training of any AI model outside that specific use.

Lawful basis. Our lawful basis for processing this data under GDPR Article 6 is (a) the contractual necessity of pre-contract due diligence between parties about to enter a revenue-sharing agreement, and (b) our legitimate interest, balanced against your interests, in providing a safe collaboration environment. By using Ordana — and in particular by joining a collaboration or scenario as a member — you acknowledge that other members may run a credibility check on you under these terms (see also our Terms of Service).

2.7 Contacts You Upload (Your Network)

You may optionally upload your professional network — for example a LinkedIn "Connections" export — so that our AI can suggest people you already know as potential collaborators. When you do, we store the structured contact details from the file (names, and where present, job title, company, LinkedIn URL, and email address). The uploaded file itself is parsed in your browser and is not retained.

• Used only for you. These contacts are private to your account and are used solely to surface collaboration suggestions back to you. They are never shown to other users, never sold, rented, or traded, and never used for general matching or advertising.
• We never contact them. Ordana does not email, message, or otherwise reach out to your uploaded contacts. Any outreach is something you choose to do yourself, directly.
• AI processing. To generate suggestions, relevant contact details may be sent to our AI providers (Anthropic's Claude API, with Google's Gemini API as backup; see 5.2), on Ordana's behalf and not used to train external models.
• Your control. You can view, replace, or permanently delete your uploaded contacts at any time, and they are deleted automatically if you delete your account.

Lawful basis. We process this data on the basis of your consent, which you give by choosing to upload it; you can withdraw that consent at any time by clearing your uploaded contacts. You are responsible for ensuring you are entitled to share these contacts with us for this purpose.

2.8 Widget Usage Data

When Ordana sells a widget inside another startup's product, the widget owner's server asks Ordana, before each use, whether that product's user may use the widget. To answer, we process:

• A pseudonymous reference for the user, chosen by the product. It is hashed with a secret key (HMAC) as soon as it arrives and is never stored in clear. A reference that looks like an email address is refused.
• Counts only: how many free uses and credits the user has used, monthly totals per product, and whether the user has an active subscription.

We never receive what the user does inside the widget or any content they create there. The owner and the product must not send us an email address or other directly identifying data as the reference. We use this data to enforce the widget's free allowance and paywall, to bill buyers and to tell the owner and the product whether the integration is working. Our legal basis is performance of the contract with the buyer, and our legitimate interest in metering the widget for its owner and host. When the user signed in with Ordana ID (Section 2.9), the reference is the identifier Ordana gave that widget for them.

A widget's owner may test two or three versions of its widget. Which version a user sees is worked out from the same pseudonymous reference each time and is not stored; we keep only counts per version (how many users saw, used and bought each one), shown to the widget's owner so it can keep the version that works best. The versions never differ in price or terms. We also use these counts, in aggregate, to improve our Service and the guidance we give widget owners (for example, which kinds of version tend to win). They identify no user. Our legal basis is our legitimate interest in improving the Service.

When a widget's owner runs a bounty (paying a new product a trial per person who uses its widget), we mark on the same pseudonymous reference when it was counted, so each person counts at most once per product, and we keep only the number of people counted per product per month. Neither the owner nor the product receives anything that identifies a user. Our legal basis is performance of the bounty for its owner and the product.

When a product applies for a bounty's paid trial, we show the widget's owner the product's name, its website and the note it chose to write, together with a short automated assessment of how well its users fit the widget. We make that assessment with our AI providers (Section 5.2), using only the product's public profile and website text and its note, never its private product details. The assessment is advice for the owner; it decides nothing and sets no amount. Our legal basis is our legitimate interest in helping owners choose where their bounty goes, and the product's own request when it applies.

2.9 Ordana ID (signing in to widgets)

A widget can let people sign in with “Continue with Ordana”: one Ordana account used across every widget, so a person signs in once and pays with a card saved once. When you use Ordana ID we process:

• Your account: your email address, your name, and how you signed in (email code or Google).
• Your consent per widget: which widgets you agreed to share your details with, when, the exact wording you agreed to, and when you withdrew it.
• Your wallet: one Stripe customer per account, so a card you save when buying one widget can pay for the next. Card details are handled by Stripe only.

What a widget's owner receives. Only after you press Continue on Ordana's consent screen, that widget's owner receives your name, your email address and an identifier that is different for every widget, so owners cannot recognise you across each other's widgets through Ordana. From then on the owner is responsible for what it does with your details under its own privacy policy. The product that shows the widget receives nothing from Ordana ID (what it may share with the widget itself, in your browser, is Section 2.10).

Widgets where you stay the host's customer. Some widgets are sold so that you stay the customer of the product you use them in, not of the widget's maker. For those, the widget's owner receives your name and that identifier, never your email address: it gets a stand-in address that receives no mail instead. The consent screen tells you which kind of widget it is before you press Continue, and once a widget has hidden your email it stays hidden for that widget.

What Ordana does not do. We do not tell any owner which other widgets you use, we do not build a profile of you from your widget use, and we never sell your details. We count usage per widget and per product (Section 2.8) to run billing and the directory.

Your own Ordana (ordana.me). When you sign in to ordana.me, it shows you the widgets you connected with Ordana ID, the products you use each one in, the free uses you have left there, your subscriptions, your saved card and your receipts. To show you your free uses, we match the pseudonymous usage records of Section 2.8 to you at the moment you open the page, using only your own sign-ins. That match is shown to you alone, is never stored, and is never shared with a widget's owner or the products you use it in. Our legal basis is performance of the contract with you.

You can see every connected widget and withdraw your consent at any time in your Ordana at ordana.me, under Widgets. After that the owner gets no new sign-in or details from Ordana; ask the owner directly to delete what it already received. Our legal basis is performance of the contract with you (your account, your purchases) and your consent (sharing your details with each widget's owner). We keep the consent record for as long as your account exists and for the limitation period afterwards, as evidence of what you agreed to.

2.10 Shared context and connected products

Shared context. A widget may say which details the product you use it in can fill in for you (for example your website or your industry), and which of its results that product may keep for you. These move between that product's page and the widget in your own browser; Ordana does not receive or store them. The widget shows what was filled in, tagged with the product it came from, and you can change it or choose “Don't use”. Results go back to the product only after you agree to keep it updated, and you can switch that off in the widget's settings. Where the widget's maker offers it, the product may also fetch those same results for you directly from the maker, under the same agreement and only until you switch it off; Ordana is not part of that exchange either. These details never include your email address, phone number, name, passwords, payment details, government identifiers, health or other sensitive data, your precise location or information about other people. The product and the widget's owner are each responsible for what they do with them under their own privacy policies. When you use Ordana's own widget, the details a product fills in (your website, your product's name, what it does, who its users are, its main features and the tools it integrates with) are used only for that check, like anything you type into it.

Connected products. If you use Ordana's widget inside another product, you may connect that product to your own Ordana numbers. Only you can do this, on Ordana's own screen. While connected, that product can read counts about your own widgets (views, uses, people who reached the paywall, sales and A/B test results per version), never money amounts, the names of the products that use your widget, or anything about your users, and it can suggest new versions of your widget, which change nothing unless you accept them. You can disconnect at any time in the widget's settings or in Ordana, and access stops straight away. Our legal basis is your consent, which you can withdraw by disconnecting; the product is responsible for what it keeps under its own privacy policy and must delete it when you disconnect.

2.11 Widgets inside a product that signs you in

Some products sign you in to the widgets they show with the account you already have there, instead of “Continue with Ordana”. Then that product's server tells Ordana that it is you, and we process:

• The product's id for you, which we keep only as a one-way hash, and a private id we create that belongs to that product and that widget only. We never link it to an Ordana account, and these sign-ins don't appear in your Ordana at ordana.me.
• Your name, or your name and email address, only if the product chooses to send them. We pass them on to the widget's owner and keep no copy.
• Usage counts as in Section 2.8, keyed by that private id. If the product pays for your use of the widget, we also count how many times a day you sign in to it and use it, and keep a one-way fingerprint of the name the product sends for you (never the name itself), for 30 days, so that we can tell the product and the widget's owner when one paid account seems to be used by several people. We never see what you do in the widget.

What the widget's owner receives. The private id and whatever the product chose to share. If the product shares only your name, the owner uses it only to provide the widget for that product, and the widget does not show the owner's name; the product names the owner as one of its providers in its own privacy notice. If the product also shares your email address, the widget shows the owner's name and the owner may contact you under its own privacy policy.

Paying. If the product charges you for the widget, you pay the product, on its own checkout and under its own terms. Ordana charges the product, not you, and never receives your payment details.

The product decides to sign you in this way and is responsible for doing so under its own privacy policy; in passing your sign-in on to the widget, Ordana acts on the product's behalf. We delete the hash and the private id once they have not been used for 400 days. Our legal basis is our legitimate interest, and the product's, in running a widget the product chose to offer you.

We use your personal information for the following purposes:

3.1 Service Provision

• Creating and managing your account
• Facilitating collaborations between startups
• Processing revenue-sharing payments through Stripe
• Generating and managing digital contracts
• Enabling communication between collaboration partners

3.2 AI-Powered Features

• Matching startups with potential collaboration partners
• Analyzing resource needs and availability
• Generating collaboration suggestions based on compatibility

3.3 Communications

• Sending email notifications about collaborations, deliverables, and payments
• Delivering in-app notifications and updates
• Sending email digests of unread messages (based on your preferences)
• Providing customer support and responding to inquiries, including, where needed, a read-only staff preview of your account (see Section 6)

3.4 Security and Legal Compliance

• Detecting and preventing fraud, abuse, and security threats
• Verifying user identity and preventing unauthorized access
• Complying with legal obligations and regulatory requirements
• Enforcing our Terms of Service and other policies

3.5 Platform Improvement

• Analyzing usage patterns to improve our Service
• Improving the guidance, defaults and AI models we use to help startups build, test and integrate widgets, from aggregated widget data that identifies no user
• Developing new features and functionalities
• Conducting research and analytics

We process your personal data based on the following legal grounds:

• Contract Performance: Processing necessary to fulfill our contract with you, including providing the Service and facilitating collaborations
• Legitimate Interests: Processing necessary for our legitimate business interests, such as fraud prevention, security, and service improvement
• Consent: Where you have given explicit consent, such as for marketing communications or optional features
• Legal Obligation: Processing necessary to comply with applicable laws and regulations

5.1 Collaboration Partners

When you enter into a collaboration, certain information is shared with your collaboration partner, including your startup name, contact information, and collaboration-related data. This sharing is necessary to facilitate the collaboration.

5.2 Service Providers

We work with trusted third-party service providers who assist in operating our Service:

• Supabase: Database hosting, authentication, and backend services
• Stripe: Payment processing, revenue sharing, and financial services — including, when Ordana sells a widget as merchant of record, checkout, subscriptions, receipts and tax calculation (Stripe Checkout, Billing and Tax)
• Resend: Transactional email delivery
• Anthropic: AI-powered matching, suggestions, and content generation via Claude models, our primary AI provider. Anthropic processes this data on our behalf under its commercial API terms and does not use it to train its models
• Google: AI-powered matching, suggestions, and content generation via Gemini models (our backup AI provider, and the provider of the text embeddings behind our search), OAuth authentication (if you choose to sign in with Google), and website usage analytics via Google Analytics
• Exa: AI-powered web and company search that powers collaborator discovery and partner credibility checks
• Reddit: Public-post search used to find potential collaborators for collaborations that are recruiting (see 5.8). We only send Reddit a search query built from a collaboration's own public launch-page text — no personal data about you or anyone else is sent to Reddit.
• LinkedIn: We send nothing to LinkedIn. Public LinkedIn posts are reached through Exa (above), and used only to find potential collaborators for collaborations that are recruiting (see 5.8).
• Microsoft Clarity: Behavioral analytics (session replays, heatmaps) that help us understand how the Service is used and improve it. Not used on our admin systems.

These providers are bound by contractual obligations to protect your data and use it only for the purposes we specify.

5.3 Legal Requirements

We may disclose your information if required by law, court order, or governmental authority, or when we believe disclosure is necessary to:

• Comply with legal obligations
• Protect our rights, privacy, safety, or property
• Protect the rights, privacy, safety, or property of you or others
• Prevent or investigate possible wrongdoing

5.4 Business Transfers

In the event of a merger, acquisition, or sale of assets, your personal data may be transferred to the acquiring entity. We will notify you of any such change and the choices available to you.

5.5 No Sale of Personal Data

We do not sell, rent, or trade your personal information to third parties for their marketing purposes.

5.6 Public Collaboration Pages

A scenario's launch page (served at joinordana.com/s/…), the public collaboration directory (joinordana.com/collaborations) and the collaboration listing on our home page(joinordana.com) are public web pages whose purpose is to recruit collaborators. Their content — the collaboration's title, description, what the founding team is building, the roles being sought, the number of participating startups, and the names and logos of the participating startups — is publicly accessible and may be indexed by search engines and read by AI crawlers so that relevant collaborators can find the opportunity. This content is written in the team's voice and is not intended to contain your private personal data. We publish the startup as the participant, never the individual — no personal account name, email or photo appears on these pages. Search engines and AI crawlers access this content the same way they access any public website; they are not our sub-processors. When a scenario is completed, dissolved, or removed, its page is taken out of our sitemap and marked so search engines de-index it (though third-party caches may retain a copy for a time outside our control).

A startup's logo shown on these pages is either one you uploaded or the icon published by your own website (its favicon), which we fetch and re-host so that visitors' browsers are not sent to a third party to load it. We do not publish a directory of startup profiles: a startup appears on a public page only through a collaboration it has joined. You can change or remove your logo at any time from your startup profile, and you can ask us to remove your startup from a public collaboration page by contacting help@ordana.me.

5.7 Collaboration Outreach ("Recruiting AI")

When you build a collaboration, Ordana can help you find partners beyond our own network. If a role can't be filled by an existing Ordana member, we run a web search and collect publicly available business contact information (such as a company's general info@ / contact@ email published on its own website) for companies that appear to fit the role. These prospects are attached to your collaboration for your review.

Ordana does not send these emails. Instead, we prepare a ready-to-send email for you — a subject line and body based on your collaboration's own description, with a link to its public launch page — and you send it yourself, from your own email account, to the companies you choose. You are the sender; Ordana does not transmit the message. Web/company search is performed via Exa (see 5.2).

Because you send from your own inbox, replies and any opt-out requests go directly to you, and you are responsible for honoring them. We process this business-contact data on the basis of legitimate interests (helping startups find relevant partners), balanced against the recipient's rights, and we honor objections and erasure requests about data we hold as described in Section 8. We do not sell or share these contacts for anyone else's marketing (see 5.5).

5.8 Finding Collaborators on Public Social Posts

For collaborations that are actively recruiting, we also search public posts on social platforms — currently Reddit and LinkedIn — to find people who might be a good partner. We store only what the author already published: their public username or profile handle, the post title, an excerpt of the post, a link to it, and (where the platform has them) the community it was posted in — together with our own note on why it looked like a fit. On LinkedIn a public profile identifies a named individual, and the post they published may mention their company or role.

We do not build a profile of anyone. We do not seek, derive or store professional characteristics — seniority, employer, location or career history — as separate information about a person, and we do not aggregate anyone's posting history. Our assessment is of the business described in the post, not of the person who wrote it.

This information is visible only to Ordana staff. It is not shown to you, to the collaboration's members, or to any other user, and it is never sold or shared for anyone else's marketing (see 5.5). Ordana does not send automated messages to these people. If we reach out, a person at Ordana writes the message and sends it themselves from their own account on that platform, in public or by direct message, subject to that platform's rules and each community's rules.

We only ever send the platform, or the search service we use to reach it (see 5.2), a search query built from the collaboration's own public page — never personal data about you or anyone else.

We process this on the basis of legitimate interests (connecting startups with relevant partners), balanced against the author's rights. If you are the author of such a post and want us to stop, tell us and we will add you to a permanent do-not-contact list and delete what we hold — see Section 8. Records we never acted on are automatically stripped of the username, title, excerpt and link after 90 days.

5.9 Founders Listed in Public Startup Directories

Some startup directories publish who founded each company — for example, Y Combinator's public company pages list each founder's name and LinkedIn profile. To invite founders to collaborate, Ordana staff may keep a list of founders taken from such pages. For each person we store only their name, their LinkedIn profile address, and the company, directory page and batch they are listed under, together with our own note of whether we have contacted them and how it went. We add nothing from other sources: no email address, phone number, job title, location or career history, and we do not visit or copy their LinkedIn profile.

This list is visible only to Ordana staff. It is not shown to you or to any other user, and it is never sold or shared for anyone else's marketing (see 5.5). Ordana does not send automated messages to these people. If we reach out, a person at Ordana writes the message and sends it themselves from their own LinkedIn account, and that first message says where we found your details and links to this section.

We process this on the basis of legitimate interests (inviting startup founders to business collaborations), balanced against your rights. If you are on such a list and want us to stop, reply to our message or email privacy@ordana.me: we will add your LinkedIn profile to a permanent do-not-contact list and erase everything else we hold about you — see Section 8. Entries we never contacted, or that we closed as not a fit, are automatically erased after 180 days.

5.10 Widget Directory

A startup can package its product as a widget so that other startups can integrate it, and can choose to list that widget on Ordana. Listing is always the startup's own choice, made by its own team; Ordana never lists a widget on a startup's behalf. When a widget is listed, Ordana publishes a public page for it (at joinordana.com/w/…) and lists it in Ordana's widget directory, which anyone can read. That page and the directory show only the widget's name, its one-line summary and list of capabilities, the offer its owner set, whether Ordana has verified it, and the startup's name, logo and website, plus, if its owner designed one, an example of what the widget looks like (its screens and sample content, which is fictional) and a link to its live preview (a page on the startup's own website that runs the widget on fictional sample content, which appears inside Ordana's page only when a visitor chooses to open it, at which point the visitor's browser connects to that website), and, once Ordana sells widgets, the commercial rules its owner confirmed (price, free use, the free-use cap per product, when the paywall appears and who the buyer becomes a customer of). This is information about the business, not about any person: no founder's or team member's name, email address or photo is shown.

Widget pages are public and may be indexed by search engines, and the page address may be shared freely, including by the startup itself. The technical details of a widget (how partners connect to it, support contacts and the like) are never public: they are shown only to startups that have added the widget to their product, and to Ordana staff. The one exception is the widget's API documentation, if its owner writes one: it is published on the widget's page so that engineers can read it before they integrate, unless the startup chooses to show it only to startups that added the widget. It describes how to connect to the product, not any person. The directory is also published in machine-readable form (joinordana.com/widgets.md and .json) with exactly the same fields, so that search engines and AI assistants can read it. A startup that lists its widget can put a “Listed on Ordana” badge on its own website; the badge shows the startup's name and links to its widget page, and turns generic if the widget is unlisted.

We count how often a listed widget is viewed and clicked, as daily totals per widget, so that its owner can see how it is doing. We do not record who viewed it. A startup can unlist its widget at any time: within minutes its page stops being served and it leaves the directory and our sitemap, and search engines drop it when they next visit. Any startup that wants a listing removed, or a detail on it corrected, can also email help@ordana.me.

We implement appropriate technical and organizational measures to protect your personal data against unauthorized access, alteration, disclosure, or destruction:

• Encryption: All data is encrypted in transit (TLS/SSL) and at rest
• Access Controls: Strict role-based access controls limit who can access your data
• Password Security: Passwords are hashed using industry-standard algorithms
• Contract Integrity: Digital contracts are secured with SHA-256 cryptographic hashing
• Row-Level Security: Database policies ensure users can only access their own data and what other users share with them. Authorised Ordana staff can access account data where needed to provide support, prevent abuse and operate the Service, under the role-based controls above
• Staff Account Preview: To help you, or to check that a feature works as intended, authorised Ordana staff can open a read-only view of the platform as you see it, for at most 30 minutes at a time. A preview cannot change anything in your account, does not show contacts you uploaded from LinkedIn or your AI chat history, and is never recorded by analytics tools. Every preview is logged with the staff member, the time and the reason. The log is kept for 12 months and is included if you ask for access to your data
• Regular Audits: We regularly review and update our security practices

While we strive to protect your personal data, no method of transmission over the Internet or electronic storage is 100% secure. We cannot guarantee absolute security but are committed to implementing best practices.

We retain your personal data for as long as necessary to:

• Provide our services and maintain your account
• Comply with legal, accounting, or reporting requirements
• Resolve disputes and enforce our agreements

Specific Retention Periods

• Account Data: Retained while your account is active and for 30 days after a deletion request.
• Collaborations & Scenarios: Retained in our active systems while the collaboration or scenario exists. When it is deleted, the operational data (messages, tasks, deliverables, and the revenue ledger) is removed from our active systems, and an archived PDF of the executed contract together with a full activity / deletion report is retained for 7 years for legal and tax purposes. The archive is emailed to the parties at deletion.
• Executed Contracts & Signatures: Preserved in the archived contract PDF — including each signer's identity, Stripe-verified name where available, and timestamps — for at least 7 years. The underlying database signature records are removed if the parent collaboration or scenario is deleted.
• Financial Records: Transaction records are retained for 7 years as required by financial regulations, held by our payment processor (Stripe) and within the archived deletion report.
• Usage Logs: Retained for 90 days for security and analytics.
• Support Tickets & Feedback: Retained while your account is active; deleted with your account.
• Credibility Check Reports: Stored for 1 year from generation, then anonymized — source URLs and snippets are removed; only the aggregate trust-score delta is retained for historical accuracy. Reports tied to a deleted collaboration or scenario are removed when the parent record is removed.
• Founders Listed in Public Startup Directories: Entries we never contacted, or closed as not a fit, are erased after 180 days. Entries we did contact are kept as the record of that correspondence. A request to stop erases the entry immediately and keeps only your LinkedIn profile address on our do-not-contact list, so that you are never added again (see Section 5.9).
• Widget Directory: A widget's public page and directory listing stay up only while its startup keeps it listed, and are removed when it is unlisted or retired. View and click counts are kept as daily totals per widget, with no information about who viewed it (see Section 5.10).
• Widget Sales: When Ordana sells a widget, each sale and the ledger of shares paid to the host and the owner are kept for 10 years, the record-keeping period for VAT sold under the EU One-Stop-Shop scheme.
• Widget End-User References: The hashed reference and its counts (Section 2.8) are deleted once the user has not used the widget for 400 days, unless they still hold unused credits or an active subscription. Monthly totals per product contain no reference to any user.
• Widget Checkouts: A checkout that is not completed is closed when it expires; its record is kept with the widget sales records.
• Contacts You Upload (Your Network): Retained until you remove them or delete your account, whichever comes first — we do not expire them on a fixed schedule, because they are only useful to you for as long as you keep them. Clearing or replacing your uploaded network deletes the previous contacts immediately, and deleting your account removes them all. The uploaded file itself is never stored (see Section 2.7).

Depending on your location, you may have the following rights regarding your personal data:

• Right to Access: Request a copy of the personal data we hold about you
• Right to Rectification: Request correction of inaccurate or incomplete data
• Right to Erasure: Request deletion of your personal data (subject to legal retention requirements)
• Right to Restriction: Request restriction of processing in certain circumstances
• Right to Portability: Request your data in a structured, machine-readable format
• Right to Object: Object to processing based on legitimate interests
• Right to Withdraw Consent: Withdraw consent at any time where processing is based on consent

Exercising Your Rights

To exercise any of these rights, please contact us at privacy@ordana.me. We will respond to your request within 30 days.

Credibility Check Reports: you may request deletion of any credibility check report you initiated, or any report that was generated about you, by emailing privacy@ordana.me. We will erase the report from our active store within 30 days. Trust-score deltas derived from a deleted report can also be reversed on request.

You can also manage many of your data preferences directly through your account settings, including notification preferences and account deletion.

We use cookies and similar tracking technologies to enhance your experience:

9.1 Essential Cookies

Required for the Service to function properly, including authentication tokens and session management. These cannot be disabled.

9.2 Functional Cookies

Remember your preferences and settings to provide a personalized experience.

9.3 Analytics Cookies

Help us understand how you use our Service so we can improve it. These are anonymized and aggregated where possible. We use Google Analytics for aggregate usage statistics and Microsoft Clarity for behavioral analytics such as session replays and heatmaps; account identifiers shared with Clarity are hashed in your browser before transmission.

We also run our own first-party product analytics inside the Service: anonymized, aggregated interaction signals (pages visited, time on page, navigation patterns, and derived interaction-difficulty indicators) used solely to find and fix points where the product is confusing or broken. These events are keyed to a random, temporary session identifier — not to your account — never include what you type or the content of your messages, are not shared with any third party, and are deleted within 90 days (see Section 7, Usage Logs).

Managing Cookies

You can control cookies through your browser settings. However, disabling essential cookies may affect the functionality of our Service.

Your personal data may be transferred to and processed in countries other than your country of residence. We use Supabase for hosting, which operates data centers in multiple regions.

When we transfer data internationally, we ensure appropriate safeguards are in place:

• Standard Contractual Clauses approved by the European Commission
• Data processing agreements with all service providers
• Compliance with applicable data protection laws

Our Service is not directed to individuals under the age of 18. We do not knowingly collect personal information from children. If you are a parent or guardian and believe your child has provided us with personal information, please contact us at privacy@ordana.me, and we will take steps to delete such information.

We may update this Privacy Policy from time to time to reflect changes in our practices, technology, legal requirements, or other factors. We will notify you of any material changes by:

• Posting the updated policy on our website with a new "Last Updated" date
• Sending you an email notification (for significant changes)
• Displaying a prominent notice on our Service

We encourage you to review this Privacy Policy periodically. Your continued use of the Service after any changes constitutes your acceptance of the updated policy.

If you have any questions, concerns, or requests regarding this Privacy Policy or our data practices, please contact us:

• Email: privacy@ordana.me
• General Inquiries: help@ordana.me

We are committed to resolving any complaints about our collection or use of your personal data. If you are not satisfied with our response, you may have the right to lodge a complaint with your local data protection authority.