PRIVACY POLICY.

• We collect what running a recipe app needs: your account, what you post, and what you do with recipes.
• We use it to run the service, to personalise your feed, and to show creators how their recipes are doing.
• We do not sell your personal information.
• You can download your account data, or delete your account, from settings. Deletion is immediate and permanent, subject to the safety and legal-retention exceptions below.

The rest of this page is the detail. It describes what the software actually does today, not what we might do later.

Reciped Inc. is a company incorporated under the Canada Business Corporations Act, with its head office in Ontario, Canada. We decide how and why your personal information is handled, which makes us the organisation accountable for it, and the person in charge of protecting personal information can be reached at [email protected]. Write to that address for any question or request in this policy.

Canada's federal privacy law, PIPEDA, is the baseline for how we handle your information. If you live in Quebec, Law 25 applies to you as well; in the European Economic Area or the United Kingdom, the GDPR does. Where one of those gives you more than this policy describes, the law wins.

Your account. Email address, username, display name, and password. The password is stored only as an Argon2 hash, so we cannot read it. Optionally a bio, an avatar, social profile handles, and your accent colour preference. If you go PRO, your subscription status.

What you post. Recipes, ingredients, steps, photos, comments, and collections, including drafts you never publish.

What you do. Likes, saves, follows, recipes you have cooked or hidden, and searches you run. We also log lighter signals about which recipes you were shown, opened, clicked, and how long you stayed. These are tied to your account while you are signed in. Signed out, the same signals are counted only in aggregate for the creator, in a form that identifies a browser by IP address and user agent and is never attached to a person.

Imports. The link, file, photo, or video you import from, the extracted result, and a record of the processing run.

Payments. If you subscribe, Stripe collects and holds your card details. We receive and store only a customer reference and the state of your subscription. Your full card number never reaches our servers.

Technical records. Server logs of requests, including IP address, user agent, and a correlation id, plus performance and error telemetry. Logs are configured to redact personal fields.

Safety and enforcement records. Warnings, suspensions and bans; one-way hashes of the email address, device id, Google account id and network addresses observed for an account; and records of signups that match the enforcement list. A matching signup record can include the attempted email address, a masked network address and the user agent so staff can review false positives.

Email verification and password resets. Short-lived tokens tied to your address, so those links work once and then expire.

• To run your account and the service, which is the contract between us: signing you in, storing your recipes, sending service email, taking payment for PRO.
• To personalise your feed and search, and to show creators aggregate reach for their recipes. We rely on our legitimate interest in making a recipe app that is useful and that creators can see the effect of.
• To keep the service safe: rate limiting, abuse and spam prevention, and moderating images. This includes keeping an account we have removed for abuse from immediately signing up again, for which we store one-way hashes of identifiers the account signed in with and link those hashes to its enforcement record. Legitimate interest, and in the case of illegal content, a legal obligation.
• To meet legal obligations, including tax records for payments and responding to lawful requests.

Where the law requires consent, for example non-essential cookies, we ask first and you can withdraw it at any time.

The FOR YOU feed is ranked by a model. It builds a profile of your tastes from what you save, like, cook, hide, and open, and uses it to order recipes. That is profiling, so we say so plainly.

No decision with a legal or similarly significant effect is made about you automatically. Ranking affects the order recipes appear in, nothing else.

If you would rather not see a personalised feed, the FOLLOWING tab is ordered by time and shows only accounts you chose to follow, and search is not personalised. Signed-out browsing is not personalised at all. Deleting your account erases the taste profile with everything else.

Importing a recipe runs it through a language model to pull out ingredients, steps, and timings. Video imports are transcribed and sampled frame by frame first. This processing runs on infrastructure we operate, unless we have configured an external model provider, in which case the content of the import is sent to that provider to be processed.

Images uploaded to Reciped are checked automatically before publication to detect sexual, violent, and other prohibited content. Where an external moderation provider is configured, the image is sent to it for that check.

Both are described here rather than buried, because in both cases something you uploaded may leave our systems.

We use cookies that the service cannot work without, and no others today:

