Privacy Policy

This Privacy Policy explains how Omer Frank, trading as Juicy Patterns and registered in Israel ("we", "us", or "our"), collects, uses, and protects your information when you use Discover Agents (the "Service"), or open a board someone shared with you. We are the data controller responsible for your personal information, except where section 1 says otherwise for a board someone shared with you, and you can reach us at omer@discoveragents.io. By using the Service, you agree to this policy.

1. Information we collect

Account information. When you create an account, we collect your email address and a securely stored (hashed) password, handled through our authentication provider.

Content you provide. The starting point you enter (a website address, an angle, or an idea), the problem spaces, opportunities, and items you select, and the blueprints you generate and save.

Experiment results you log. When you record how a validation experiment went, for example pass, fail, or inconclusive, and what you learned, we store it against your discovery so we can guide your next step and, if you opted in, remind you.

Using the tool without an account. You can run the tool anonymously. In that case your discoveries and agents are not saved to any account. We measure anonymous visits the same way as any other visit (see "Usage information" below and section 6), without knowing who you are. Your inputs are still processed by the AI and search providers below to return results to you. We may use anonymized, aggregated insights as described in "How we use your information" below.

Contact details you give us. If you ask us to email you something or to join a list, for example, to receive your blueprint, request early access to upcoming features, send feedback, or enquire about working with us, we collect the email address (and any message) you choose to provide.

Your idea, saved with your account. When you sign up from our home page you can type an idea (up to 500 characters). Your email address and password are needed to create the account; the idea is optional. We save the idea with your account so that your first board can start from it, even if you open the confirmation link on a different phone or browser. We use it for that and nothing else: the AI and search providers listed below read it to build your first board. We don't train our own models on it or sell it. Our AI and search providers handle it under their own terms. Some of them may keep it, and our search provider may use the short search topics it receives to improve its own service. Please do not put other people's private details in it. If you choose to share a board, that is your choice. Numbers we look at, such as how many people started a board, never include the text of your idea.

If you never confirm your email, your account, with the email and the idea saved on it, is deleted after 30 days.

Once your first board starts, the saved copy of the idea is cleared, at the latest 8 days later, and the idea lives in your board like anything else you enter there, until you delete it or your account.

The early-access list. If you join the early-access list on our home page, we keep your email address and, if you type one, your idea, together with the time you agreed to hear from us and the campaign link that brought you, if any. We use them only to prepare your board, to decide the order in which we send invitations, and to email you about your early access. We never publish or sell your idea, and only the service providers below that store and deliver it can see it. By joining you agree that we email you about early access and nothing else, such as when a place opens or where you stand in line. You can unsubscribe from any of these emails. We keep it for up to 12 months, or until you ask us at omer@discoveragents.io to delete it, and we email you only about early access. A person who already has an account is not on this list; their idea is covered in the paragraph above.

Requesting a seat in the closed alpha. While the alpha is closed you can ask for a seat from our home page.

What we keep from a seat request. We keep your name, your email address and what you told us you do. We also keep when you asked and how often, which button you used, the notice wording you saw, and our decision and its date. To stop abuse, we count requests per connection and per inbox. The counters use a keyed hash that does not hold your IP address or email in readable form. They reset within an hour and a day, and we never store them with your request.

Why we keep it, and the legal basis. We use these details to decide on your request, email you about it and recognise you when you sign in to take your seat. If you get a seat, we also keep your answer to "What will you use Discover Agents for, and how?" on your account, to learn who uses Discover Agents and why, and to choose whom to invite to our feedback group. Only our team and the providers below can see it, and we never publish it. In Israel, under the Privacy Protection Law as amended by Amendment 13, we rely on the informed consent you give by sending the request after reading this notice. You can withdraw it by asking us to delete the request. Where the GDPR applies, we rely on steps you asked us to take before entering an agreement (Article 6(1)(b)). For the counters, we rely on our legitimate interest in preventing abuse (Article 6(1)(f)). Keeping your answer on your account for those two reasons relies on our legitimate interest in understanding our users (Article 6(1)(f)). You can object at any time, and we delete it. The law does not require you to give these details, but we cannot consider a request without them.

What we never do with a seat request. We do not put you on a marketing list or send you a newsletter from it, and we do not sell or rent it. Please keep other people's details out of "what you do".

Who processes a seat request. Supabase stores it (Mumbai, India). Vercel hosts the site that receives it. Resend sends the emails. Your details therefore leave Israel, and the EU if you are there (see section 10).

