Privacy Policy

Erkinov LLC operates Weekwell and is responsible for the account and service data described here. This policy covers weekwell.io and the Weekwell web application.

Contact availability: support@weekwell.io is available for account, service, privacy, cancellation, and refund correspondence. Written notices can also be addressed to the company mailing address below. Do not send passwords, full card numbers, API keys, or private calendar links.

• Account details: your name, email address, password hash, time zone, account identifiers, verification state, plan and trial dates, and settings. Passwords are stored as salted hashes, not readable passwords.
• Planning content: course names, codes and colors; assignment titles, due dates and times, requirements, source quotations, completion state, reminders, and in-app notifications.
• Import information: files or text you submit for processing, their filenames, extracted text used during processing, saved review candidates and corrections, and the source excerpts included with saved assignments.
• Optional integration data: the private LMS feed URL you supply, provider and host, previewed event content, course mappings, sync state, and, for Google Calendar, authorization tokens, the app-created calendar identifier and managed-event identifiers.
• Technical information: connection details such as IP address and browser request information received by our server, session tokens, and operational or error records used to deliver and protect the service.
• Support information: the contact details and information you send with an inquiry. Do not send passwords or private calendar feed links.
• Prepared billing records: recurring-charge consent and policy snapshots, account and checkout references, payment and subscription identifiers, prices and periods, cancellation/refund/withdrawal notices, their timestamps, decisions, provider statuses, and downloadable receipts. No paid purchase is created merely by registration.

Weekwell is not currently accepting subscription payments and does not collect card details through an active checkout.

The following identifies our purposes and, where the GDPR applies, the corresponding legal bases. Website availability alone does not determine which law applies.

• Account and planning service: account details, sign-in sessions, settings, courses, assignments, completion state, and reminders provide and maintain the service you request. The basis is performance of our contract with you where the processing is necessary for that service.
• Requested imports and connections: submitted material produces an import review; integration data performs the optional connection you choose. The basis is performance of the requested service where necessary. OAuth permission is also a technical authorization; it is not treated as a universal legal consent for unrelated uses. You can stop connections as described below.
• Security and reliability: limited connection, session, and error records authenticate users, investigate failures, prevent abuse, and protect accounts. The basis is our legitimate interest in a secure, reliable service, subject to the applicable balancing of your rights. This does not justify unrelated advertising or model training.
• Requests and correspondence: the details you provide answer a service request or verify and fulfil a privacy request. The basis is performance of the service contract, an applicable legal obligation, or the legitimate interest in handling other correspondence, depending on the request.
• Legal requirements and claims: specific records meet an applicable legal obligation or establish, exercise, or defend a legal claim. A legal obligation is the basis when law requires the processing; an appropriate legitimate interest may apply to handling a claim.
• Separate consent: if a use relies on consent, it is identified when consent is requested. You may withdraw that consent without affecting earlier lawful processing. Acceptance of this policy is not inferred consent to a new purpose.

Information necessary for a feature must be supplied to use it. You can avoid optional document processing or connections by entering assignments manually. Do not submit unnecessary information about other people or material you lack lawful authority to share. Weekwell does not make decisions with legal or similarly significant effects about you.

Requested AI import sends document text through OpenRouter to the Azure Sweden Central endpoint for OpenAI GPT-4.1 mini. Photos and locally rendered PDF page images are sent for model-based transcription, followed by separate assignment extraction. PDFs needing OCR are rendered into bounded images on the Weekwell server; the current route does not send the original PDF to an external file-parser or Mistral OCR plugin. Unsupported or oversized scans are rejected for a clearer or smaller upload. OCR results require your review before assignments are saved.

Uploads can contain names, contact details, or academic information. Remove information unnecessary for extracting assignments. Do not submit health, biometric, financial, government-identifier, or other sensitive personal information through document import. You can enter assignments manually.

Weekwell handles the binary upload during processing and does not save it as a downloadable file in its application database. It saves the filename, review candidates and corrections, source excerpts, and confirmed assignments. This describes Weekwell's storage, not outside-provider retention.

