All articles

News 2026-07-13 1 min read

Testar

Testar att ange en ingress

By Tobias

Updated 2026-07-15

Testar brödtext

asdasd

Alt-text — Bildtext Photo: Tobias · © Jonson · Copyright- eller licenstext

Blutter blutter blutter.

DEBUG

Request ID
7RRU2JMT1AKN92PR-V2PPKH7M4K4JRPDD-Y5CV0P795EXKC4C0-URWYXAR55C0FV4DU

Analytics ID
3X9X0WVVCPNFPC4X-6UW4D9J7UNC55FNM-NENAUTNMW68KHV4V-V0PNMPKRFAH46R9W

Session policy


                            idle=7200s,
                            absolute=86400s,
                            php_gc=86400s

Session
4e274c11…

Environment
dev

Version
0.0.0

Random: 2
1D

Random: 4
YUA5

Random: 8
H5Y8UF86

Random: 16
06XKJ2D6MMAYDXD8

Random: 32
MFA2R5R8JYEV4EWAV3KMA31KTWWFAY2M

{
    "csrf_token": "[redacted]"
}

[]

Privacy policy

Last updated: 2026-06-01

Before production: Configure LEGAL_* environment variables so contact details in sections 2–3 are complete. Sections referencing the data model reflect tables installed via InstallDb.php.

1. Introduction

This privacy policy describes how ArcWind AB processes personal data when you use our websites, applications and APIs.

We process personal data in accordance with the General Data Protection Regulation (EU) 2016/679 (GDPR) and applicable Swedish legislation.

If you are aged 9–12

You may use the service from age 9, but a parent or legal guardian must first approve the account through their own email address. We use your date of birth to apply the right protections. We do not send you marketing, load PostHog while you are signed in, or show automatic push onboarding. You or your guardian can contact hello@arcwind.se with questions or to request correction, withdraw consent or delete the account. Never enter someone else's email address without permission.

2. Data controller

Organisation: ArcWind AB Organisation number: 559287-4894 Address: ArcWind AB, Box 152, 116 74 Stockholm, Sweden Email: hello@arcwind.se Phone: +46 8 - 121 486 70

3. Contact and data protection

Privacy enquiries: hello@arcwind.se

Data protection officer (if applicable):

4. Categories of personal data (data model)

Identity and account data (`users`)

Name
Username
Email address
Alternative usernames and email addresses
Alternative phone numbers
Verification status, hashed verification tokens and expiry times for alternative email addresses
Phone number (optional)
Date of birth (required for self-service signup for age assurance)
Password (hashed only)
MFA settings and metadata (TOTP secret stored encrypted)
Roles and permissions
Administrative labels
Internal administrator comments about the account
Last sign-in time

Parent or guardian consent (`guardian_consents`)

For users aged 9–12: the parent or legal guardian's email address
Time of verified consent to the terms and necessary personal data processing
Verification method and any withdrawal time
The one-time code is only stored as a hash in the short-lived signup session and is not retained in the consent record

Session and security data (`user_sessions`, `audit_logs`)

IP address
Browser / user agent
Session timestamps (created, last activity, revoked)
Audit log entries (action, time, actor)

Session secrets (session_id) are stored internally for operations but are never included in data exports.

Authentication data (`auth_otps`, `mfa_recovery_codes`)

OTP codes (hashed) for email/SMS sign-in and account creation
MFA recovery codes (hashed)

Email preferences (`email_preferences`)

Email address
Marketing consent and unsubscribe token

Orbit Life and Hub data (`orbit_lives`, `orbit_hubs`, `orbit_hub_memberships`, `orbit_sharing_scopes`)

Life profile linked to the user account
Display name, language, timezone and accessibility profile for the Life
Hubs the user creates or participates in
Hub name, Hub type and membership role/status
Sharing settings that define which information categories a Life shares to a Hub
Calendar links to Hubs and the choices controlling whether title and location may be shown; the default is time/busy status only
Hub invitations with recipient account, role and status; an exact username or email is used only to locate the recipient account
Hub invitations are disabled for guardian-protected accounts pending renewed product and legal review
Encrypted title and description for Hub activities and chores, plus start/end, status, assigned members, dependencies and recurrence interval
Fingerprint/hash for external sources when a sharing scope needs to reference a calendar, task list or other resource

Optional calendar import and synchronization (`orbit_calendar_connections`, `orbit_calendars`, `orbit_calendar_events`)