• reciped_at, your signed-in session, about 15 minutes.
• reciped_rt, the token that quietly renews that session, 30 days.
• reciped_did, a random id for the browser, 2 years. It exists to stop an account we have removed for abuse from simply signing up again on the same machine. Its one-way hash is linked to the accounts that sign in from that browser for enforcement only; it is never used for analytics or advertising, and the raw id is not stored in our database.
• Short-lived cookies used only when a staff member is troubleshooting an account on request, which is recorded in an internal audit trail.

The mobile app stores an equivalent random installation identifier in secure device storage and sends it for the same safety and enforcement purposes.

They are set to be unreadable by scripts in your browser, sent only to this site, and encrypted in transit in production. We do not use analytics cookies, and there is nothing here for you to consent to, which is why you are not being asked.

The free plan is funded by ads, and PRO removes them. Ads are not being served at the moment: the integration exists in the product but is switched off, so no advertising script runs and no advertising cookie is set.

When we do switch it on, ads will be served by Google AdSense, which sets its own cookies and may use them to personalise advertising. We will update this page and, where the law requires consent for that, ask you before any advertising cookie is set. PRO accounts never load the advertising script at all.

We do not sell your personal information to advertisers.

Other people on Reciped. Your username, avatar, bio, social profile handles, published recipes, comments, and follower lists are public, including to people without an account and to search engines. Drafts, saves, collections, cooked history, and your email address are not.

Companies that process data for us, under contract and only on our instructions:

• Stripe, for payments and subscription billing.
• Resend, to send account email such as confirmations and resets.
• Our cloud hosting and object storage providers, which hold the database and your uploaded images and files.
• Where configured, an external language-model or image-moderation provider, as described above.

Authorities, when the law requires it, or where it is necessary to prevent serious harm. Child sexual abuse material is reported and preserved without notice to the account concerned.

A future owner, if the service is ever sold or merged. We would tell you before your information moved.

We do not sell your personal information.

Reciped is operated from Canada, and some of the providers above process data in the United States and elsewhere. That means your information may be stored or handled outside your country and be accessible to courts and authorities there. Where we transfer personal information out of the European Economic Area or the United Kingdom, we rely on the European Commission's standard contractual clauses with the provider.

• Your account and everything in it, until you delete it. Deletion is immediate and permanent, except for the safety and legal records described below.
• Safety and enforcement records. Signals and sanction history linked to an account are kept while the account exists. An enforcement-list hash can remain after account deletion until its stated expiry or until staff removes it; a block tied to an indefinite ban has no automatic expiry. Signup-match records are kept while needed to review abuse and false positives.
• Sign-in tokens, 30 days from last use, and sooner if you sign out.
• Email confirmation links, 24 hours. Password reset links, one hour.
• Finished imports and the files you uploaded for them, about three days, then deleted.
• Aggregate creator statistics, which contain no personal identifiers, are kept after an account closes so a recipe's history stays intact.
• Records we must keep by law, such as payment records, for as long as the law requires.

You can, at any time:

• Get a copy. Settings gives you a JSON file of your portable account data, including your enforcement history and the hashed signals linked to your account.
• Delete your account. Also in settings. It asks for your password, and there is no undo. Limited safety and legal records may remain as described above.
• Correct what is wrong. Edit your profile and your recipes directly, or write to us.
• Object, or ask us to restrict use. Write to us and tell us what you object to.
• Withdraw consent where we asked for it, without affecting what we did before you withdrew it.

Write to [email protected] for anything the settings page does not cover. We answer within 30 days.

If you are not satisfied, you can complain to a regulator: in Canada the Office of the Privacy Commissioner, and additionally the Commission d'accès à l'information if you live in Quebec. In the European Economic Area or the United Kingdom, your national data protection authority.

Passwords are hashed with Argon2. Session tokens live in cookies your browser will not hand to scripts. Traffic is encrypted in transit. Requests are rate limited, and sensitive actions such as deleting your account ask for your password again.

Staff access to production data is limited to what support and operations need, and every change made through our internal console is written to an append-only audit trail, including the rare cases where a staff member views an account to troubleshoot it.

No service is perfectly secure. If a breach affects you and carries a real risk, we will tell you and the relevant regulator as the law requires.

Reciped is not for children under 13, and we do not knowingly collect their information. If you believe a child has an account, write to [email protected] and we will remove it.

As the product changes, this page changes with it. The effective date at the top always reflects the current version, and for material changes we will tell you by email or in the app before they take effect.