Privacy Policy

Inora ("Inora", "we", "us") operates the inoraflow.com website and the Inora application. We are based in Massachusetts, United States. For anything related to this policy, write to [email protected].

Account information. Your name, email address, a one-way hash of your password (we never store the password itself), and your time zone, which we capture at sign-up because every "today" in your schedule is computed in it. If you sign in with Google, we receive your name, email address, profile picture and Google account identifier instead of a password.

Schedule information. The commitments you enter: classes, work shifts, gym sessions, sports, commutes, sleep times, and any recurring or one-time commitments. Your goals and projects, their deadlines, notes you attach about your progress, and files you upload (course syllabi in particular). The tasks Inora generates from all of this, and the completion status you record against each one.

Preferences. Scheduler settings, priority ranking, time format and theme.

Billing information. Your subscription plan, status and billing period, and a customer reference issued by Stripe. Card numbers are entered directly into Stripe and never reach our servers.

Messages you send us. Contact form and beta feedback submissions, including the topic you pick, your message, and, for beta feedback, the area of the app you were in and your browser type.

Waitlist. If you join the waitlist, your email address and the time you joined.

Technical and security information. Standard server logs (IP address, browser type, requested pages, timestamps), sign-in security records such as failed sign-in counts and session tokens, and a record of which AI features you used and when, which we count against your monthly allowance. That usage record does not include the content of what you sent.

• To build your schedule and rebuild it when something changes. Your commitments define when you are unavailable; your goals define what has to fit in the gaps.
• To break your goals into tasks and to read the syllabi you upload, using the AI processing described in section 4.
• To send account email: verification, password resets, security notices, billing receipts and notices about your account. We do not send marketing email.
• To take payment and manage your subscription through Stripe.
• To keep accounts secure: throttling repeated sign-in attempts, checking new passwords against known data breaches, and detecting misuse.
• To answer your support requests and act on your feedback.
• To meet legal obligations and enforce our Terms of Service.

We do not sell your personal information, we do not share it for advertising, and we do not use it to build profiles for any purpose other than running Inora for you.

Inora uses Claude, a model made by Anthropic, to turn goals into task plans and to read syllabi. When you add or revise a goal, or upload a syllabus, we send the following to Anthropic through its commercial API: the description of the goal, any notes you attach about your progress, your revision feedback, and the contents of the uploaded file. We do not send your name, email address or account identifier with these requests.

Anthropic processes this data under its commercial terms, which do not permit it to train models on customer content. Anthropic retains API inputs and outputs for up to 30 days for reliability and abuse monitoring and then deletes them, unless content is flagged by its safety systems or retention is required by law. Anthropic's handling of API data is described in its data retention documentation.

Content screening. Goals are screened before they are planned. If a submission is flagged as describing harmful or illegal activity, we keep a record of the submitted text, the reason it was refused, and a one-way hash of your email address so we can review the decision if you dispute it. These records are used only to review screening decisions and to enforce our Terms of Service.

Inora runs on a small number of external services. These are the only places your information leaves our own systems:

• Anthropic processes goal text and uploaded syllabi as described in section 4.
• Stripe handles payments and stores your card details and billing history under its own privacy policy. We store only a customer reference and your subscription status.
• Resend delivers our transactional email and sees your email address and the content of each message.
• Google provides sign-in if you choose to sign in with Google. Inora does not currently connect to Google Calendar; if we add that, this policy will describe it first.
• Google Cloud Platform hosts the application, the database, its backups and our server logs, in the us-east1 region (South Carolina, United States).
• Have I Been Pwned is used to check whether a new password appears in a known data breach. We send only the first five characters of a one-way hash of the password, never the password or your email address, so the service cannot learn what you typed.
• Cloudflare provides DNS for inoraflow.com and routes email sent to our addresses to our mailbox.

Each provider is bound by its own terms to use the data only to provide its service to us. We will disclose personal information beyond this list only if the law requires it, to protect the rights and safety of our users, or to a successor if Inora is acquired or reorganized, in which case this policy continues to apply.

Inora sets a cookie that keeps you signed in, a cookie that records that your subscription is active so pages can load without an extra round trip, and a cookie that lives for sixty seconds during Google sign-in to complete the handoff securely. Your theme preference and session are kept in your browser's local storage.

There are no advertising cookies, no analytics cookies and no cross-site tracking. We do not currently use any analytics service. If that changes, we will update this policy before it takes effect.

Your information is kept for as long as your account exists. When you delete your account from Settings, the account is locked immediately and permanently erased 14 days later. That window exists so an accidental deletion can be undone: sign-in stays blocked throughout, and we will email you a cancellation link if you ask for one from the sign-in page.

After erasure, a few records remain:

• Content-screening records (section 4) are kept for two years from the date they were created, then deleted.
• A minimal record of the deletion request itself: when it was made, the reason you chose from the list if you chose one, and a one-way hash of your email address. This shows that a deletion was requested and carried out. Anything you typed in the optional comment box is discarded when the erasure runs.
• Erased data can persist in encrypted database backups for up to 14 days before those backups expire. We do not read or restore backups except to recover from a failure of the service.
• Billing records are kept by Stripe under its retention rules and for as long as tax and accounting law requires.

Waitlist entries are kept until we invite you or you ask to be removed. Server logs are kept for 30 days. Messages you send us are kept in our mailbox for as long as needed to resolve them.

You can correct most of your information directly in the app, and you can delete your account at any time from Settings. You can also ask us to:

• provide a copy of the personal information we hold about you;
• correct information that is inaccurate;
• delete your information, subject to the retention above;
• explain how we use your information, beyond what this policy already says.

Send requests to [email protected]. We may ask you to confirm the request from the email address on the account so that no one else can exercise these rights on your behalf. We respond within 30 days.

California residents. You have the right to know what personal information we collect and how we use it, to request deletion and correction, and to not be discriminated against for exercising these rights. We do not sell or share personal information as those terms are defined in the California Consumer Privacy Act, and we do not use sensitive personal information to infer characteristics about you.

Other regions. If your local law gives you further rights, such as those under the GDPR, you may exercise them the same way. Where that law applies, our bases for processing are the contract we have with you, our legitimate interest in keeping the service secure and working, your consent where we ask for it, and our legal obligations.

Traffic is encrypted in transit and data is encrypted at rest. Passwords are hashed, never stored in readable form, and new passwords are checked against known breaches. Third-party tokens are encrypted. Session tokens expire, rotate, and can be revoked by signing out. Repeated failed sign-ins are throttled.

No system is perfectly secure. If we discover a breach that affects your personal information, we will notify you without undue delay and as required by law.

Inora is intended for people aged 13 and older. If you are under 18, you may use Inora only with the permission of a parent or guardian. We do not knowingly collect personal information from children under 13. If you believe a child under 13 has created an account, contact us and we will delete it.

Inora is operated from the United States and your information is stored and processed there. If you use Inora from another country, you understand that your information will be transferred to and processed in the United States, where privacy law may differ from the law where you live.

When this policy changes, we will post the new version here and update the effective date at the top. If a change materially affects how we handle your information, we will email account holders before it takes effect.

Questions about this policy, or requests about your information, go to [email protected] or through our contact page.