How long we keep a seat request.

• Waiting or "not now": deleted 6 months after you last asked. About 5 months after you asked we email you once to say it is still waiting. If you reply "keep", we hold it for another 6 months. If you reply "delete", we remove it sooner.
• Approved but not yet in: deleted 90 days after approval. This covers an approval you never used, and a sign-in that did not let you in.
• Once you are in: deleted within 30 days of your first sign-in with the seat. Your account keeps the fact that you joined by seat request, in which group, when we approved it, and your answer to what you will use it for. We keep that answer while your account exists, and delete it with your account, or sooner if you ask.
• If you already have an approved account: deleted within 30 days.

Your rights over a seat request. To see, correct or delete it, write to us from the address you used. We act only on requests from that address, so nobody else can read or change yours. If you have lost access to it, tell us and we will agree another way to check it is you. We answer within 30 days. If someone used your address without asking you, write to us and we delete it. Contact: omer@discoveragents.io

If someone shared a board with you. A person with a Studio plan can send you a link to read one of their boards. You do not need an account, and you do not need to agree to anything, to read it.

What we record when you open it. If you open the page from a country in the European Economic Area, the United Kingdom or Switzerland (or a territory under the same data protection law, such as Gibraltar, Jersey, Guernsey or the Isle of Man), or from a place we cannot identify, we record nothing about the opening: no time, no device, no country and no visitor code. For every other visitor, each time the page opens, we record the time, the type of device (phone, tablet or computer) and the country your connection comes from. We also make a visitor code from your connection's IP address, your browser's details and the link itself, using a secret key that we replace every month and then destroy. The code only tells us whether the same device opened that one link more than once. It cannot connect you to another link or to another month. We use your IP address and browser details for that moment only and do not store them. We never record your city, the page you came from or anything you type. The page sets no cookies and runs no analytics and no screen recording. Wherever you are, we keep a short count of tries, under a code that does not hold your IP address, to stop people guessing links. If a link does not open, for example because it has ended or was mistyped, that count is all we keep.

Who sees it. The person who shared the link sees, for each opening we recorded, the time, the type of device and the country, and how many different devices opened it. Openings from the places named above are not recorded, so they see nothing about those, and their screen says so. They do not see the visitor code, your IP address or anything else about you. Our support team sees only how many links an account has, never the links or who opened them.

Why we record it, and the legal basis. For visitors outside the places named above, we record each opening to keep the link secure, by stopping guessing and abuse, and so the person who shared it can tell it was read. For everyone, the short count of tries is for security only. Where the GDPR applies, we rely on our legitimate interest in both (Article 6(1)(f)), and you can object (see "Your rights" below). In Israel, this notice is given to you under the Privacy Protection Law, as amended by Amendment 13. No law requires you to give us this information: it is recorded only because you open the page.

Who is responsible for what. We decide what is recorded about an opening and how long it is kept, so for that record Omer Frank, trading as Juicy Patterns, is the controller. The board belongs to the person who shared it. They decide what it says and who gets the link, and they are responsible for it, including anything it says about you or about the people they spoke to. We store it and show it to you on their behalf. Before the page is shown, we hide the names, companies, email addresses and phone numbers we can recognise, but the person who shared it chooses what to share.

Who processes it. Supabase stores the record of each opening (Mumbai, India). Vercel delivers the page, and handles your connection, including your IP address, to do that; it keeps its own technical logs for about a day. Your information therefore leaves Israel, and the EU if you are there (see section 10). Nothing from the page goes to our analytics provider or to any advertiser.

How long we keep it. The record of each opening is deleted 90 days after the link stops working: when the person who shared it ends it, when it passes its end date, when their plan ends or when the board is archived. A link works for at most 90 days, so the record is gone at the latest about 6 months after the link was made. The count of tries resets after a minute and is deleted within a day. The key behind the visitor codes is destroyed at the end of each month. Backups are covered in section 7.

Your rights. You can ask to see the record of your openings, ask us to delete it, or object to it, by writing to omer@discoveragents.io. We do not know who you are, so we can find the record only through the page. Every shared page shows a page reference at the bottom: send us that reference, not the link, and we delete every opening recorded for that link. If you send the link itself instead, we end it at once, so the copy in our inbox stops working, and delete every opening recorded for it. If you opened the page from the European Economic Area, the United Kingdom, Switzerland or a place we cannot identify, nothing was recorded, so there is nothing to delete. If the board says something about you that you want corrected or removed, ask the person who shared it, because they control what it says. You can also use "Report this page" at the bottom of the page: we read every report, and we may end the link. You can also complain to the Privacy Protection Authority in Israel, or to your local data-protection authority (see section 9).