Google OAuth refresh tokens, calendar identifiers, iCal subscription URLs and synchronization markers are stored encrypted
Uploaded iCalendar files (.ics) are stored temporarily in encrypted form while the import job is waiting and deleted after a successful import
iCal subscriptions are fetched repeatedly from the HTTPS URL provided by the user; the source server then receives a technical HTTP request from the service
The user explicitly selects which calendars may sync and chooses their names in Orbit
Selected calendars store the event's encrypted title and optional location, plus start, end, all-day flag and status
Description, attendees, attachments, meeting links and Google profile data are not stored
The integrations are read-only and cannot change or delete data in the source calendar
External calendars and file imports are disabled for guardian-protected accounts aged 9–12 in this version
Disconnecting removes the connection, selected calendars and the local event cache

Personal habits (`orbit_habits`, `orbit_habit_completions`)

Goal name, color, recurrence schedule, start date, target count and whether a streak is shown
Completion dates and counts used to render the monthly calendar and calculate streaks
This information is private to the account and is not shared with Hubs, guardians, analytics or advertising providers
Luma in the getting-started state is guidance copy in the interface; goals are not sent to an external AI service

Shared costs and other amounts between people (`orbit_hub_expenses`, `orbit_hub_expense_shares`, `orbit_hub_expense_settlements`, `orbit_debts`)

Hubs store an encrypted expense title, amount in the currency's minor unit, currency, date, paying member, participant shares and payments made outside Orbit
Amounts a Hub member needs to pay or receive are combined with expenses and recorded payments
Personal entries store the counterparty name encrypted plus whether the user needs to pay or receive, amount, currency and date; a keyed hash is used only to combine entries for the same counterparty
Orbit does not transmit payments and stores no bank, card or account information for this feature
Hub entries are visible to active members of that Hub. Personal entries are private to the user
Registration is disabled for guardian-protected accounts

Messaging and call metadata

Delivery status for outbound email/SMS/push when those channels are used
Incoming SMS/MMS via 46 Elks may be stored for administrative follow-up with message text, from/to numbers and image links for MMS
Incoming calls via 46 Elks may create call logs with call id and from/to numbers; audit logs use short fingerprints instead of raw numbers

News and press content (`news_items`)

Public article metadata, publication dates and language variants
Optional author reference to a user account
Audit references to the administrator who created or last updated the article
Optional publication notification sent through the existing notification preference system
When an administrator explicitly chooses AI translation or improvement suggestions, the relevant article version and necessary language choices are sent to OpenAI; the API key remains server-side
AI-assisted language variants are marked in the database and shown with a public transparency notice

Editorial image library (`image_library_*`)

Only administrators with a dedicated permission can upload and manage library images; user uploads are not included
Originals are stored first and PNG/WebP variants are then created by a background job; all objects remain private under a random image identifier
Metadata may include title, caption, alternative text, photographer or creator, copyright, licence or consent evidence, marketing permission, AI origin and publication time limits
Focal point, folders and tags support editorial organisation and consistent cropping
The system records which editorial content uses a library image so rights and unpublishing can be followed up
Images with expired rights, revoked consent or a passed unpublish time are not served through the public image route; unknown rights remain visible as metadata but do not block the link

Cookie and preference data (browser)

Cookie choices and consent version
Language, theme and font size (after preferences consent)
Limited anonymous page-view statistics via PostHog (in-memory, before analytics consent)
Full analytics via PostHog (after analytics consent)
Push subscription via OneSignal (browser notification permission and choices under /me; not tied to marketing cookies)
Security verification via Cloudflare Turnstile during sign-in and account creation when enabled

See the cookie policy for details.

5. Purposes and legal basis

Purpose	Legal basis
Provide the service	Contract
Account and access management	Contract
Orbit Life, Hub and sharing features	Contract
Personal habit tracker	Contract
Shared Hub costs and private amounts between people	Contract
Optional calendar import and read-only calendar synchronization	Consent
Age assurance and guardian consent for users aged 9–12	Contract, parent or guardian consent and legal obligation
Information security and audit	Legitimate interest / Legal obligation
Operations, monitoring and troubleshooting	Legitimate interest
Limited anonymous web analytics (PostHog, in-memory)	Legitimate interest
Extended analytics and product statistics (PostHog)	Consent
Push notifications (OneSignal)	Consent (browser notification permission)
Marketing email	Consent
Incoming SMS/MMS follow-up (46 Elks)	Legitimate interest / Contract where enabled
Incoming call control (46 Elks)	Legitimate interest / Contract

6. Logging and security