Inference routing controls and their limits: model requests require OpenRouter's data_collection: deny and zdr: true filters and are restricted to the reviewed azure/swedencentral endpoint, with provider fallback disabled. The application rejects external file-parser plugins, tools, presets, and remote image URLs. On 27 October 2026, the service key was matched to its OpenRouter workspace; input/output logging and permission for OpenRouter product-improvement use were off, training-enabled routes were excluded, and account ZDR for the OpenAI model group was on. Synthetic scan and photo imports succeeded through Azure with these controls. Weekwell sends no response-cache enabling header or preset. These controls follow OpenRouter's routing rules and ZDR scope; they do not promise no operational metadata, transient provider prompt caching, necessary security or malicious-use handling, legally required processing, or EU-only processing. Provider representations and settings require ongoing review.

We recorded the existing commercial OpenRouter account as used for Weekwell on behalf of Erkinov LLC. OpenRouter's standard Terms incorporate its DPA for commercial use. This records the contracting route and checked controls, rather than certifying every upstream resource or legal exception. Removing the former OCR plugin does not itself delete any information previously processed through that path; historical provider copies, where relevant, require separate assessment.

If you connect Canvas, Blackboard, D2L / Brightspace, or Moodle, Weekwell requests the subscription URL you provide and reads the calendar items your school publishes there. The feed may contain assignments, meetings, descriptions, and other events. The preview lets you choose what to import.

A private feed URL is a credential. It is stored encrypted for periodic updates, is not displayed in the connection list, and is removed from the active connection when you disconnect. The provider/host, sync metadata, and tasks already imported remain. Disconnecting Weekwell does not revoke the source URL at your school; regenerate it there if it has been disclosed.

With your authorization, Weekwell requests only calendar.app.created. It creates a separate Weekwell calendar and sends your active-course assignment titles, course labels, requirements, deadlines, time zone, and completion state to Google as managed events. It reads those managed events to avoid duplicates and update or remove them when you change the corresponding assignments. It does not read your primary or other unrelated personal calendars.

Authorization credentials are stored encrypted on the server together with calendar and event identifiers and sync state. Google connection credentials and Google-managed event responses are not sent to OpenRouter for document extraction. Sync is one-way from Weekwell; edits in Google do not become Weekwell assignments.

Weekwell's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. Google user data is used for the visible calendar connection, not for advertising, sale, or training general-purpose AI models. Human access is limited to your specific permission, necessary security investigations, legal requirements, or the limited internal uses allowed by that policy.

Disconnect in Settings → Connections to stop syncing and erase Weekwell's stored connection credentials. Weekwell also attempts to revoke the Google token. You can independently revoke access in your Google Account's connections settings. The calendar and events already in Google remain until you remove them there. An expired trial pauses sync and preserves the connection; it does not disconnect it.

Weekwell's application server and database are hosted with Friendhosting LTD in the Netherlands, according to the hosting order confirmed by the operator. The server also stores database backups and processes website requests. This server location does not establish where every external provider processes information. OpenRouter and the selected Azure inference endpoint process requested imports. Google processes calendar content you authorize us to send. Your institution or LMS provider receives requests for a connected private feed.

Resend is supported by the application, but outbound account and reminder email is disabled. Enabling it would transmit the recipient address and message content to Resend.

Stripe: payment collection is disabled

The prepared Stripe-hosted checkout integration sends the selected price or plan, your email or existing Stripe customer identifier, and an internal Weekwell account identifier associating the order and subscription. A user opening an enabled Stripe checkout would provide payment and required billing/contact information to Stripe; Stripe also receives browser, IP, and transaction information through its interface.

The prepared billing records store recurring-charge consent text and policy snapshots, their version and acceptance time, account and checkout references, Stripe customer and subscription identifiers, subscription and payment status, payment amounts and dates, cancellation and refund or withdrawal requests, operator decisions, provider outcomes, and event identifiers used to update access. Transaction, receipt, refund, and limited payment-method information may also be available in our Stripe business account when handling a payment issue. Card entry in the prepared flow is hosted by Stripe; this does not mean that Weekwell receives no payment-related information.

These uses concern processing orders, administering subscriptions and refunds, preventing fraud, and meeting applicable financial obligations. Necessary order processing is based on contract performance; legal obligations and appropriate fraud-prevention interests apply to relevant additional processing. Stripe acts as a processor or an independent controller depending on the operation; see Stripe's Privacy Policy. These disclosures describe a separately purchased paid service and do not claim payment collection is currently enabled.