Studio: client links, your logo and search. If you have the Studio plan:

• Client links. When you share a board with a client, we keep a fingerprint of the link (never the link itself), your private label, the parts of the board you chose, the words you asked us to hide, the link's dates and counts, and the record of openings described above. Your private label is never shown to your client.
• Your name and logo. If you upload a logo, we redraw it as a new image and remove the file's hidden details, such as location data, before we keep it. Your name and logo are shown only on your client pages and in your account.
• Search across your boards. When search is part of your plan, we keep a search index of your boards' text and conversations so that you can search them. A search shows you only your own content.

How long we keep each of these is set out in section 7.

Connecting your own coding agent. You can connect a coding agent you already use to your account. You make a key for it in Settings, and you can revoke it there at any time. Your agent then asks us for your boards with that key. Connecting an agent is optional, and nothing else in the Service depends on it.

What your agent can read. Only your own boards, never boards that belong to someone else, and never the boards you put away. For each board: its name and what it is about, your spaces, problems and opportunities, the one line of your Blueprint, and your tests with what you recorded on them, such as the result and what you learned. That can include what the people you spoke to told you, as you recorded it, and quotes from public web pages, each with a link to where it came from. Your agent sees no more of a board than your plan shows you in the app. Each piece is marked as typed by you, written by our research, or taken from the web. On a paid plan, your agent can also ask for your Blueprint as a build brief: a plan to build from, in a fixed form, made from your Blueprint, with no quotes, no source links and nothing taken from the web. Your agent never receives your chats with Iris, the simulated people and their answers, who's circling, what's been tried, your build prompts or the edit history of your boards.

Where it goes. We send your boards to your agent only when it asks with your key. That request is your instruction to us. What your agent reads then goes to your agent and to the company that runs it, or to the AI service you set it to use. That company is not one of our service providers. It handles what it receives under your own agreement with it, and we do not control what it keeps or how it uses it. It may be in another country, such as the United States. If you revoke a key, your agent can no longer read your boards, but what it already read stays with it.

What your agent can send back. Your agent can send readings only to a test where nobody takes part: a data analysis, a reliability check, a cost per run check or a scenario stress test, and only before you have decided that test. For a data analysis, your agent may work over your own data, such as your customers' records, on your computer or in your own tools. We do not receive that data. We receive only what your agent chooses to send us: the numbers, a short label of up to 300 characters and a note of up to 500 characters for each row, and a summary of up to 2,000 characters for each batch. Anything longer is cut. Please keep names and other personal details out of them. A batch waits on the test, not counted, until you confirm it or throw it out. Readings you confirm become part of your board.

What we keep.

• For each connection: the name you gave it; the first part of its key, which is not secret and lets us find the connection; a one-way fingerprint of the secret part, which cannot be turned back into the key; when it was created, last used and revoked; and the kind of coding agent it last said it is, as one of a few names we recognise, or "your coding agent" when we do not recognise it. Your agent reports that about itself, so we only show it to you and never rely on it. A revoked connection stays in your list, so you can see which one you ended.
• Each batch your agent sent: its readings, notes and summary, the connection that sent it and when, and whether you confirmed it or threw it out.
• Each time your agent reads a build brief: the board, the version of the brief, a fingerprint of its text (never the text itself), the time, the connection, and the kind of coding agent it said it is. That is how your Blueprint can tell you which version your agent took.

Why we keep it, and the legal basis. We keep these to run the connection you asked for, to show you your connections and what they sent, to let you end one, and to notice and stop misuse of a key. Where the GDPR applies, we rely on performance of our contract with you (Article 6(1)(b)) to run the connection, and on our legitimate interest in keeping your account secure (Article 6(1)(f)) for the record of when each key was used; you can object (see section 9). In Israel, this notice is given to you under the Privacy Protection Law, as amended by Amendment 13. How long we keep each of these is set out in section 7.

Onboarding details. If you complete onboarding, we collect the details you share, such as your role, your use case, and how you heard about us.

Usage information. We record what happens in the Service so we can run, secure and improve it:

