This policy explains what personal information Ideyo collects, why, who receives it, how long we keep it and how you can exercise your rights. It is written to meet Québec’s Act respecting the protection of personal information in the private sector, as amended by Law 25, and, for people in the European Union, the General Data Protection Regulation (GDPR).
01Who we are
Ideyo (ideyo.io) is operated by Mohamed Douaré, in Montréal, Québec, Canada (“Ideyo”, “we”). We are responsible for the personal information described here.
Our person in charge of the protection of personal information can be reached at privacy@ideyo.io.
02What we collect
- Account: your name, email address, a hash of your password (never the password itself), your language and your plan. If you sign in with Google, we also receive from Google your name, your email address (with whether Google has verified it) and your Google account ID; we keep the account ID and the address to recognise you at your next sign-in, and an address Google has verified counts as verified for us. We receive no password, contacts or other Google data.
- Email verification: before we send you any email, you confirm your address through a signed link that expires after 24 hours. We store only the date your address was confirmed, never the link.
- Projects: the ideas, messages and settings you enter, and everything Ideyo produces for you: studies, specifications, designs, code and the log of each run, including the tokens and cost of each model call. On idea boards, the same for each idea, plus the board’s name and the idea you picked.
- Your decisions in the app: the decisions you take on Ideyo’s assumptions at the gates (confirmed, rejected or edited, with your note and the date), and the state of the Get started checklist (whether you dismissed it and which steps you skipped).
- Share links: when you share documents or an idea board with a client, we keep the link’s settings (what is shared, title, expiry, revocation), a SHA-256 fingerprint of the link (never the link itself), how many times it was opened and when it was last opened. We record nothing about the people who open it: no IP address, no browser, no cookie, no analytics.
- Agency branding: your agency name, contact line and colour, and the logo image you upload (PNG, JPEG or WebP, at most 512 KB), stored in our database to brand your reports and shared pages.
- Notifications: your choice of notifications per event and channel. When you turn on push notifications on a device, we store the subscription your browser gives us (the push service address and the encryption keys for that device) and a short device label derived from your browser, such as “Chrome on macOS” (not the full browser identification string), with the date of the last successful delivery. For each notification we keep a record of the project, the kind of event, the time and whether it went out by push or email.
- Keys and connections: the API keys you add (with the names you give them and when each was last used) and your GitHub token, encrypted at rest with AES-256-GCM. We only ever display their last four characters.
- Billing: your plan, purchases, amounts and invoices. Cards are handled by Stripe and mobile-money payments by CinetPay; we never see your card number or your mobile-money PIN.
- Technical data: IP address, browser type and timestamps in server logs, used for security and debugging. A strictly necessary session cookie keeps you signed in; during a Google sign-in, a second cookie, sealed and valid for 10 minutes, protects the exchange. A preference cookie remembers your theme (light, dark or system), and your browser’s local storage keeps display preferences such as pane sizes. We use no advertising or cross-site tracking cookies.
03Why we use it
- To provide the service you asked for: run your projects, store your documents, notify you when a project needs you, publish the share links you create and open pull requests (GDPR: performance of a contract).
- To bill you and keep accounting records (contract; legal obligation).
- To secure the service, prevent abuse and fix bugs (legitimate interest).
- To forecast what a stage will cost: we compute anonymous averages of the tokens and time that finished stages used, across all accounts, by stage and model tier. Only token counts, durations and the model tier enter that calculation, never the content of a project or who it belongs to; demo projects are left out (legitimate interest).
- To write to you about your account and, only if you agree, about new features (contract; consent, which you can withdraw at any time).
We do not sell personal information, and we do not use your projects to train AI models.
04Who receives it
AI model providers. To run a stage, Ideyo sends the relevant project text to the provider you chose for that stage, for example Anthropic, OpenAI, Google, Mistral, DeepSeek or OpenRouter. With your own key, that exchange is also governed by your agreement with the provider; for managed purchases, by Ideyo’s. Choose providers accordingly, and do not put information in a project that you are not allowed to share.
GitHub, when you connect it, receives the code and documents Ideyo pushes to your repository.
Google, when you choose “Continue with Google”, authenticates you and sends us the information listed above. Google processes your sign-in under its own privacy policy.
Browser push services, when you turn on push notifications: the service your browser uses delivers them, namely Google (Firebase Cloud Messaging, for Chrome, Edge, Opera, Samsung Internet and Brave), Mozilla (Firefox), Apple (Safari and home-screen apps on iPhone and iPad) or Microsoft (older Edge). We only send to these services. Each notification is encrypted for your device: it contains a title, a short text naming the project and the event (for a failed run, the beginning of the error message), a link into the app and the project’s identifier. The push service cannot read it, but it sees that a notification was sent to your device and when.
Our email relay, when email notifications are on: the SMTP provider we use sends them, only to an address you have verified. A notification email contains the project name, the event (for a failed run, an excerpt of the error) and a link into the app, and every one carries a one-click unsubscribe link; that link is signed, turns email notifications off and can do nothing else.
People you share a link with (and anyone they forward it to) can read the documents or the idea board comparison you chose, your agency name, logo and contact line, or your name when no agency name is set, until the link expires or you revoke it. Only share what you are allowed to share.
Payment processors: Stripe for cards, CinetPay for mobile money.
Hosting providers, bound by contract to use the information only on our behalf.
We disclose information to public authorities only when the law requires it.
05Transfers outside Québec and the European Union
Some of the recipients above process information outside Québec and outside the European Union, notably in the United States. Before such a transfer we assess, as Law 25 requires, whether the information will be adequately protected, and where the GDPR applies we rely on safeguards such as the European Commission’s standard contractual clauses.
06How long we keep it
- Account and projects: as long as your account is open, or until you delete them. Closing a project only moves it to Closed, where it stays with its documents until you reopen or delete it.
- Deleting a project (from its ⋯ menu, from the Closed list on the Projects page or from the command palette, after typing its name) is permanent and immediate: the project, its documents, working tree, activity log, messages, gate and assumption decisions, model usage, notification records and share links (whose pages stop working) are deleted from the database at once, and from backups within 30 days. It also leaves its idea board, and a board left without an idea is deleted. A purchase made for that project keeps its billing record, without the project. A deleted project cannot be recovered, by you or by us.
- Share links: until you delete the project or your account; a revoked or expired link stops working at once and keeps only its settings and counters, for your list of links.
- Push subscriptions: until you turn notifications off on that device, remove the device in your settings, or the push service tells us the subscription no longer exists.
- The anonymous cost averages are recomputed every few minutes from the runs that still exist; when a project or an account is deleted, its runs no longer count.
- When you delete your account (Settings → Danger zone, confirmed with your password or, for an account created with Google, your email address), your profile, sign-in methods and sessions, keys, GitHub token, projects and their documents, idea boards, share links, branding, push subscriptions, notification records and purchase history are deleted at once, runs in progress are stopped and any paid subscription is cancelled; backups expire within 30 days.
- Billing records: as long as tax law requires (six years in Québec). After an account is deleted, the invoices and payment records our payment processors (Stripe, CinetPay) must keep stay with them for that period.
- Server logs: 30 days.
07How we protect it
Encryption in transit (TLS) and at rest for keys and tokens, end-to-end encryption of push notifications, share links stored only as fingerprints and shared pages kept out of search engines, access limited to the people who run the service, and a security review of every release. If an incident creates a risk of serious injury, we notify you and the Commission d’accès à l’information du Québec and, where the GDPR applies, the competent authority within 72 hours.
08Your rights
You can ask to access your personal information, correct it, delete it, receive it in a structured and commonly used format, or stop receiving messages. In the European Union you can also object to processing based on legitimate interest and ask us to restrict processing. You can exercise the main ones yourself, at any time, without asking us:
- Access and portability. Settings → Profile & language → Your data → Download my data gives you at once a zip file of everything Ideyo keeps about you. account.json holds your profile, sign-in methods, preferences and notification settings, the state of the Get started checklist, your plan, subscription and purchases, the labels of your push devices, your branding (with your logo as a file), your API keys and GitHub connection as metadata, your share links and your idea boards. Each project, open or closed, has its own folder with project.json (settings, model routing, status, verdict, gate and assumption decisions, spend per model and per run, your messages, notification records), activity.jsonl (the activity log, one event per line) and every document and working-tree file as a file. The export never contains a secret: API keys appear only as their provider, label and last four characters, the GitHub connection as its login and token type, share links without their address and push devices without their keys. You can download it three times an hour; an account holding more than 512 MB of content is exported on request at privacy@ideyo.io. A single project’s documents and working tree can also be downloaded from the project.
- Deletion. Delete a project from its ⋯ menu (Delete permanently…) and your account from Settings → Danger zone, with the effects described in “How long we keep it”.
- Correction. Change your name, language and settings in Settings; to change your email address, write to us.
For everything else, or if you cannot use the app, write to privacy@ideyo.io. We answer within 30 days.
Ideyo’s verdicts and scores are recommendations about ideas, not decisions about people: no decision about you is made solely by automated processing.
09Children
Ideyo is not intended for people under 16, and we do not knowingly collect their information.
10Complaints
If our answer does not satisfy you, you can complain to the Commission d’accès à l’information du Québec (cai.gouv.qc.ca) or, in the European Union, to the data protection authority of your country.
11Changes
We post every change here with a new date, and we tell you by email before a significant change takes effect.