International processing and safeguards

Although the application server is in the Netherlands, OpenRouter is a US company and its inference path, Google infrastructure, and other providers can process information outside your country or the EEA. We do not promise EU/EEA-only processing.

A transfer covered by GDPR restrictions requires an applicable adequacy decision or appropriate safeguards, such as the European Commission's Standard Contractual Clauses and necessary additional measures. OpenRouter's published DPA includes a mechanism for those clauses where applicable. The standard commercial OpenRouter agreement and relevant account controls were checked as described in section 4. Hosting processing terms and all onward arrangements have not yet been fully verified. Where GDPR applies, necessary safeguards concern current free processing as well as any future paid service; we do not claim every recipient's safeguards have been confirmed. Use section 11 to request the provider and safeguard information relevant to your data. Acceptance of this policy is not treated as consent replacing a required transfer safeguard.

Specific information may also be disclosed where necessary to meet a valid legal requirement, investigate abuse or a security incident, or handle a legal claim. Google-derived information remains subject to section 6.

Weekwell uses an essential weekwell_session cookie to keep you signed in. It expires after 30 days unless cleared or replaced earlier. Signing out ends the current server session. Production cookies are marked Secure, HttpOnly, and SameSite=Lax. Your browser may also retain interface preferences when that feature is provided.

The reviewed Weekwell application does not include advertising pixels or a third-party analytics SDK. Essential service requests and server operation can still generate technical records. Blocking the sign-in cookie prevents the account features from working.

The following periods and rotation criteria describe this release, rather than promising immediate erasure from every system.

• Accounts and planner content: remain while the account exists until the relevant content is deleted or an account-deletion request is completed. Inactive accounts are not automatically removed. There is no self-service account-deletion button. Settings → Profile → Download account data provides a JSON copy of current application account records, including archived work, saved reviews, notification history, integration metadata and billing evidence. Passwords, authentication/connection credentials, backup copies, operational logs and records held by outside providers or correspondence channels are excluded; the file explains its scope. The separate .ics export contains assignment deadlines. A broader access request may therefore require additional operator work.
• Import reviews: unconfirmed reviews expire after seven days and are removed by scheduled cleanup. Confirmed reviews, excerpts, corrections, and confirmation snapshots have no separate automatic expiry. Deleting an assignment does not erase its earlier copy in a confirmed review. Deleting a course removes its tasks and associated file-import reviews from the active database.
• Integration and notification history: LMS previews expire after 30 minutes and Google authorization state after 10 minutes. Disconnection removes active credentials as described above. Imported assignments, some synchronization/deletion markers containing source snapshots, and notification text can remain after a task or course is removed. These historical records and old notifications do not currently have an automatic age-based purge.
• Sessions and tokens: sessions expire after 30 days, password-reset tokens after one hour, and verification tokens after 24 hours. Scheduled cleanup removes expired records. Signing out invalidates the current session. A protected service restart changes an independent authentication secret, invalidating existing sessions and previously issued password-reset and verification links; you may need to sign in or request a new link after maintenance.
• Backups: database recovery copies have a 30-day age limit, including recognized pre-deployment database copies. The daily backup process also keeps no more than the 14 most recent successfully checked daily copies; fourteen copies are not fourteen calendar days. Expiry is checked daily and eligible copies are removed by the next successful sweep. Unsafe, damaged, or unrecognized copies require operator review rather than silent deletion; failed cleanup must be investigated. This rule covers database copies, while configuration and other rollback artifacts require separate assessment. Deleting live content does not immediately remove earlier backup bytes. Before a restored copy returns to service, the operator must apply recorded account erasures and verify the sanitized copy through the separate controlled restore process.
• Operational logs: dedicated Weekwell web-server request/error logs are rotated daily with a 30-day age limit. The application does not maintain a separate API access log. New output from the Weekwell application, backup, and retention services is routed to an isolated Weekwell journal configured for 30-day retention. Scheduled rotation and expiry checks require monitoring and successful execution. These scoped settings do not erase all shared host history: earlier Weekwell entries already in the shared journal cannot be selectively removed by service name, and the host service manager's start/stop/failure metadata and other infrastructure or security records can remain there. Their treatment requires a separate assessment with the host operator; changing the whole host's retention would also affect other services. We do not claim that every historical or host-level log has been purged.
• Billing records: consent, payment, invoice-evidence, cancellation, refund, withdrawal, decision, and provider-result records and receipts support subscription administration, evidence of agreements, dispute handling, and applicable obligations. Receipts and consent snapshots are protected against ordinary modification or deletion; this protection does not itself justify indefinite retention. An exception to erasure requires an individual assessment of the records still needed, with a documented basis, scope, and review date. These records do not automatically inherit the 30-day backup/log period or the 12-month correspondence period. There is no automatic age-based billing purge, and no single period is presented as applying to every legal obligation or claim. We do not promise immediate erasure of all billing evidence.
• Correspondence: the approved handling rule is to retain support correspondence for 12 calendar months from closure. An open request remains available while it is being handled. A particular record may be kept longer for an applicable legal obligation or unresolved dispute only under an individually documented retention basis and review date; a review date is not an automatic removal of that exception. Support correspondence is received at support@weekwell.io and remains in the mailbox or channel used to handle the request. A general in-app support-ticket database is not configured. Correspondence received through another working channel remains in that channel and must be handled under this rule by the responsible operator, including any separate provider copies or holds. Automated cleanup of an external mailbox or every correspondence channel is not claimed. A refund response target is separate from this retention period.

