Privacy Policy
Last Updated: October 13, 2026 • Effective Date: October 13, 2026
Introduction
Lykke (“we,” “our,” or “the Service”) is operated by Lykke Technologies Inc. and consists of the Lykke web application at getlykke.com, the Lykke iOS app, the Lykke Knowledge Companion Chrome extension, and related APIs. The Service helps students organize course materials, take notes, and use AI to generate study tools such as flashcards, quizzes, study guides, summaries, infographics, and course wikis.
This Privacy Policy explains what information we collect, how we use it, how your content flows through our AI providers, and your rights regarding your data. By using the Service, you agree to the collection and use of information in accordance with this Privacy Policy.
If you sign in with Google or connect Google Calendar, Section 5, Google User Data, explains exactly what we access from Google, how we use, store, share and protect it, and how to delete it.
1. Information We Collect
Account & Identity
- Profile: Name, email, profile picture, institution (if provided)
- Authentication: Session tokens (we do not store passwords in plaintext)
- Preferences: Settings, selected classes, theme, notification preferences
Canvas LMS Data
When you connect Canvas:
- User Information: Canvas user ID, profile (name, email)
- Course Information: Names, codes, identifiers, descriptions, enrollment, term info
- Course Materials: Files (PDFs, docs), assignments, announcements, modules, calendar events, syllabus
- Course Roster: Names and roles of the instructors and classmates Canvas shows you, for course context (you can turn this off in the extension's settings)
- Pages you study: When you press Study this with Lykke on a Canvas page, or Study on an item in the extension's This week list, that page's or item's text (an assignment's instructions, for example), title and address, the course's name and any passage you highlighted, kept with your account for 30 days so Lykke can answer from it. The This week list itself is read from your Canvas planner in your browser and is not sent to Lykke.
Google Account & Calendar
- Sign in with Google: Name, email address, profile picture
- Google Calendar (optional): Events on your primary calendar and the email address of the connected Google account, only after you choose to connect it
- Details in Section 5
Your Study Content
- Notes: Text, rich content, block-level annotations on wikis
- Documents: Files you upload (PDF, DOCX, PPTX, images, etc.) and their extracted text
- Generated Materials: Flashcards, quizzes, summaries, infographics, study guides, wikis
- Chats: Prompts and responses exchanged with the AI study assistant
Voice, Camera & Recordings
Only when you use these features:
- Video Tutor (Luca): While a lesson runs, your microphone audio goes from your browser directly to OpenAI, which listens and answers. Lykke's servers don't receive the audio. Lykke keeps a transcript of what you and Luca said, and the pictures he drew, as a lesson recap in your account and in your notes, until you delete it.
- Voice notes: When you dictate a note, your browser's speech recognition turns it into text (in Chrome, that's Google's speech service), and the recording is attached to your note like any other file.
- Focus Mode camera coach: Only if you choose Camera coach and allow your camera. During a sprint, about every 15 seconds, a small, low-resolution frame goes to Google Gemini (or to OpenAI if Gemini is unavailable), which answers one question: are you looking at the screen? Lykke doesn't store the frames. It keeps the verdict and the time, which you can clear. No camera mode uses tab switches and idle time only.
Web Clipper & YouTube
- Web Page Content: Text, titles, URLs you save via the clipper
- YouTube: Video URL, title, and transcript when you save a video
- Class Tags: Optional class associations you apply
- Timestamps: When content was saved
Usage & Analytics
- Product Analytics: Events (feature usage, clicks) via PostHog
- Website Analytics: Pages visited, device and browser details, and approximate location (from your IP address), collected by Google Analytics through Firebase with Google cookies. Not used for advertising. See Section 9.
- Diagnostics: Error reports, request logs, performance metrics
- Credits: AI generation credits consumed and remaining
- Optional AI-assistant learning signals: If you opt in through MCP settings, the assistant's reason for reading or searching a course is classified into a course topic and learning intent. Only that classification, your account id, course id, and time are stored for up to 30 days.
Technical Data (Local)
Stored in your browser / on-device:
- Cached course lists, documents, and notes for performance
- Sync timestamps and status
- Selected classes and filter state
2. How We Use Your Information
Primary Purposes
- Sync & Organize: Bring your Canvas and uploaded materials into your personal knowledge base.
- Search: Index your content so you can find and reference it semantically.
- AI Study Tools: Generate flashcards, quizzes, study guides, summaries, infographics, mind maps, practice problems, and course wikis from your selected sources.
- Conversational Study: Answer questions about your material in chat, with citations back to the original source.
- Personalization: Remember preferences, recent chats, what you tell a chat for the rest of that chat (your classes, a test date, how much time you have; deleted with the chat, and after 180 days), and saved materials.
- Practice that remembers: Keep a learning record (the practice questions you answer and how sure you said you were, the sections you read, and when you ask Lykke for help) so practice picks up where you are and comes back to things before you forget them.
Your learning record
Lykke keeps your learning record by default. You can see it, pause it, or delete it in Settings → Learning record. Records are deleted after 180 days. If you type an explanation under a practice answer, Lykke keeps it as your own content, like a note, until you delete it. Only you can see your learning record, unless you share a snapshot of it from Learning history. It is not sent to an AI provider unless you turn on personalization.
Specific Uses
- Content Processing: Extract text from PDFs, DOCX, images, and other uploads for indexing.
- Embeddings: Generate vector embeddings of your notes and documents to power semantic search and retrieval-augmented generation (RAG).
- Duplicate Prevention: Track which files have been uploaded to avoid redundancy.
- Quota Enforcement: Track credits consumed by AI generations.
- Course Question Insights: Questions you ask about a course anywhere in Lykke (its Ask AI, Lykke chat, the study page, lessons with Luca) are shown to that course's owner only after an AI rewrites them without your name or personal details and groups them with other students' questions. Nothing is shown until at least three students have asked, owners never see who asked, and your questions are kept for up to a year and deleted with your account.
- Canvas Course Insights: When you sync a Canvas course, questions you ask Lykke about that course (in Lykke chat from its pages or its material, on its study page, or in a lesson with Luca) may be shown to that course's verified instructor, only after an AI rewrites each one without your name or personal details and groups it with other students' questions. Nothing about a course is shown, not even a count, until at least five students have asked; instructors never see who asked or your conversations; and questions from the course's instructors and TAs aren't counted. We verify an instructor through their school's faculty directory and the course roster, or by our own review. Only questions asked after this section took effect are used.
- Answer Quality Reviews: To improve Lykke's answers, we may compare a sample of them with answers other AI models give to the same question (Anthropic's Claude and OpenAI, Section 4). A sample holds your question, the conversation before it and the course or Canvas material the answer used; it's kept up to 30 days, the comparison results up to 90, and neither is used to train any model. Our staff may read them to find what to fix.
- Opted-in Educator Insights: Summarize broad course topics explored through connected AI assistants for a course owner only after at least three students contribute; no individual MCP reason or request is shown.
3. Where Your Data Is Stored
Backend Services
- Primary API: api.getlykke.com
- File Storage: AWS S3 (
getlykke-assets) - Database: MongoDB
- Vector Database: Zilliz (Milvus Cloud)
Storage Details
Data Location
Data is stored on servers located in the United States, encrypted at rest and in transit (TLS/HTTPS).
Files You Upload
Files you upload, and files synced from Canvas, are stored in Amazon S3. Each file has its own web address with a long random part. We don't list or publish these addresses, but anyone who has a file's address can open it, for as long as we store the file. The same goes for pictures Lykke cuts from your PDFs to illustrate a course.
A file's address is shown to you and to people who can see the file in Lykke, such as classmates in a synced Canvas class. Some providers in Sections 4 and 6 receive it so they can read the file. If you publish a course built from your files, the course links to them, so anyone reading it, search engines included, can open them.
Pictures and files that an AI assistant you connect through Lykke's MCP connector adds to your notes are stored the same way, and processed like your own uploads. When such an assistant reads one of your notes or documents, Lykke sends it the pictures and the text of the attached files, but not their web addresses.
Embeddings
Vector representations of your notes and documents are stored in Zilliz to power semantic search and source retrieval during AI chat.
4. AI Providers & What We Send Them
For ordinary study generations and chat turns, Lykke sends portions of your selected study content and your prompt to third-party AI providers. If you opt in to MCP learning signals, an AI model also classifies the reason your connected assistant gives for reading or searching a course; that reason is not stored in the learning signal. Educator summaries are generated from grouped course topics and counts, without individual reasons or requests. We do not send other users' content to fulfil your request.
Your private MCP activity history records tool names, connected app or API key labels, times, outcomes, durations, and the brief reasons supplied by your assistant for up to 30 days. Recording is enabled by default and can be paused or cleared in Settings → AI assistants → MCP activity. Raw tool arguments and results are excluded from this history; successful course reads may include their course identifier. These reasons are visible only to you and are separate from optional educator summaries and shared learning snapshots.
Learning records remain private unless you explicitly select evidence cards and create an expiring sharing link. Anyone with that link can see the selected snapshot and the profile fields you chose; you can revoke the link. Raw tool reasons, prompts, answers, and private conversations are excluded. Daily preparation is off by default; when enabled, selected synced teaching sources are sent to an AI provider to generate source-cited questions, and the preparation is retained for 30 days.
| Provider | Model(s) | Features | What We Send |
|---|---|---|---|
Google Gemini Google LLC | gemini-2.5-pro, gemini-flash-latest | Study material generation (flashcards, quizzes, summaries, study guides, infographics), course wiki generation, chat responses, Ask AI answers when you pick Gemini in its model picker, and reading uploaded files other tools can’t (Word, PowerPoint, Excel and CSV files, and some PDFs) through the Gemini Files API. Google deletes files sent this way within 48 hours. | Prompts, selected notes, selected document text/files, chat history for the current session. For Ask AI: your messages and the chat so far, the course text and any passage you highlight, your learner profile and recent practice results. |
OpenAI OpenAI, via Microsoft Azure and directly | GPT models for chat, including GPT-6 and GPT-5.6 in Ask AI; text-embedding-3-large (embeddings) | Ask AI answers (GPT-6, the default, sent to OpenAI directly; GPT-5.6, if you pick it, through Azure), chat / generation fallback, semantic search embeddings, and reading the text in images you upload or that an AI assistant you connect adds to your notes, and answer quality reviews (Section 2). | Prompts and content snippets for chat; for Ask AI, your messages and the chat so far, the course text and any passage you highlight, your learner profile and recent practice results; text of your notes and documents for embedding; the web address of each image you upload, which Azure OpenAI uses to download it. |
Anthropic Anthropic, directly or through OpenRouter, Inc. | Claude Sonnet (answer quality reviews); claude-3.5-sonnet (fallback) | Chat / generation fallback, and answer quality reviews (Section 2): a sample question, the conversation before it and the material its answer used. | Prompts and content snippets from selected sources; for answer quality reviews, the sample described in Section 2. |
Perplexity Perplexity AI, Inc. | sonar | Web search with citations inside AI chat. | Search queries you issue. Your private notes and documents are not sent. |
Mistral AI Mistral AI | mistral-ocr-latest | Reading the text in PDFs that have no usable text layer, such as scans. | The web address of a PDF you upload, sync, or have a connected AI assistant add to a note; Mistral downloads the file from it. |
OpenAI (Video Tutor) OpenAI | GPT-Live (real-time voice) | The Video Tutor (Luca): a live spoken lesson. Your microphone audio goes from your browser directly to OpenAI; Lykke’s servers don’t receive it. | Your microphone audio while a lesson runs, the lesson’s material and the conversation so far. Lykke turns OpenAI’s response storage off for these sessions; OpenAI may keep data briefly under its API terms, for example to monitor abuse. |
Google Gemini (Focus Mode) Google LLC (OpenAI if Gemini is unavailable) | Gemini vision models | Focus Mode’s camera coach: judging whether you’re looking at the screen. | One small, low-resolution camera frame about every 15 seconds while a camera-coach sprint runs, and the topic you’re reading. Lykke doesn’t store the frames, only the verdict and the time. |
Model training
We use these providers through their paid API tiers. Under current provider terms (OpenAI, Anthropic, Google for API/Vertex, Perplexity API), content submitted through the API is not used to train their foundation models by default. If a provider changes its policy, we will update this section. Content is retained by each provider per their own retention policy — typically short-term for abuse monitoring.
Why multiple providers?
We route different features to the model best suited to the task and fall back across providers for reliability. The table above lists the primary use for each.
5. Google User Data
This section covers the data Lykke receives from Google APIs when you sign in with Google or connect Google Calendar: what we access, and how we use, store, share, protect, keep and delete it.
Limited Use. Lykke's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
What we access
- Sign in with Google. Google shares your name, email address and profile picture with Lykke. We use them to create your account and sign you in.
- Google Calendar (optional). Only when you choose Connect Google Calendar, Lykke asks Google for permission to see the events on your calendars (
https://www.googleapis.com/auth/calendar.events.readonly), and for the email address of that Google account so Lykke can show which account is connected. This permission is read-only: Lykke cannot create, change or delete your events, or answer invitations. Google's permission covers all of your calendars, but Lykke only reads events on your primary calendar. - If you connected Google Calendar before October 1, 2026, Lykke asked then for permission to change your events too, and Google may still list that permission. Lykke no longer uses it. To narrow it to read-only, disconnect on the Calendar page and connect again.
- For each event on your primary calendar, Lykke receives the title, description, location, start and end time and time zone, video-meeting link, organizer and guests (their names, email addresses and RSVP responses), recurrence, status, and Google's link to the event.
- Lykke does not access your list of calendars, your other calendars, their sharing settings or your Calendar settings.
How we use it
Lykke uses Google Calendar data only for calendar features you can see in Lykke:
- Showing your events and invitations on the Calendar page, alongside your courses and study plans.
- Lykke doesn't make changes to your calendar. To add an event or a study block, Lykke opens Google Calendar's own event page with the details filled in, and the event is saved only if you press Save there. You answer invitations and delete events in Google Calendar.
- Listing up to five upcoming events (title and time) in Lykke's optional weekly email. You can turn that email off under Settings → Notifications, or with the unsubscribe link in any email.
We do not use Google user data for advertising, sell it, or use it to determine creditworthiness or for lending. We do not use it to develop, improve or train AI or machine-learning models.
Your calendar and AI
- Lykke's AI features never receive your Google Calendar data. Your events are not sent to Google Gemini, OpenAI, Anthropic (via OpenRouter), Perplexity or any other AI provider listed in Section 4, and they are not used in chats, study tools or anything Lykke generates.
- If you connect your own AI assistant to Lykke through Lykke's MCP connector, it can make a Google Calendar link for an event you ask for, which you open and save yourself. It cannot read or change your calendar, and Lykke sends it none of your Google Calendar data.
How we store it
- Google tokens. When you connect, your browser receives only a one-time code from Google. Lykke's server exchanges that code for the tokens that let it reach your calendar, so the tokens never reach your browser. Our application encrypts them before saving them, with a key that is kept on our servers and not in the database, and they are never written to our logs.
- Your events. Lykke keeps a copy of the events on your primary calendar in our database (MongoDB Atlas), covering 30 days in the past to 12 months ahead, plus any later changes. This copy lets the Calendar page load quickly and show new invitations. While your calendar is connected, Lykke refreshes it from Google about every five minutes.
How we share it
We do not sell Google user data, and we do not transfer it to advertisers, data brokers or information resellers. We share Google Calendar data only:
- with the providers that host Lykke, Amazon Web Services (our servers) and MongoDB Atlas (our database), which store and process it only to run Lykke;
- with Google, which delivers our weekly email through Gmail;
- when needed for security (for example, investigating abuse) or to comply with applicable law; or, with your explicit prior consent, as part of a merger, acquisition or sale of assets.
Our product analytics (PostHog) records that you connected Google Calendar and the domain of the connected account (for example, school.edu). It never receives your events.
How we protect it
- Encryption in transit. Traffic between your browser, Lykke's servers, our database and Google's APIs is encrypted with HTTPS/TLS.
- Encryption at rest. Our database and its backups are encrypted at rest, and Google tokens get a second layer of encryption from our application before they are saved.
- Tokens stay on our servers. Google tokens are used only by our servers to call Google, and are never sent to your browser or to any other service.
- Per-account access. Every calendar request is tied to your signed-in Lykke account, and Lykke only returns the events stored for that account.
- Least access. Lykke asks Google only for read access, and calls the Google Calendar API only to read your primary calendar for the features listed above.
- Restricted staff access. Only a small number of authorized Lykke engineers can access our production servers and database, and only to operate and support the service.
- No human reading. No one at Lykke reads your Google Calendar data unless you ask us to (for example, in a support request), it is necessary for security (for example, investigating a bug or abuse), the law requires it, or the data has been aggregated for internal operations.
- Breach notification. If we learn that your data was accessed without authorization, we will notify you as required by law.
How long we keep it, and how to delete it
- Lykke keeps your Google tokens and the copy of your events only while your Google Calendar is connected.
- Disconnect at any time. On the Calendar page, choose Disconnect. Lykke asks Google to revoke its access and immediately deletes the stored tokens and every copied event from our database.
- From your Google Account. You can also remove Lykke's access at myaccount.google.com/connections. Lykke can then no longer read your calendar. At its next sync, usually within five minutes, Lykke finds its access removed and deletes the stored tokens and every copied event. It keeps only the email address of that Google account, so the Calendar page can offer Reconnect; choose Disconnect to delete that too.
- Deleting your account. When you ask us to delete your Lykke account at hello@getlykke.com, we also ask Google to revoke Lykke's access, and delete your Google tokens and stored events.
- Backups. Deleted data can remain in our encrypted database backups for a limited time, until those backups expire.
6. Other Third-Party Services
Accessed on your behalf via your own auth. We do not store Canvas passwords.
File storage for uploaded documents and generated assets.
Primary database for user, class, note, and material records.
Vector database storing embeddings of your notes and documents for semantic search.
Product analytics: usage events and feature flags. Does not include your study content.
Sign in with Google, and website analytics through Google Analytics (see Section 9).
Payments for subscriptions, credits and courses. We never see or store your full card number.
Fetching transcripts and metadata when you save a YouTube video.
Reads web pages you add as course sources when we can’t load them, or find their links, ourselves. It receives the page’s web address, or the address of an image you add as a source.
Reads events on your primary calendar, only if you connect Google Calendar. See Section 5.
Data We Do NOT Share
- ✕ Sell your personal information
- ✕ List or publish your private notes or files. File links are unlisted, not locked: see Files You Upload.
- ✕ Use your content for advertising
- ✕ Share your information with your institution, beyond what you already have in Canvas and the anonymized course questions a verified instructor sees (Canvas Course Insights)
- ✕ Train our own or third-party foundation models on your content
7. Chrome Extension Permissions
| Permission | Why We Need It |
|---|---|
| storage | Keep your Lykke sign-in, chosen school, course selection, sync progress and preferences on your computer. |
| tabs | Read tab addresses to recognise your Canvas and its sign-in pages, so the extension shows the right guidance and never runs on sign-in pages. Browsing history is not collected or sent. |
| scripting | Show the Lykke guide on Canvas pages, read the page you choose to save, and read Canvas through an open Canvas tab when needed. |
| activeTab | Save the page or video you are viewing, only when you click Save. |
| identity | Sign in with Google. |
| Canvas sites (*.instructure.com and school Canvas domains) | Read the courses you choose to sync, read-only, with the Canvas session you already have. We never see or store your Canvas password. |
| api.getlykke.com | Communicate with the Lykke backend. |
| *.amazonaws.com, *.inscloudgate.net, *.instructure-uploads.com, *.canvas-user-content.com | Read a course file you chose to sync from where Canvas stores it. |
| Other sites (optional) | Asked one site at a time, only if you enable Lykke on a Canvas site that is not built in. |
8. Your Data Rights
- Access: View all collected data by logging into your Lykke account.
- Delete: Delete individual notes, documents, classes, or generated materials from the app. Request full account deletion via hello@getlykke.com (Settings → Delete Account starts that email).
- Remove synced Canvas content: On the web under Settings → Canvas (and in the extension from version 2.1, under Settings → Privacy & data), remove one synced course or everything you synced. Your files from those courses are deleted from Lykke, you leave their classes, and the courses stop syncing. Canvas itself is not changed.
- Disconnect: Unlink Canvas from the Extension settings or the web app. Disconnect Google Calendar on the Calendar page, which revokes Lykke's access and deletes the stored tokens and events (see Section 5).
- Export: Request a portable copy of your data via support.
- Analytics: If your browser sends a Global Privacy Control or Do Not Track signal, Lykke doesn't load product analytics or Google Analytics (Section 9). You can also ask us at hello@getlykke.com to delete the analytics data linked to your account.
- AI-assistant Learning Signals: Sharing is off by default. You can turn it on or off in MCP settings; turning it off removes your stored learning signals.
- Uninstall: Remove the Chrome extension at any time.
9. Cookies, Analytics and Do Not Track
- To keep you signed in: Lykke uses cookies and your browser's local storage for your sign-in and settings. The Chrome extension keeps its data in the extension's own storage.
- Product analytics (PostHog): how Lykke is used, such as the pages you open and the buttons and links you click, linked to your account when you're signed in, so we can improve Lykke. It can record the text of a button or link you click, but we don't send it the contents of your notes, files or chats.
- Website analytics (Google Analytics, through Firebase): pages visited, device and browser, and approximate location from your IP address, using Google cookies such as
_ga. Google processes it under its own terms. We don't use it for advertising. - No advertising: Lykke uses no advertising cookies or pixels, doesn't sell personal information, and doesn't share it for targeted (cross-context behavioral) advertising.
- Global Privacy Control and Do Not Track: when your browser sends either signal, Lykke doesn't load PostHog or Google Analytics.
10. When We Share Information
We share personal information only:
- with the providers in Sections 4 to 6, which process it only to run Lykke for us;
- with people you choose: those you share a course or a snapshot with, everyone if you publish a course, and classmates in a synced Canvas class, who can see the course files synced into that class;
- with apps you connect, such as an AI assistant through our MCP server, to the extent you approve;
- with your school, only if you use Lykke under an agreement between your school and us (Section 11); and with the verified instructor of a Canvas course you sync, only as anonymized, grouped questions about that course (Section 2, Canvas Course Insights);
- when the law requires it, or to protect the safety, rights or property of our users, the public or Lykke;
- as part of a merger, acquisition or sale of assets, in which case we'll tell you before your information is covered by a different privacy policy; and
- otherwise, with your consent.
11. Students, Schools and FERPA
Most students use Lykke on their own. When you connect Canvas yourself, you choose to bring your own course information into your Lykke account, and we act for you, not for your school. We never ask for your Canvas password, and Lykke only reads Canvas: it never submits, posts or changes anything there. The one thing a course's instructor can see is the anonymized, grouped questions described under Canvas Course Insights (Section 2): never your name, your conversations or your files.
If your school makes Lykke available under an agreement with us, for example through its Canvas, we use the student information the school shares only to provide Lykke to its students, as that agreement and the Family Educational Rights and Privacy Act (FERPA) require. Where that agreement differs from this policy, the agreement controls.
We don't sell education records or student information, and we don't use them for advertising.
12. Children and Teens
Lykke is for students 13 and older. Students under 18 need a parent's or guardian's permission (see our Terms). We don't knowingly collect personal information from children under 13. If we learn that we have, we delete the account and its information.
Parents and guardians can ask about their child's information, or ask us to delete it, at hello@getlykke.com.
We don't sell teens' personal information or show them targeted advertising.
California residents under 18: you can ask us to remove content you posted publicly on Lykke, such as a public course, by writing to hello@getlykke.com. Removing it may not remove copies other people made, and the law has some exceptions.
13. Your Privacy Rights
Wherever you live, you can see and delete your information as described in Section 8, and ask us for a copy.
Depending on where you live, you may also have the right to know what personal information we hold about you, and to correct or delete it, get a portable copy, object to or restrict some uses, withdraw your consent, and opt out of the sale or sharing of personal information or targeted advertising (Lykke does neither). This includes California and other US states, the European Economic Area, the United Kingdom and Switzerland.
To use these rights, email hello@getlykke.com from the address on your account. We may need to confirm it's you. Someone you authorize can ask for you, with proof that you did. We'll answer within the time the law sets: 45 days in California, one month in the EEA and the UK. If we turn a request down, you can appeal by replying to our answer, and you can complain to your data protection authority or your state attorney general. Using these rights won't change how we treat you.
Legal bases (EEA, UK and Switzerland): we use personal information to provide the Service you asked for (contract), for our legitimate interests in running, securing and improving Lykke, with your consent for optional features such as connecting Google Calendar, Focus Mode's camera coach or MCP learning signals (you can withdraw it at any time), and to meet legal obligations.
Where your information goes: Lykke is run from the United States and stores data there (Section 3). If you use Lykke from another country, your information is transferred to, and processed in, the United States.
Additional Information
Data Retention
- Your notes, files, courses, chats and lesson recaps: until you delete them or your account.
- Your learning record: 180 days (Section 2).
- Canvas pages you study with Lykke: 30 days.
- MCP activity history: up to 30 days.
- What you tell an Ask Lykke chat (your classes, a test date): with that chat, and at most 180 days after you last use it.
- Course questions kept for instructors, without your name: up to 365 days.
- Answer quality samples: up to 30 days; their comparison results up to 90 days.
- Focus Mode verdicts: until you clear your focus history or delete your account.
- Google Calendar data: while it's connected (Section 5).
- Payment records: as long as tax and accounting laws require. Stripe keeps your card details.
Deleting an item removes it from our primary database right away and invalidates its embeddings. Encrypted backups may keep it for a limited time, until they expire. Inactive accounts (2+ years) may be flagged for deletion, with notice.
Security
HTTPS/TLS encryption, encrypted at rest, scoped access tokens, strict access controls, CSRF protection, and no plaintext password storage. No system is perfectly secure. If we learn that your personal information was accessed without authorization, we'll notify you, and the authorities where required, as the law requires.
Changes to This Policy
When we change this policy, we update the date at the top. If a change is material, we'll tell you by email or in the app before it takes effect.
Contact
Lykke Technologies Inc. · Privacy & Support: hello@getlykke.com
By using Lykke, you acknowledge that you have read and understood this Privacy Policy.
Lykke Technologies Inc.