To maintain security, stability and traceability we may record:

Application logs
API logs
Security and audit logs (audit_logs)

Logs may include timestamps, IP addresses, user identifiers and technical error messages — not raw session IDs in exports or audit detail fields.

PHP and JavaScript errors may be sent to PostHog for operations and incident response regardless of cookie choices. A stack trace is always sent. Without analytics consent it is sanitized and other technical properties are anonymized; with consent, the error message, full stack trace, user agent and IP address may be included. Server errors may also be sent to MQTT under the organization's logging procedures.

For repeated production errors, the error message, file and line number may be sent to OneUptime regardless of cookie choices. These details are shown only internally in private alerts or internal incident notes. A public status page may show a generic incident description without error details.

Cloudflare Turnstile may be used during sign-in and account creation to distinguish legitimate users from automated abuse. When enabled, the verification token and technical data such as IP address are sent to Cloudflare for security verification.

7. Analytics and statistics

PostHog is not loaded for signed-in users aged 9–12. Marketing channels and automatic push onboarding are also disabled for these accounts.

PostHog may operate at two levels:

Before analytics consent: the SDK may load with in-memory persistence (memory) and pseudonymous $pageview events without a persistent profile or identifying cookies. The distinct id is derived from date and page path — not from account or email.

After analytics consent: full PostHog analytics with persistent storage (cookies/localStorage), $identify on sign-in and extended event properties as described in the cookie policy.

Data is stored in the configured PostHog instance (see the cookie policy for retention).

8. Automated decision-making

We do not use automated decision-making or profiling that produces legal or similarly significant effects for users.

9. Recipients of data

Personal data may be shared with:

Hosting and operations providers
Email provider (SMTP)
46 Elks (SMS and incoming call control when enabled)
Cloudflare Turnstile (sign-in and account creation security verification)
PostHog (analytics — in-memory before consent; full profile after analytics consent)
OneSignal (push, after browser notification permission)
Google Calendar (optional read-only synchronization after the user connects Google and selects calendars)
Stripe (hosted Checkout and subscription administration; payment-card details are sent directly to Stripe and never to Project Orbit)
OpenAI (only when an administrator chooses AI-assisted translation of public article content)
Authorities when required by law

10. Data processors

When external providers process personal data on our behalf, data processing agreements are entered into.

11. Transfers outside the EU/EEA

When data is transferred outside the EU/EEA, appropriate safeguards are used such as the EU Commission's Standard Contractual Clauses (SCC) or adequacy decisions.

12. Retention periods

Normal retention periods according to current service configuration (RETENTION_*) are listed below.

Data type	Normal retention
Account	While the account is active
Parent or guardian consent	While the child's account is active or until consent is withdrawn and the account has been handled
Orbit Life, Hub membership and sharing scope data	While the account, Life or Hub is active
Hub subscription references and status	While the Hub or subscription relationship exists; card details are not stored by Project Orbit
Google Calendar connection and selected calendars	Until the user disconnects Google or removes the calendar
iCal source and imported/subscribed calendar	Until the user removes the calendar; an uploaded original file is stored encrypted until the import succeeds or the calendar is removed
Locally cached calendar events	Normally 30 days in the past and 365 days in the future; older cache is removed by cron
Personal habits and completions	Until the user deletes the habit or the account
Expenses, shares and amounts to pay or receive	Until the entry, Hub or account is deleted; entries involving a deleted Hub member are removed
OTP codes (sign-in)	7 days
Used MFA recovery codes	90 days
Audit logs	365 days
Incoming SMS/MMS	30 days
Revoked sessions	90 days
Inactive sessions (auto-revoked after absolute timeout)	90 days after revocation
Rate-limit data (files)	7 days
Application logs (files)	30 days

After account deletion the user record is anonymized so audit logs retain traceability without remaining identifiable personal data.

13. Your rights

Under GDPR you have the right to access, rectification, erasure, restriction, objection, data portability and to withdraw consent.

Self-service (signed-in user on `/me`)

Right	How it is handled in the service
Access / portability	Export JSON via Export my data
Rectification	Update name, primary phone and alternative identifiers in your profile; date of birth is corrected manually after verification
Erasure	Delete my account (anonymizes the account and removes identifiable data)
Consent	Cookie settings in the footer or on `/cookies`

Manual handling

For rights requiring manual review — e.g. restriction of processing, objection, correction of email/username, or questions about audit logs — contact:

hello@arcwind.se

We respond within one month under GDPR unless an extension is communicated.