• Visits: the pages you open, the link, site or campaign that brought you, whether you use a phone or a computer, your browser and its language, and the country you are in.
• Product events: the steps you reach and the actions you take, for example starting a board or setting the bar for a test.
• Screen recordings of some visits: a replay of clicks, scrolling and page changes. Everything you type is blurred out, on every page. All other text on screen is blurred too, except on our home, pricing and help pages, where the text is our own. We never record the sign-in and sign-up pages, your account, billing, checkout, settings, onboarding answers, or published boards, or pages shown through a client link.

What our analytics never contains: your name, email address, phone number or IP address, the text you type, what the AI writes for you, the content of your boards, and card or billing details.

Your country, not your address. Our hosting provider works out your country from your connection. We keep the country only. Your IP address is not stored in our analytics and is not sent to our analytics provider.

We record these events in our own database and share them with our analytics provider, Amplitude, as explained in section 6. When you are signed in, events are linked to your account's internal ID, never to your email.

Interview recordings. You can add a recording of an interview you ran. We write it out for your board and keep the sound so you can play it back. Only the sound is kept: for a video, your browser removes the picture first.

Whose information it is. A recording holds the voice and words of the person you spoke to. You choose to add it, so you are responsible for their agreement (Terms, section 4). We handle it on your behalf, only to write it out and to let you play it back.

Who processes it. We send the sound to Google's Gemini AI, on Google's paid terms, only to write it out. Anthropic never receives it. On these terms Google does not use it to improve its products. Google keeps a log of requests for a limited period, only to detect misuse and for legal reasons, and that log may be stored in any country where Google operates, including outside Israel and the EU. Supabase stores the recording (Mumbai, India), so it too leaves Israel, and the EU if you are there (see section 10).

How long we keep it. If a recording cannot be written out or holds no speech, we delete it straight away, and an upload that is not written out is deleted after 1 hour. Otherwise we keep it for 90 days from upload and then delete it automatically; the interview page shows the date. You can delete it sooner at any time, and deleting the board or your account deletes it too. Deleting removes the file itself. The transcript stays on your board like a pasted one, until you delete it or your account.

Who can play it. Only you, signed in, on the interview page. There is no download button. We do not listen to it, and our support tools have no way to play it. A recording is never played through a client link.

If the person you spoke to asks. We pass their request to you. If you do not act on it within 30 days, or they tell us they never agreed, we delete that recording without listening to it.

What we never do. We never build a voiceprint, never use a voice to recognise who someone is, never use it to train any AI, and never use it for anything except writing out your transcript and letting you play it back.

A document you attach is read in your browser: the file itself is never sent to us, only the text read from it, which is kept on your board. Recordings are sent and kept, as described above.

2. How we use your information

We use your information to:

• Provide, operate, and maintain the Service.
• Generate the analyses and blueprints you request.
• Save and display your discoveries and blueprints to you.
• Send your boards to a coding agent you connect, when it asks with your key, and keep what it sends back for you to confirm or throw out.
• Remind you about, and help you record the results of, experiments you asked us to track, by email, only if you opted in (you can unsubscribe at any time).
• Produce de-identified, aggregated insights, such as which problems and opportunities are trending, to improve the Service and, where useful, to publish or share aggregate research. These insights do not identify you, and we never sell your personal information.
• Respond to requests you make, such as emailing you something you asked for, adding you to a list you joined, or following up on an enquiry.
• Secure the Service and prevent abuse.
• Communicate with you about your account or important changes.

Legal bases (EEA, UK and Switzerland). Where the GDPR, the UK GDPR or Swiss law applies, we rely on these legal bases: performance of a contract, to provide the account, discoveries, and blueprints you request; legitimate interests, to secure the Service, prevent abuse, record usage events in our own database, share the events of signed-in use (linked only to your internal account ID) with our analytics provider so we can see how the product is used, and produce de-identified aggregate insights to improve it, balanced against your rights, and you can object at any time (see section 9); consent, for the optional emails you opt into, which you can withdraw at any time by unsubscribing, and for analytics in your browser, the analytics cookies and screen recordings, which start only after you press Accept and which you can withdraw at any time with "Analytics choices"; and legal obligation, to keep records the law requires, such as tax and accounting records for purchases.

In Israel and everywhere else. Analytics in your browser and screen recordings are on when you arrive. This policy tells you what we collect, why, and who receives it, and you can turn them off at any time with "Analytics choices" (see section 6).