Use the contact details below for account deletion, an access request beyond the application download, or assistance with residual records. The prepared operator process records a verified request, an individually assessed deadline and decision, clears ordinary account content including residual reviews/notifications/sync records, and separates any assessed billing-retention exception. Its restricted erasure ledger is bound to a separate root-owned authority, with an off-server witness retaining a monotonic record of acknowledged history. Before local account erasure, the recorded intent requires a fresh witness acknowledgement. Controlled recovery verifies a creation-time signed backup from this installation, clears restored credentials and pending external work, reapplies erasures, and requires a fresh witness approval for the exact prepared copy before promotion. The installed startup guard checks the current acknowledged ledger, authorized database identity and erased-account invariants. These checks do not activate a support inbox, verify the requester's ownership or erase outside-provider copies. They protect the documented stopped-service recovery route; they do not automatically detect every privileged in-place change while the application is running or an internally consistent rollback of the entire host and its authority. Such incidents require an independent comparison with the off-server witness and operator investigation before service resumes. Completion is recorded only after the responsible operator has assessed all relevant scopes and the response. Proportionate ownership verification may be required. Necessary legal/security exceptions and third-party copies are assessed separately. Disconnecting Google does not erase its calendar, and removing an LMS connection does not erase your institution's records.

We use HTTPS, salted password hashes, restricted server access, and encryption for integration credentials. No online service can guarantee absolute security. Avoid unnecessary sensitive information and keep passwords and private calendar links secure.

You can edit your name and time zone, correct planning content, change reminders, disconnect integrations, delete planner items, export deadlines as .ics, and download current application account records as JSON in Settings → Profile. Section 9 explains the limits of deletion and export.

Where GDPR applies, rights may include access, rectification, erasure, restriction, objection, portability where applicable, and withdrawal of consent for a use actually based on consent. A legitimate-interest use can be challenged on grounds relating to your situation. You may complain to the relevant data-protection authority, including the authority in your habitual residence, place of work, or alleged infringement where applicable. Other laws may provide further rights. Requests are handled under the applicable law; a voluntary support target does not replace a statutory deadline.

Use section 11 for an account or privacy request. Weekwell is not directed to children under 13. Contact us if you believe a child supplied information without required authorization so the issue can be reviewed.

We show a new revision date when this policy changes and give additional notice of material changes when required. A new use of Google user data requires the applicable disclosures and authorization.

For account, service, privacy, cancellation, or refund correspondence, identify your Weekwell account email and describe the request.

Contact availability: support@weekwell.io is available for account, service, privacy, cancellation, and refund correspondence. Written notices can also be addressed to the company mailing address below. Do not send passwords, full card numbers, API keys, or private calendar links.