ALNET WORK · PRIVACY

Privacy policy

Draft — not yet reviewed. This is not a final version.

Last updated: (draft)

What personal data AlNet Work processes, why, on what legal basis, who receives it and how long it is kept. It describes the service as it will work at launch.

Who is responsible

AlNet Work is run by Albanian Network, a founder-operated business in Tirana, Albania. Albanian Network is the controller of the personal data described here. [TO CONFIRM: legal form, registration number (NUIS/NIPT) and registered address of Albanian Network]

For any privacy question or request: Support. [TO CONFIRM: whether a data protection officer must be named, and whether an EU representative is needed for users in the European Union (GDPR Art. 27)]

Albania's current general law on personal data protection is Law No. 124/2024 of 19 December 2024. The EU General Data Protection Regulation (GDPR) may also apply. [TO CONFIRM: how Albanian law and the GDPR apply to the legal bases and rights described below, and whether Albanian Network must notify the Commissioner before processing]

What we process, why, and on what basis

We describe the legal bases under review below. They include contract (needed to provide the service you asked for), legal obligation, legitimate interest (ours, weighed against your rights) and consent.

Phone number and code (optional)

  • What: your phone number. To send you a one-time code (OTP) by SMS, we will use Twilio Verify, a service of Twilio in the USA. Twilio will receive your phone number and the code you type, to send the code and to check it. A code confirmation is valid for at most 5 minutes. The account service does not store your phone number. It stores only a keyed hash of it, used to find your account.
  • Why: to create your account or add a phone number to it, to sign you in, and to keep each phone number on only one account. A phone number is optional when you sign in with Apple or Google; a proven phone number is also the strongest way back into your account (see Recovery below).
  • Legal basis: contract. [TO CONFIRM: how long Twilio keeps the phone number — Twilio's documentation gives only a minimum of 30 days]

Sign in with Apple or Google

  • What: you can create your account with Apple, Google or your phone number; any one of them is a full account, and you can link the others later. Without an account you can only read posts. When you use Apple or Google, Apple or Google sends us a one-time sign-in token. We check it and keep only a one-way keyed code made from the account identifier, never your email address, your name or the identifier itself.
  • One account per contact: a phone number, an Apple ID or a Google account can belong to only one AlNet Work account. We compare the keyed codes to refuse a second account with the same contact (fraud prevention). You can remove a link in the app.
  • Apple token: if you use Sign in with Apple, we keep an encrypted Apple token, so that when you delete your account or remove the Apple link we can ask Apple to remove AlNet Work from your Apple ID. We delete it once Apple confirms, at the latest after 30 days if Apple does not answer.
  • Sign-up limits: new accounts are counted per internet address (at most 60 an hour) and per Apple ID, Google account or phone number (at most 3 tries an hour), in memory only, to stop mass sign-ups.
  • Legal basis: contract; legitimate interest in preventing fraud and abuse.

Recovery and the 72-hour wait

If your account is opened on a new device by a recovery (with an SMS code, Apple or Google), we record that recovery on your account. For the next 72 hours you cannot delete the account, link or remove an Apple or Google sign-in, or link a phone number. A linked Apple ID or Google account can open your account on a new phone without an SMS code, so this wait protects you if someone else got hold of one of them. During the wait, whoever proves the account's phone number with a new SMS code can remove an Apple or Google sign-in at once; we record that removal without the number. Legal basis: legitimate interest in the security of your account.

DeviceCheck (iPhone)

On iPhone the app uses Apple's DeviceCheck. Apple stores two bits for each device under our Apple developer account. These bits are shared across apps from the same developer account. We use one bit to remember that an AlNet Work account on this iPhone has already reached the earnings line (see Help), so that a new account on the same iPhone also needs a plan for new work. The app checks the iPhone when you create an account, and marks it when your account reaches the line, once plans are open. The DeviceCheck token is used for that one request and is never stored; on your account we keep only Apple's answer, never a device identifier. Apple keeps the bits even after the iPhone is reset. If Apple's check does not answer, creating an account, or that step, waits until it does. Legal basis: legitimate interest in preventing abuse.

Devices and keys

  • What: each device creates its own keys. Private keys stay on the device (Keychain). The servers keep only public keys, the device list, an installation ID and sessions.
  • Why: secure sign-in and end-to-end encryption of messages.
  • Legal basis: contract; legitimate interest in the security of the service.

Posts, offers and Scout

  • What: the posts you publish are public: title, text, category, city or area, price and the name you chose. On the website, phone numbers and email addresses in the text are hidden, and the location is rounded to a grid of about 100 m. The creator of a post sees the offers you make on it.
  • Photos and videos: the photos and videos you add to a post are public with it: up to 10 photos, and videos of up to 15 seconds at 720p, with their sound. Adding photos is free for everyone. The app removes location and other camera data from them before upload, and the server removes them again from the copy it publishes.
  • Where photos are kept: at launch, the server keeps only the cleaned copy of each photo and a small preview it makes from it; the file as uploaded is deleted once the photo is saved. Both are stored in Cloudflare R2 and served through Cloudflare's cache at a public address with a long random code: anyone who has that address can open the photo, without an account. When you withdraw the post, when it is hidden after a report, when a draft expires or when you delete your account, we delete both files and ask Cloudflare to clear its cached copies, and we retry until it has. A copy already in someone's browser or app can stay there for up to 1 hour. To stop abuse, each account can start at most 100 photo uploads a day and keep at most 500 MiB of photos.
  • Map pin (optional): if you add one, its exact point is stored with the post. Others see your pin rounded to about 100 m; only you see the exact point. The "Use current location" button reads your phone's location once, only when you tap it.
  • Scout: your Scout questionnaire answers are stored privately by the service and are not published without your confirmation. Scout also records your Yes, No and Change answers and the offers and jobs that follow from them, to improve its next suggestions. If you let Scout watch for you, it stores your goal (free text, up to 1,000 characters), how many matches a day you want (1 to 20) and your time zone.
  • Boosts: a boosted post goes through the same steps as any other post. A paid boost only gives it a better score in the feed, so it is shown more often than posts without a boost. To charge the post's creator, we count each account that the boosted post is shown to, once per account.
  • Why: to publish, match and show jobs and offers.
  • Legal basis: contract.

Scout and DeepSeek (the AI function is switched off today)

This section describes the older Scout path, not Anaia. Its data limits are not a promise about all AI functions; Anaia is described separately below.

  • Today: Scout has an optional function that uses AI models from DeepSeek, a company in China. This function is switched off today, and Scout sends nothing to DeepSeek.
  • Only with a plan: like all AI in the app, Scout's AI function will come only with a paid plan.
  • Once switched on: only then will Scout send DeepSeek, in China, the data below.
  • Questionnaire: your Scout questionnaire answers: what you offer or look for, trade categories, city and area, price ranges, languages and the options you chose.
  • Posts that Scout drafts: whether the post offers or looks for work, its category, city, area, price range and language.
  • Search with Scout: your search text as you write it, and the titles, sources and IDs of the search results it compares.
  • Scout memory: the kinds of your recent Scout events (for example Yes, No or Change), and the IDs of the posts, offers and jobs they concern.
  • Completed jobs: the job's ID.
  • Not sent: your account ID, your phone number, your name and the exact point of a map pin.
  • Transfer to China: see International transfers.

AI rewrite and DeepSeek (only with a plan; switched off today)

This section covers only the older single-box rewrite. Its payload and retention limits do not describe the new Anaia path below.

  • Today: the AI rewrite of post text is switched off, and nothing is sent to DeepSeek for it. It will come only with a paid plan, and plans are not open yet.
  • Once switched on: when you tap Shorter, More detail or Fix mistakes, our server sends DeepSeek, in the People's Republic of China, only the text of that box, the button you chose, its language and the box's length limit. It adds no separate account ID, name, phone number, place, questionnaire answers or photo fields; your text itself can contain personal data.
  • What we keep: not the text we send, only a fingerprint (hash) of it. We keep DeepSeek's answer for up to 7 days, so that a retry of the same request does not send the text again, and then delete it. In a draft, the new text stays until you change or publish it.
  • What DeepSeek keeps: DeepSeek processes this text in the People's Republic of China. DeepSeek's general privacy policy does not establish the processing rules for downstream application users' API data. Retention and training arrangements for our API account have not been verified. Before the AI rewrite is switched on, we ask DeepSeek not to use this text to train its models.
  • Legal basis: contract (a feature you ask for with a tap). Transfer to China: see International transfers.

Anaia: planned AI data sharing

Release status: this is a draft disclosure for the new Anaia path. Its account-level sharing permission and withdrawal controls are implemented in the source candidate. Backend migration, provider/privacy integration, release-build and device qualification, and deployment remain pending. This page does not activate Anaia. The older Scout and single-box rewrite described above are separate paths.

  • Your choice: before the app uploads personal context for Anaia, it must explain the recipients and data and ask for your explicit permission. A membership, an assistance setting or accepting general terms is not that permission. Declining must leave ordinary app functions available. Permission for a shared transcript must cover its participants; one person cannot authorize another person's private notes or photos. The shared-chat permission controls still require end-to-end qualification.
  • Cloudflare: the phone sends the permitted context over HTTPS to our Cloudflare Worker. Cloudflare processes it in readable form. Recovery copies use Cloudflare R2, Queues and Durable Objects, encrypted with a key held by the server. This is not device-only encryption: the service and selected AI providers can read the supplied content.
  • TypeSafe / JEV: routine decisions and relevance checks can receive the full context permitted for that turn: your request, selected messages, job records and language, and on private turns the permitted personal notes, job notes and approved-photo descriptions. Photo selection uses approved references, hashes and descriptions, not image bytes. Private guidance is therefore not confined to your phone.
  • DeepSeek: writing and complex answers can receive the permitted context, available tools and their results, and research excerpts when used. For a photo description it receives one explicitly approved analysis JPEG, at most 1024 pixels and 256 KiB, plus the language. It does not receive your whole album or the full-resolution publication file through that operation.
  • Job notes and search: DeepSeek can compress the current job's records, selected messages and previous job note, without personal notes, the photo gallery or images. Web research is restricted to an opened existing job chat; the search query is at most 128 characters and asks for up to four results. A query can itself contain personal information.
  • AlNet records: our backend receives authority records, hashes, usage and the proposed app content, including draft or task text and selectable questions. It does not receive the full personal prompt or transcript through the AI result callback. A personal-note update is represented there by a commitment, not the note's text. Do not treat this as a promise that our backend stores no text.
  • Our temporary AI storage: queued input expires after approximately 24 hours and is removed after a successful commit. Completed result and operation storage has a 90-day retention period; cleanup removes payloads before operational metadata and retries storage failures. Small financial records of known or unresolved charges remain without the model context. A timeout or withdrawal does not cancel a legitimate charge. These are service limits, not a provider deletion deadline.
  • What providers keep: TypeSafe states that JEV is not trained on customer requests or responses; service, billing, abuse-prevention and telemetry processing can still occur. Retention depends on the applicable agreements. We have not verified a zero-retention arrangement for our account. DeepSeek's Open Platform terms put downstream end-user privacy rules on us; its general privacy policy does not establish a fixed API retention period, an API no-training promise or an effective opt-out for our account. Those account arrangements remain unverified. DeepSeek processing in China also requires the unresolved transfer review below.
  • Withdrawing permission: the planned controls must stop new personal-data AI sharing and further authorized actions. Withdrawal cannot recall a request already sent, undo a completed action or prove that a provider deleted its copy. Reopening a saved answer or draft must not automatically start a paid generation. The permission and withdrawal checks still require end-to-end release qualification.
  • Personal notes and job notes: forgetting your personal notes is separate from the retained notes of a job. Job notes remain readable and downloadable after closure; the current app does not offer per-job Forget. Account deletion, backups and retention exceptions remain subject to the account-deletion and legal review below. No phone action described here sends a deletion request to an AI provider.
  • Your final decision: proposed posts and offers remain drafts for you to review and edit. You choose Publish or Submit. Anaia is not the marketplace's moderation or reporting service.

Agreed price and estimated earnings

  • What: when a job is agreed (Accept, or Agree to a counter-offer), the app sends the agreed terms of that offer to the server once. The server checks them against the offer's fingerprint and keeps only the agreed price and its currency, for the person who is paid (the worker on a job post, or the creator of a post that offers their own work). The proposal text, dates and attachments are not kept. With it we keep the price shown on the post at that moment and whether the worker or the payer completed the agreement, also after the post is deleted and after the poster deletes their account.
  • Why: to estimate what you earned through AlNet, which decides when a plan is needed for new work (see Help), and for your private earnings stats. Amounts in euro, dollar or pound are converted to lek at rates we set (today 1 USD = 80.98 ALL, 1 EUR = 94.75 ALL, 1 GBP = 108.92 ALL).
  • How long: 365 days after the agreement, then only per-currency totals (number of jobs, summed amount) until you delete your account. This record stays after the 72-hour reduction of a completed job. A job that ends as "It did not happen", with the first such answer within 72 hours of the agreement, stops counting (we keep only a yes/no mark, never when or by whom); we delete its record after 365 days. If the other person says it was done, it still counts.
  • The other person: if you delete your account, the price you agreed to pay for a job stays in the other person's earnings record for up to 365 days after the agreement, without your name or account. If the person who paid you deletes their account, your own record stays.
  • Who sees it: only you, in the app, as "about X lek from N jobs" for a period with at least 3 jobs, rounded down to 500 lek. Your profile card, which only your contacts and the people you deal with can see, shows jobs done, never money. Only one thing shows to others: when a client asks to hire you on your own post that offers your work while you need a plan, the client is told that the request is paused, which tells the client that you need a plan for new work. When you then choose a plan, that client gets one notification that you can accept now.
  • Legal basis: contract (the membership rules you accept); legitimate interest in applying them fairly.

Typical prices (market reference)

Once a week we compute a typical price per job category and city from: the agreed prices of jobs on AlNet (only where at least 5 different workers were paid by 5 other people), the prices shown on open posts, and the pay in public job listings that Scout reads (read as one day's pay). Each person or site counts once; each person's or site's value gets its own small random change (up to 10 %, the same for as long as that value does not change); the highest and the lowest value are left out and the result is rounded to 500 lek. It contains no names, accounts or IDs, and no single job's price is published in it. Someone who deliberately sets up several accounts around one person could still learn that person's usual agreed price to within about 10 %, and a round amount (such as a multiple of 5,000 lek) sometimes exactly; that is why the app shows estimates built on it only in rough steps. We use it to estimate what a job was worth when its agreed price is missing or unusually low. An erased account's jobs leave it at the next weekly computation. Legal basis: legitimate interest in a fair estimate.

Profile photo

A profile photo is optional. Only your own devices and your accepted contacts can see it; it is not public. Camera data is removed from it, and a replaced or removed photo is deleted. Legal basis: contract.

Reviews

  • Reviews: when a job is completed by both sides, each side can rate the other once, with 1 to 5 stars and an optional text of up to 500 characters. In the app a review is public with the month of the job and the label "verified client", never with the name of the person who wrote it. The website shows only the average and the number of reviews, from 3 reviews on. A text with a phone number, an email address or a street address with a house number is refused. You can withdraw your review at any time.
  • When you delete your account: the reviews you wrote lose their text and their link to you, and their stars stay as anonymous ratings. The reviews about you are deleted.
  • Legal basis: contract.

Messages, attachments and drafts

  • Messages and attachments are encrypted from device to device. The server stores ciphertext and sees only who, to whom, when, the kind and the size for that delivery. If you separately permit sharing context with Anaia, selected copies follow the readable AI path described above.
  • Drafts and their attachments synced between your devices are sealed (encrypted) to your devices; the server cannot read them through that sync. Drafts created through Anaia also have the AI processing described above.
  • Legal basis: contract.

Calls

  • What: calls are set up through our relay server. It sees who calls whom, when, and whether the call rang, was answered or ended. The data that sets up the call is sealed (encrypted) for your devices.
  • The call itself goes through our call relay, encrypted from device to device. The call relay sees the IP addresses of both phones; the two phones never see each other's IP address.
  • Legal basis: contract.

Contacts, blocks and mutes

The people you add as contacts (who asked and whether the other person accepted), the people you block or whose notifications you mute, and the labels you give your contacts. Each contact is stored by the other person's user ID; the app does not read your phone's address book. The servers can read this list: they use it to deliver messages and calls and to apply blocks and mutes in every service. Legal basis: contract.

Labels and preferences

Labels and preferences synced between your devices (for example saved posts) are stored readable by the server. Legal basis: contract.

Receipts

The message service issues signed receipts (stored, delivered, read). When you delete your account, each service records a signed deletion receipt; the deletion counts as complete only when all receipts exist and each of your devices has confirmed it, or when 30 days have passed for a device that never confirms. Legal basis: contract (delivery receipts); legitimate interest and legal obligation to prove that a deletion happened (deletion receipts).

Membership

Apple takes the payment. We receive Apple's signed transaction records (product, dates, transaction IDs), not your card. The same applies to reach packs, one-time purchases in the App Store. Legal basis: contract; legal obligation to keep accounting and tax records. [TO CONFIRM: how long transaction records must be kept for accounting and tax purposes under Albanian law]

Reports, moderation and appeals

Reports: who reported, which post or review, the reason and the time; review decisions and appeals; a record of each automatic erasure after a removal; limited records of refused reports, to stop abuse of reporting. Legal basis: legitimate interest in a safe service; legal obligation where the law requires us to act on illegal content.

Support mail

If you write to support: your email address, what you write and our replies. Why: to answer you and to handle privacy requests. Legal basis: legitimate interest; contract where the question is about your account. [TO CONFIRM: the legal basis for transferring support mail to Google in the USA; and how long support mail is kept — 12 months after the case is closed assumed, as a manual clean-up in the mailbox]

Problem reports from the app

If you report a problem in the app (by shaking your iPhone, or in Settings → Report a problem): what you write; a screenshot of the screen you were on, if you keep it (it can show anything that was on that screen, including messages, and you can remove it before sending); the name of that screen; the app version, language and light or dark mode; the iPhone model and iOS version; and, when you are signed in, your account and device IDs. Why: to find and fix the problem. Legal basis: legitimate interest; contract where the problem is about your account. We keep reports at Cloudflare (Workers and its D1 database, in its Eastern Europe region) and read them on our own computer. They are deleted 90 days after they arrive. To limit abuse we keep a code made from your network address and the day, not the address itself; the code cannot be turned back into the address and changes every day.

Notifications

When a notification is sent, Apple receives the device token and a generic alert, without the sender's name and without the message content. Notifications about offers and jobs (for example "A client wants to hire you. Choose a plan to accept." or a reminder the evening before a job) carry only a fixed text and the IDs of the offer, post or job, never names, prices or messages, and none is sent between two people after one has blocked the other. If a start time is set for a job, the server keeps that one date and time, to send both of you the reminder; we delete it with the job. For incoming calls the app registers a separate call token. Our servers delete a token 60 days after its last update. Legal basis: contract; you can turn notifications off in the iOS settings.

IP address

Once the app is in use, our servers will receive your IP address with every request from the app. Requests will be counted per IP address in memory, to limit how many requests from the same address are handled at once. Our servers that the app connects to keep access logs without client IP addresses and record errors without addresses. When an access log file is rotated (closed and replaced by a new one), we delete the old file automatically once it is older than 7 days, at the next rotation or restart of the web server. Legal basis: legitimate interest in the security of the service.

Automated decisions

Scout suggests matches; they are only suggestions, and you decide what to do with them. People make and answer offers themselves. A report on its own never hides a post; a person reviews it.

One rule runs automatically: the earnings line. In plain words:

  • The estimate: our server estimates what you earned through AlNet in the last 7 days, from the jobs you agreed, at the agreed price, checked against the market reference (see Typical prices above) when a price is missing or below half of the usual price. Help gives the exact rules.
  • The line: once plans are open, when the estimate reaches the line described in Help, you need a plan before you take new work: before a new offer, and before you accept a client on your own post that offers your work. The rule follows fixed numbers and never blocks work you already have. On an iPhone where another AlNet Work account already reached the line, a new account needs a plan for new work too (see DeviceCheck above).
  • A person reviews it: if you think your estimate is wrong, for example because a job should not count, write to Support. A person then reviews the estimate.

Apart from this rule, we make no decision with a legal or similarly significant effect on you by automated means alone.

Who receives data

We do not sell personal data and do not share it with ad networks. We use the providers below to deliver the service; unverified AI provider arrangements are explained under Anaia above:

  • Hetzner Online (servers): today the web server in front of api.alnet.work runs on our server at Hetzner, but no app service runs behind it yet. The account, post, offer, message, call, media and moderation services will run there. Location: EU. [TO CONFIRM: Hetzner region — Germany or Finland]
  • Cloudflare (this website, its database and bot protection, and the problem reports from the app): requests to alnet.work pass through Cloudflare's global network. The app will connect to our servers through the address api.alnet.work. That address is prepared but not in use yet. Once it is in use, the app's requests will also pass through Cloudflare, which will open and re-encrypt them on the way; messages stay encrypted from device to device. Off-site backup is not switched on yet either. Once it is, backup copies will be sealed (encrypted) on our server and then stored in Cloudflare R2 storage, with Western Europe as the chosen location. There they will be protected from deletion or change for their first 32 days. Cloudflare also receives the mail sent to our support address and forwards it to our support mailbox at Google (Gmail). Its Email Routing log keeps each message's sender, recipient and authentication checks for up to 30 days. Once the app is in use, the photos in posts will also be stored in Cloudflare R2 and served through Cloudflare's cache (see Photos and videos above).
  • Google (Gmail, our support mailbox; USA): it receives the support mail that Cloudflare forwards, and our replies are sent from it. If you sign in with Google, Google also sends us the sign-in token described above.
  • Apple (App Store billing, notifications, Sign in with Apple, DeviceCheck, and the map search and address lookup in the app, when you search for a place or place a map pin).
  • Twilio (Twilio Verify, one-time codes by SMS; USA), see above.
  • TypeSafe / JEV: permitted context for decisions and photo selection in the planned Anaia path, without image bytes; see Anaia above. Processing locations and account arrangements still need confirmation.
  • DeepSeek (Scout's AI function, the AI rewrite and the planned Anaia path; People's Republic of China): each path's data and limits are explained above. Retention, training arrangements and any opt-out for our API account remain unverified. Our request not to use data for training is not a confirmed opt-out.
  • The OpenStreetMap Foundation (map tiles on the website's map page).

Each provider must act under a data processing agreement. [TO CONFIRM: a data processing agreement is signed with each provider above]

We disclose data to authorities only when the law requires it. [TO CONFIRM: procedure for requests from the police, courts and other authorities]

International transfers

Our servers at Hetzner will process your data in the EU. Cloudflare also processes data in other countries, including the United States, and Apple will too. Twilio will process your phone number in the United States. Google processes support mail in the United States. If Scout's AI function or the AI rewrite is switched on, the data described above will go to DeepSeek in the People's Republic of China. For Anaia, TypeSafe also receives the permitted context; its processing locations and applicable safeguards still need confirmation. Albania is not in the EU: transfers to EU countries rely on their adequate level of protection; transfers to the United States and China need additional safeguards. [TO CONFIRM: legal basis for each transfer outside Albania, including to China if Scout's AI function or the AI rewrite is switched on — Commissioner authorisation or standard contractual clauses; for EU users, the EU–US Data Privacy Framework or standard contractual clauses; for DeepSeek, also whether consent is needed]

How long data is kept

Undelivered messages and attachments
48 hours, then deleted
Completed job
72 hours for the original job thread, then a minimal anonymous record remains; retained Anaia job notes are separate, as described above
Question whether to turn an offer into a post
10 days from the award; the offer thread is kept until then
Unsaved Scout results
7 days
External pages saved from Scout (on your devices)
30 days
Traces of deleted items in sync
30 days
Your Yes, No and Change answers to Scout, and your Scout watch goal
the answers until you delete your account; the goal until you replace it or delete your account
Digest of a deleted contact, so that another person's late edit cannot store the deleted account again
30 days
Call records (who called whom, and when)
at most 1 hour after the call ends; technical records of a call: 7 days
Notification and call tokens
60 days after their last update
Post or review removed after a report
hidden for 7 days, while the decision can still be reversed (the post's photos are deleted at once); then its content is erased and only a removal marker remains. An open appeal pauses this.
Removed post whose job was awarded
made anonymous 72 hours after the job is completed, or erased 30 days after the post expired; never within the first 7 days after the removal, and not while an appeal is open
Reports, moderation decisions and records of automatic erasures
reviewed for 90 days; automatic deletion after 90 days is not active yet [TO CONFIRM: retention period for moderation records and when the 90-day cleanup starts]
Technical deletion receipts
365 days after completion, then a minimal completion marker remains. For an offline device, its device code, enrollment, public verification key and wipe request remain until it reports erasure. The 30-day cutoff does not prove that an offline phone has erased its data.
Apple transaction records
as long as the law requires for accounting (see Membership above)
Support mail
12 months after the case is closed (assumed, see Support mail above); we delete it by hand from the support mailbox. Cloudflare's Email Routing log: up to 30 days
Problem reports from the app
90 days after they arrive; deleted automatically every day
Agreed price of a job (the earner's record)
365 days after the agreement, then only per-currency totals (number of jobs, summed amount) until the account is deleted
Job counts and earnings totals after an account is deleted (under one-way keyed codes)
Indefinitely for minimal anti-abuse markers and lifetime totals; 7-, 30- and 365-day totals continue to age from their original window start
Encrypted Apple token (Sign in with Apple)
until the account is deleted or the Apple link is removed and Apple confirms; at most 30 days after that
Photos in a post
until the post is withdrawn or hidden after a report, its draft expires or the account is deleted; a copy in a browser or the app: up to 1 hour more
Typical prices (market reference)
replaced every week
Start time of a job
deleted with the job
AI rewrite (once switched on)
on our server: only a fingerprint (hash) of the text sent, and DeepSeek's answer for up to 7 days; at DeepSeek: our API account's retention remains unverified; this row does not describe Anaia storage
Anaia (planned path)
queued input: approximately 24 hours, or until successful commit; completed result and operation: 90 days, with cleanup retrying storage failures; retained job notes and financial records: see Anaia above; provider retention remains unverified
Backups
35 days (planned; no production backup exists yet). Copies will be sealed (encrypted) before they leave our server. The off-site copies will be stored at Cloudflare R2, with Western Europe as their chosen location; R2 will delete them automatically after 35 days, and during their first 32 days they will be protected from deletion or change. [TO CONFIRM: how an account deleted after a backup was taken is deleted again if that backup is restored; how long copies stay on our own server; whether the EU jurisdiction setting of R2 is needed instead of a chosen location]

Deletion

You can delete your account at any time in the app. Ten parts of the service delete your data, and each records a signed receipt: account data, messages, notifications, calls, posts, offers, Scout, photos and videos, the profile photo, and moderation.

If one of your devices never confirms the deletion, the deletion is completed after 30 days and that device is revoked; it deletes the data it holds the next time it connects. A backup may keep the account until it expires.

When you delete your account we retain indefinitely only minimal anti-abuse markers under one-way keyed codes of your verified phone number, Apple ID and Google account. We keep job counts and per-currency earnings totals, including a marker when there are no earnings. These markers exclude your name, raw phone number, raw Apple or Google identifier, profile, content, sessions and private keys. If you verify the same sign-in method on a new account, the totals continue there; 7-, 30- and 365-day totals continue to age from their original window start. The codes share a random deletion number to prevent double counting; they are pseudonymous data, not anonymous. Their purpose is to prevent deleting and reopening an account to reset earnings checks. [TO CONFIRM: confirm the lawful basis, necessity and duration for indefinite anti-abuse retention before open testing]

After a recovery on a new device, deletion waits 72 hours (see Recovery above).

Your rights

You can ask whether we process your data and request access, a copy, correction, restriction of processing, or deletion. You can object to processing based on our legitimate interest. You can complain to the Commissioner for the Right to Information and Protection of Personal Data (Tirana).

If you are in the EU, the GDPR also gives you the rights to erasure, to restriction of processing, to data portability and to withdraw consent at any time; you can complain to the data protection authority of your country.

You delete your account yourself in the app. For every other request: Support. We answer within 30 days and never ask for your one-time code. [TO CONFIRM: response deadline — 30 days assumed — and how identity is checked without asking for the code (OTP)]

A copy of your data is provided on request. [TO CONFIRM: how a copy of the data (access, portability) is delivered — the app has no export feature yet]

Children

AlNet Work is for people aged 18 and over. We do not knowingly create accounts for anyone younger. If you believe a minor has an account, tell us through Support and we will delete it. [TO CONFIRM: minimum age — 18 assumed; the App Store age rating must match; the app does not check age]

Cookies and analytics

  • No analytics, no ad networks or tracking, and no third-party fonts. The app contains no analytics or tracking SDK.
  • This website sets no cookies of its own and stores nothing in your browser.
  • Searches are part of the address; the site's logs hide the search parameters and do not keep request addresses.
  • The map page loads tiles from tile.openstreetmap.org, which receives your IP address.
  • Cloudflare protects the site (Bot Fight Mode): it inspects requests and may add a script and a security cookie to tell people from bots. [TO CONFIRM: which cookies Cloudflare's bot protection sets on alnet.work, and whether this notice is enough under Albanian and EU rules]

Security

Private keys stay on your devices, messages are encrypted end to end, the servers keep phone numbers only as keyed hashes, and access to the servers is limited to the founder. If a breach puts your data at risk, we will tell the Commissioner and, where required, you. [TO CONFIRM: breach procedure and deadline — 72 hours to notify the Commissioner assumed]

Changes to this policy

We publish every new version on this page with a new date. For important changes we also tell you in the app before they apply. [TO CONFIRM: how and how early users are told of important changes — an in-app notice assumed]

Questions

For any question about your data: Support.

Other pages