3. AI processing & web research

To generate results, the Service sends your inputs (such as the page content you submit, the ideas and angles you enter, and your selections) to third-party AI providers and search services. These providers process the data to return results to us. We do not use your content to train our own models.

Your idea is sent to our AI providers (Anthropic and Google) and, when we run a web search for your board, the search words we build from it go to our search provider (Tavily), to our search-trend provider (DataForSEO) and to our job-listings provider (TheirStack), only to produce your result. These providers handle it under their own terms. Some of them may keep it, and Tavily may use the short search topics and web addresses it receives to improve its own service; see their own policies.

4. Service providers we rely on

We share information with trusted service providers only as needed to run the Service:

These providers process your data on our behalf and under their own privacy and security commitments.

A coding agent you connect is not one of our providers. When you connect one, we send it your boards on your instruction, as described in section 1. The company that runs it, or the AI service you set it to use, receives them under your agreement with it, not under ours.

5. Website content you submit

When you enter a website address, we fetch the publicly available content of that page to analyze it. We store the resulting analysis (such as the company name, description, and problem spaces) as part of your saved discoveries.

6. Cookies

Essential cookies. We use the cookies the Service needs to work: to keep you signed in and maintain your session, to remember your cookie choice, to remember for up to an hour where to bring you back after you sign in, to carry your idea through a Google sign-in for up to 15 minutes, and counters that limit how often one browser can send requests and how much it can use without an account, which protect the Service from abuse. These counters hold numbers and times, not who you are. We do not ask about these, because the Service cannot run without them, and we do not use them for advertising.

The analytics cookies. We set two cookies on our own domain for analytics, each kept for up to 12 months: one holds an anonymous device ID, and the other remembers the link, site or campaign that first brought you. They let us tell visits from the same browser apart, connect a visit to its screen recording, and connect your earlier visits to your account if you sign up later. Our analytics provider's code may also keep a small record in your browser's storage for the same purpose. We never use them for advertising or to follow you on other sites.

When analytics is on.

• In the EEA, the UK and Switzerland: nothing from analytics runs in your browser, no cookie and no screen recording, until you press Accept on our cookie bar. Reject is just as easy as Accept.
• Everywhere else: analytics and screen recordings are on when you arrive. You can turn them off at any time.

We work out which applies from the country your connection appears to come from. If you use a VPN, that can be a different country from where you are. Wherever we place you, you can turn analytics off with "Analytics choices".

Global Privacy Control. If your browser sends the Global Privacy Control signal, we treat it as a No, wherever you are.

Saying no, or changing your mind. Use "Analytics choices" in the footer of every page or at the end of this page. When analytics is off, we set no analytics cookie, remove ones set earlier, record no screen, and send nothing from your browser to our analytics provider. We still count the visit in our own database, without a device ID, without your IP address, and without anything that identifies you. We remember a No for 12 months and a Yes for 6 months. After that, in the EEA, the UK and Switzerland, we ask again.

If you are signed in. Turning analytics off stops the cookies and the screen recordings in that browser. We still record what you do in the product, linked to your internal account ID, and share it with our analytics provider (see section 2). To object to that as well, see section 9.

7. Data retention

We keep your account information and saved content for as long as your account is active. You can delete saved boards and agents at any time.

