Version 2026-11-14 · Effective
1. Who is responsible and how to contact us
ALSTER is a cultural publishing and community platform operated from Sweden. The service is operated personally by Johan Rosenberg, who is responsible for personal-data processing and privacy requests. ALSTER is the service name.
- Legal controller
- Johan Rosenberg
- Postal contact address
- Manillagatan 29 lgh 1204 702 12 Örebro Sweden
- Privacy requests
- hello@alster.me
You may contact us by email or post to ask questions or exercise your rights. You do not need to accept new Terms or allow analytics to make a privacy request.
2. Information we receive and generate
You provide account details such as your name, email and password; optional profile information such as your portrait, presentation, occupation, country, websites and work availability; and the posts, images, comments, messages, job offers and collaboration information you choose to submit.
We generate account and content identifiers, handles, timestamps, verification and security records, Terms acceptance version and time, follows, votes, presence information and notifications. New registration requires a separate minimum-age self-declaration linked to the accepted Terms version and server-recorded acceptance time. No birth date or identity document is collected by that age confirmation. Sessions can contain your IP address and browser information. Server and application logs may contain technical request and error information.
If you choose an available social sign-in provider, we receive identity information such as its account identifier, name and email where supplied. Linked provider identifiers are stored for sign-in; the linked-account record does not store provider access tokens. We do not automatically merge accounts just because email addresses match.
Other members may provide information about you through messages, posts, invitations, comments or credits, including external credits for people without ALSTER accounts. This information comes from the member who supplies it, not necessarily from you. Its visibility follows the relevant post or communication. You can contact us to request access, correction, removal or information about its source even if you do not have an ALSTER account. A credit does not establish that a non-member has agreed to join ALSTER.
Please avoid sharing sensitive information about yourself or others unnecessarily. Health, political, religious and similar information can require additional legal protection. Publishing it voluntarily does not remove all of our responsibilities.
3. Why we process information
We use information to operate accounts and sign-in; provide publishing, profiles, discovery, communications and collaboration; deliver service notifications; prevent abuse and secure the platform; handle requests and disputes; and, if you allow it, measure public-page visits.
- Account and requested services — contract, Article 6(1)(b) GDPR: information necessary to create and secure your account, verify your email, provide the publishing and profile features you request, deliver your messages and carry out requested collaboration and job-offer workflows.
- Security and moderation — legitimate interests, Article 6(1)(f): proportionate logging, abuse prevention, incident investigation and moderation to protect members, the service and other people's rights.
- Community discovery and attribution — legitimate interests, Article 6(1)(f): presenting publicly shared work, ranking it using community activity, showing enabled online status and maintaining accurate creative credits, including information supplied about non-members. The interests are helping people discover creative work, enabling contact and attributing contributions. We limit this to relevant information, apply visibility and blocking rules, and provide profile editing, an online-status opt-out and a right to object. This does not permit unrelated advertising or unrestricted reuse.
- Optional visitor analytics — consent, Article 6(1)(a): collection starts only after your separate choice. Refusal does not prevent use of ALSTER; you can withdraw at any time through Privacy choices.
- Privacy requests and binding duties — legal obligation, Article 6(1)(c): records necessary to fulfil GDPR rights requests and applicable data-protection duties. Where necessary, limited dispute records are kept to establish, exercise or defend legal claims under Article 6(1)(f).
We do not make decisions with legal or similarly significant effects solely by automated processing. Discovery ranking is used to present community content. Accepting our Terms is not consent to optional analytics or unrelated processing. Do not submit sensitive personal information about others without a valid basis; we assess requests and complaints involving sensitive information individually.
Account details and any verification needed for a feature are required to use that feature. Optional profile fields and analytics are not required to register. Without information needed for a requested service, we may be unable to provide it.
4. Public information and discovery
Public profiles, Spaces, published posts, comments and credits may be visible to visitors and appear in search, discovery, recent activity and public sharing previews. Follows and upvotes may be shown through community features. Your account email is not a public profile field.
Only publish information you intend to share with that audience, and obtain any permissions needed for other people's information. Public information can be indexed, copied or cached by search engines and other people. Removing it from ALSTER does not automatically remove those independent copies.
Drafts and restricted content use the application's access rules. Do not treat a public profile as private storage. Profile settings let you edit optional details and work availability. Online status is enabled by default; verified members can see recent activity when it is enabled. You can turn it off in Profile settings. Blocking restricts relevant contact and presence features but cannot recall information already seen or copied.
5. Private Chat and communications
We store Chat messages and conversation records to provide communication between members. Normal Chat access is restricted to authorized participants. Blocking prevents further messaging under the application's safety rules.
Chat is not end-to-end encrypted. Infrastructure administrators and people with authorized database or backup access may technically access stored messages. We do not promise that every stored record is encrypted.
No general automatic Chat expiry is currently implemented. Under the current account-deletion behavior, deleting either participant's account also deletes their shared conversation and its messages from the active database. Backups may retain earlier copies. Conversation records remain while the participating accounts and conversation exist, subject to valid removal requests, applicable duties and the rights of both participants. Keep an independent copy of information you need before deleting your account.
In-app notifications communicate community and workflow activity. Verification emails and other configured service mail are sent through the email delivery service. We do not offer a general self-service Chat or account-data export at present; contact us for a privacy request.
6. Images and uploaded media
New image uploads are processed and re-encoded, with orientation and colour handling, metadata removal and responsive versions where applicable. The standard maximum stored image dimension is 2272 pixels on the longest side; administrators can configure processing limits. Smaller images are not upscaled. Avatars use separate cropping and sizing.
The normal image pipeline stores processed images rather than retaining the full-resolution original by default. Temporary processing files are cleaned up, and abandoned upload cleanup is scheduled. We have not verified that all historical or imported images are free of EXIF or GPS metadata.
Uploaded media is served according to the associated content's visibility and access rules. Removing an image or content can queue deletion of its stored files and responsive versions. Cleanup failures can delay removal and require retry. Backups and independent public copies are separate.
7. Cookies, preferences and optional analytics
Authentication, sessions, security and sign-in flows use necessary browser storage. A remember-me choice can extend sign-in. Appearance preferences may be stored in your browser. The configured ordinary session idle lifetime is 120 minutes; a remember-me cookie can last longer. Necessary storage is separate from optional analytics. Browser settings can remove cookies, although doing so may sign you out or reset preferences.
Optional first-party analytics records public page keys, UTC days, a keyed hash of a random browser identifier, navigation identifiers for deduplication and new/returning classification. It does not store IP addresses, user agents, account IDs, private messages, search terms or URL queries in analytics events. This does not mean that separate sessions or security logs never contain IP addresses.
The analytics choice cookie lasts up to 180 days. Only after allowance, a random visitor cookie lasts up to 30 days. Configured retention is 7 UTC calendar days for raw visits, 30 days of inactivity for visitor records and 90 days for daily aggregates. Cleanup is performed by a scheduled aggregation task; a failed or delayed task can delay deletion and is an operational issue requiring recovery.
Declining analytics does not limit the service. Do Not Track and Global Privacy Control signals exclude collection. Withdrawal removes the current browser's visitor cookie and associated raw visit and visitor records. Historical aggregate counts may remain; the recent mutable window is rebuilt by the next aggregation. This is not an account-wide deletion across all browsers.
Use Privacy choices in the account menu, the guest privacy control, or the analytics privacy and choices page to allow, decline or withdraw. Administrative community totals also use existing operational records without the optional visitor cookie. Those statistics are restricted to authorized administrators.
8. Service providers and external media
ALSTER uses Webdock.io ApS for hosting and Brevo for service email. The ALSTER server is located in Denmark and application media is stored on that server. Webdock also keeps server snapshots on separate backup infrastructure. The separate backup/cold-storage country has not been independently confirmed; the server's Danish location does not establish the location of every backup.
Brevo receives email addresses and message contents needed to deliver verification and other service messages. Brevo describes EU database hosting in France, Germany and Belgium. Its agreement provides for international processing and contractual safeguards, including standard contractual clauses where applicable. Webdock's supplied agreement describes support access to servers and backups, when necessary for support or incidents, by staff in India, Malaysia and Colombia. EU hosting is therefore not a promise that all access occurs in the EU/EEA.
Hosting and email suppliers process service data for ALSTER. The precise account-level execution status of the supplied Webdock DPA and the complete backup/transfer arrangements remain unconfirmed; we do not represent that this notice establishes those safeguards. Contact hello@alster.me for available agreement and safeguard information or to request a copy, subject to appropriate redaction. These operational uncertainties require follow-up and are not resolved by accepting Terms.
Google sign-in is available where configured. An external sign-in service receives your sign-in request and provides the identity details described above. Social sign-in and embedded-media providers also process information under their own privacy notices, which may include processing outside the EU/EEA. You can instead use email/password sign-in and leave external players unloaded. Other social integrations may be disabled.
YouTube and Vimeo use server-fetched cached previews before activation; the thumbnail service sees the server request and video reference. Activating a player makes your browser contact its provider. SoundCloud, Mixcloud, Spotify and Apple Music show a local Load player button before any player iframe is loaded, including in full posts and Space listings. Loading one player does not automatically load the others.
External services may receive your IP address, browser information, origin/referrer information and the requested media identifier, and may use their own cookies or storage. ALSTER's analytics choice does not control those providers. You can leave players unloaded and follow an external source link instead. An activation choice does not guarantee that all subsequent provider processing is consent-free or resolve age-related requirements.
External links contact the destination when followed. If enabled and activated, radio uses the selected stream service or The Lot Radio controls supplied through radio.menu. It may contact further services needed to play the stream. We do not load these controls before activation. Providers may process data for their own purposes; their availability does not mean they are endorsed by ALSTER. Ask us for information about a provider used by a specific post.
9. Retention, deletion and backups
Account information normally remains while the account exists. You can correct profile information and manage content using the available settings and permissions. Account deletion exists, but provider-only members may need to establish a password first under the current flow; contact us if you cannot use it. A Platform Owner must transfer ownership before deleting that account.
Deleting an account removes its active account record and cascades through owned Spaces and several related records. Posts authored in another person's Space, attribution names embedded in their posts and some operational records can require separate review. Deleting an account is not a promise to erase every reference immediately. We must consider applicable legal duties, freedom of expression and other people's rights when handling a request.
Deleted Spaces have a 30-day recovery period before scheduled permanent cleanup. Media deletion can require queued retries. Chat behavior is described above. The operator has approved targets of 30 days for ordinary logs and failed queue jobs, 90 days for resolved ordinary notifications and a maximum of 30 days for ordinary backups. Automatic operational cleanup requires separate activation; until it is activated, these are retention targets rather than a verified automatic deletion schedule. Unresolved workflows and records subject to specific preservation requirements are excluded. The actual log rotation and all backup destinations still need operational verification. Administrative, moderation and privacy-request records are retained while the matter is open and afterwards only where needed to fulfil a specific duty or handle a relevant dispute, with case-by-case review; they are not retained indefinitely merely because an account once existed. Brevo transactional delivery logs are configured for one month and new email previews are not stored.
Backups may include the database, uploaded media and operational configuration. Separate backup destinations, encryption and expiry still require verification. Webdock's automatic snapshots rotate through two daily copies and up to three weekly copies; manual/protected snapshots can be retained longer if created. Deletion from the active application does not immediately remove older backup copies. Backups are for restricted recovery use. After restoring an older copy, approved erasures must be reapplied before normal use resumes. Contact us about any outstanding deletion request or backup copy.
10. Your rights and privacy requests
Depending on the circumstances, you can request access to your personal data, correction, erasure, restriction, portability where applicable, or object to processing, particularly processing based on legitimate interests. You can withdraw consent where it is used without affecting the lawfulness of processing before withdrawal. These rights have conditions and exceptions; other people's rights must also be protected.
Email hello@alster.me with the right you want to exercise and enough information to identify your account or the information concerned. Do not send your password, verification links or unnecessary identity documents. We may ask for proportionate additional information if reasonably needed to verify identity. Requests are handled manually; no general self-service data download is promised.
We will respond without undue delay, normally within one month of receiving a request. If a permitted extension is needed because of complexity or the number of requests, we will explain it and the reasons within the first month. Requests are normally free; any legally permitted exception must be explained.
You can complain to Integritetsskyddsmyndigheten (IMY), Sweden's supervisory authority, or another competent supervisory authority. You do not have to contact us first.
11. Security
ALSTER uses password hashing, email verification, sign-in throttling, authorization checks and validated uploads. Administrator permissions restrict sensitive application functions. These measures reduce risk but cannot guarantee absolute security. Do not assume that all stored records or backup copies are encrypted. We investigate reported security incidents and take any notification or other action required by applicable law.
12. Age eligibility and policy updates
ALSTER accounts are restricted to people aged 18 and over. The registration checkbox is a self-declaration, not verified age. Existing members are not retrospectively recorded as having made this declaration. If you believe an account is used by a child, contact the privacy address for a proportionate review; this rule does not remove our duties towards children who actually use the service.
This policy is effective from 2026-11-14. We update it when our processing changes and identify the new version and date. We will bring material changes to affected members' attention through the service or email as appropriate. A policy update is information about processing, not blanket consent to new purposes. Any consent or further agreement legally required for a change must be obtained separately.