14. Complaints

You have the right to lodge a complaint with the Swedish Authority for Privacy Protection (IMY).

https://www.imy.se

15. Security measures

We use measures including:

Encryption
Access control and MFA
Logging and audit
Backups
Security updates

16. Changes

The latest version is always published on our website.

17. Contact

ArcWind AB ArcWind AB, Box 152, 116 74 Stockholm, Sweden hello@arcwind.se +46 8 - 121 486 70

Cookie policy

Last updated: 2026-06-01

1. What are cookies?

Cookies are small text files stored on your device when you visit a website or use a digital service. We also use similar technologies such as local storage (localStorage) and session storage when required for functionality or after consent.

2. How we use cookies

We use cookies and similar technologies to:

Provide core functionality
Manage sign-in and sessions
Improve security
Save your choices and settings (after consent)
Measure usage and performance (after consent)
Send push notifications (browser notification permission and choices under /me; not tied to marketing cookies)

3. Cookie categories

Necessary cookies

These are required for the site to work correctly and cannot be disabled.

Examples:

Session cookie (PHP session)
CSRF protection
Secure sign-in
Cloudflare Turnstile during sign-in and account creation when enabled

Functional cookies and preferences

Used to remember choices and settings after consent to the Preferences category.

Examples:

Language choice (session)
Theme (session and optionally localStorage)
Font size (session and optionally localStorage)

Analytics cookies

Used for extended web analytics after consent to the Analytics category.

Before analytics consent, the PostHog SDK may load with in-memory persistence and pseudonymous page views without persistent ph_* cookies. This provides limited aggregated statistics without a person profile.

Anonymized PHP and JavaScript error events may be sent without analytics consent for necessary operations and troubleshooting. A sanitized stack trace is always sent; error messages and user-identifying technical properties are sent to PostHog only after analytics consent.

After analytics consent, persistent storage (cookies/localStorage), identification on sign-in and full event collection apply as described in the table below.

Provider: PostHog (self-hosted or configured instance per environment).

Typical cookies/identifiers after consent: ph_*, PostHog distinct id and session data.

Marketing cookies

Optional marketing technologies and communications that require consent in the cookie banner.

Web push via OneSignal

Used for browser push notifications when OneSignal is enabled for the service. Not tied to marketing cookies in the cookie banner. The browser asks for notification permission when you subscribe on a device or on first login. Which topics are sent via push is controlled under Notification settings on /me.

Provider: OneSignal.

Typical technologies: service worker, push subscription, OneSignal device identifiers.

4. Cookie and storage table

Name / technology	Category	Purpose	Retention	Provider
`cookie_consent`	Necessary	Stores your cookie choices and consent version	365 days	ArcWind AB
PHP session (e.g. `PHPSESSID`)	Necessary	Keeps you signed in and manages a secure session	Session / until sign-out	ArcWind AB
`theme` (localStorage)	Preferences	Stores selected theme	Until you clear the browser	ArcWind AB
`font_size` (localStorage)	Preferences	Stores selected font size	Until you clear the browser	ArcWind AB
PostHog (`ph_*` etc.)	Analytics	Extended statistics and product improvement (after consent)	90 days (PostHog project)	PostHog
PostHog (in-memory)	Necessary / operations	Limited pseudonymous page views before analytics consent	Session (memory)	PostHog
OneSignal push	Web push (browser)	Push after browser notification permission and choices under `/me`	365 days or until subscription ends	OneSignal
Cloudflare Turnstile	Necessary / security	Protects sign-in and account creation against automated abuse when enabled	According to Cloudflare's security verification	Cloudflare

This table reflects the actual implementation in this service. Third-party providers may update their cookie names; refer to each provider's documentation when needed.

5. Third-party services

The following services may process data via cookies or similar technologies:

Service	Category	Purpose
Cloudflare Turnstile	Necessary / security	Protect sign-in and account creation against automated abuse
PostHog	Analytics	Usage statistics and troubleshooting
OneSignal	Web push	Push (browser notification permission and choices under `/me`)

6. Consent

Where legislation requires consent, optional cookies or equivalent storage are not placed until you approve them in the cookie banner.

You can change or withdraw consent at any time via Cookie settings in the footer or on the cookies page.

7. Managing cookies

Most browsers let you:

View stored cookies
Delete cookies
Block cookies
Restrict third-party cookies

Note that some features may stop working if cookies are blocked.

8. Contact

ArcWind AB hello@arcwind.se +46 8 - 121 486 70