• Unconfirmed sign-ups: deleted after 30 days, with the idea saved on them.
• The idea saved at sign-up: cleared once your first board starts, at the latest 8 days later.
• The early-access list: kept for up to 12 months, or until you ask us to delete it, and we email you only about early access (see section 1).
• Seat requests: kept for the times set out in section 1, under "How long we keep a seat request".
• Shared board links (Studio): the record of each opening is deleted 90 days after the link stops working, so at the latest about 6 months after the link was made. The link itself, with your private label, its counts and its dates, is deleted 12 months after it stops working. The count of tries that stops link guessing resets after a minute and is deleted within a day (confirmed by ciso 2026-10-24), and the key behind visitor codes is destroyed at the end of each month (see section 1).
• Your Studio name and logo: they stop showing as soon as Studio ends, and are deleted 30 days later. Replacing your logo deletes the old one straight away. If you delete your account, they are deleted within a day.
• The search index (Studio): kept while your plan includes search, and deleted 30 days after it stops. When you delete a conversation, a transcript or a private thread, it is removed from the index straight away.
• Coding agent connections: a live connection is kept until you revoke it or delete your account. A connection you revoked is deleted after 12 months. The readings it sent are not deleted with it: they follow the next point.
• Readings your agent sent: a batch you threw out is deleted after 30 days. A batch still waiting, or one you confirmed, is kept with the test it was sent to until that test, its board or your account is deleted. Readings you confirmed are part of your board and follow its rules.
• Build brief reads: kept until that board or your account is deleted.
• Interview recordings: deleted at once if they cannot be written out, otherwise kept 90 days from upload, or less if you delete them; the transcript stays.
• Backups: anything we delete under these rules can remain in our database provider's backups until they are overwritten on their normal cycle, within 30 days. We do not restore deleted personal data from a backup except to recover from a failure, and if we ever do, we delete it again.
• Confirmed accounts: until you delete them or ask us to.
• Analytics: usage events are kept in our own database for 24 months and then deleted. Screen recordings are kept by our analytics provider for 30 days and then deleted. Usage events sent to our analytics provider are kept for as long as our account with that provider is active, and are deleted when you delete your account or ask us to delete your data (see the next point).
• Deleting your account and your data: email omer@discoveragents.io from the address on the account. Omer Frank, who runs Discover Agents, handles every request himself. We answer within 30 days and usually much sooner, and we delete your personal data within that time, except records we must keep by law (for example, purchase and tax records, kept for as long as legally required) or to settle a dispute. This includes your analytics: we delete your events from our own database and ask our analytics provider to delete everything linked to your account, including your visits from before you signed up and any screen recordings. Copies in our database provider's backups are overwritten on their normal cycle, within 30 days.
• If you never signed up: we do not know who you are, so we can only find your analytics through the device ID in your browser's cookie. To stop future collection, use "Analytics choices" or clear your cookies.
• Correcting your data: you can edit your boards and your idea inside the product yourself. For anything else, or if something we hold about you is wrong, email us and we correct it within 30 days.

De-identified, aggregated numbers that no longer identify you may be kept to improve the Service.

8. Data security

We use reasonable technical and organizational measures to protect your information. However, no method of transmission or storage is completely secure, and we cannot guarantee absolute security.

9. Your rights

Depending on your location, you may have rights to access, correct, export, or delete your personal information, and to object to or restrict certain processing. You can ask us to see, correct or delete the data we hold about you, and to stop emailing you, by writing to omer@discoveragents.io; see Section 7 for how long we take. We will respond in accordance with applicable law. You also have the right to lodge a complaint with a data-protection supervisory authority (in Israel, the Privacy Protection Authority; in the EEA or UK, your local authority). We would welcome the chance to address your concern first, so please consider contacting us before you do.

Objecting to product analytics. If you are signed in and do not want your product events shared with our analytics provider, write to omer@discoveragents.io from your account's address. We stop within 30 days and, if you ask, delete what was already shared.

10. International transfers

This section applies to everyone whose information we hold, including people who open a board someone shared with them. Your information may be processed in countries other than your own, including the United States and India (our database is hosted in Mumbai), and other countries where the providers listed above operate. Where personal data is transferred out of the EEA, the UK, or Israel to a country without an adequacy decision, we rely on appropriate safeguards, such as the European Commission's Standard Contractual Clauses and equivalent mechanisms, to protect it. Contact us at omer@discoveragents.io for more information about these safeguards.

Our analytics provider, Amplitude, stores data in the United States. For transfers from the EEA, the UK or Switzerland we rely on the European Commission's Standard Contractual Clauses.

Our AI provider Anthropic processes data in the United States and other regions.

When you open a board someone shared with you, the record of that opening is stored by Supabase in Mumbai, India, and the page is delivered by Vercel, which handles your connection in the United States and other countries where it operates. Interview recordings you add are stored by Supabase in Mumbai, India. Google keeps a log of the requests that write them out, for a limited period, in any country where it operates.

When you connect your own coding agent, what it reads goes to the company that runs it, or to the AI service you set it to use, which may be in the United States or another country. That happens on your instruction, under your agreement with that company.

11. Children

The Service is not directed to children under 16, and we do not knowingly collect personal information from them. If you believe a child has provided us information, contact us and we will delete it.

12. Changes to this policy

We may update this Privacy Policy from time to time. We will revise the "Last updated" date and, for material changes, provide additional notice where appropriate.

13. Contact

Questions about your privacy or this policy? Contact us at omer@discoveragents.io.