Privacy

Analytics

A PRASA uses Plausible Analytics to understand general use of the website.

Pages on aprasa.org load Plausible's analytics script from plausible.io.

The technical audit did not identify custom Plausible event-tracking logic in the audited shared front-end implementation.

The audit did not establish the exact data fields, retention period, processing location, or contractual role applicable to Plausible's service. A PRASA therefore does not make broader claims about those matters here.

Cookies and browser storage

A PRASA's inspected front-end code does not currently set cookies through the browser document.cookie API.

That does not mean that no third-party service used by the website can ever set or use cookies, and A PRASA does not make that broader claim.

The Mindelo Essentials language selector uses the browser's local storage to remember one preference: aprasa-language.

This preference is used to remember the visitor's selected language. The inspected implementation does not send that stored language preference to an A PRASA server.

The technical audit did not identify A PRASA use of sessionStorage, IndexedDB, or service-worker storage.

Contacting A PRASA through WhatsApp

A PRASA currently uses WhatsApp as its principal public contact and submission route rather than operating an A PRASA-hosted contact form.

The site's contact panel may help a visitor prepare an intent such as:

• sharing an event or opportunity;
• reporting incorrect or outdated information;
• asking a general question;
• asking about submissions.

Selecting one of these options inside the A PRASA website does not by itself send information to WhatsApp.

Information is passed into the WhatsApp interaction only when the visitor chooses to open WhatsApp through the provided action.

Once a visitor opens or uses WhatsApp, that interaction takes place through a third-party service. A PRASA does not control WhatsApp's own privacy or data-processing practices.

Forms

A PRASA does not currently operate a first-party web form for public submissions on aprasa.org.

Netlify Forms are not enabled for the separate Netlify project associated with A PRASA's deployment-preview workflow.

Some A PRASA listings link to application, registration, booking, or contact systems operated by third parties. Information submitted through those external services is handled by the relevant provider, not through an A PRASA web-form backend.

Email and other external links

Some listings include mailto: links or links to external websites and services.

Selecting those links may open a visitor's email application or take the visitor to another organization's website.

Those external services have their own privacy practices. A PRASA does not control how third parties process information after a visitor leaves aprasa.org.

Maps

Mindelo Essentials uses Leaflet for its interactive map and loads Leaflet resources through unpkg.com.

Map tiles are loaded from OpenStreetMap infrastructure at tile.openstreetmap.org.

A PRASA's map data itself is loaded from an A PRASA same-origin GeoJSON file.

The audited map does not request the visitor's physical location through browser geolocation.

Loading third-party map resources causes the visitor's browser to communicate with those third-party services. A PRASA does not make unverified claims about what those services retain or how long they retain it.

Fonts and other third-party resources

A PRASA currently loads font resources through:

• fonts.googleapis.com
• fonts.gstatic.com

As with other third-party resources, the visitor's browser communicates directly with those services when those resources are requested.

A PRASA does not state here what information those third-party providers retain unless that has been separately verified.

Hosting and website delivery

The production A PRASA website is hosted through GitHub Pages.

The production site is published from the main branch of the A PRASA GitHub repository and uses the custom domain aprasa.org.

HTTPS enforcement is enabled.

The authoritative DNS records for aprasa.org point directly to documented GitHub Pages destinations. No additional proxy or CDN was identified in the configured production DNS path.

This does not mean that no network infrastructure exists within GitHub's own service.

A PRASA has not established an authoritative retention period or processing geography for ordinary GitHub Pages production request logs and therefore does not make such a claim here.

Netlify

A PRASA also has a separate Netlify project used for deployment previews and related development workflows.

Netlify is not the production host for aprasa.org.

The inspected Netlify project:

• does not have aprasa.org configured as a custom production domain;
• does not have Netlify Forms enabled;
• has no exposed or configured project-level environment variables identified in the audit;
• cannot have a customer-configured Netlify Log Drain under its current Free team plan.

These facts should not be interpreted as a claim that Netlify itself maintains no operational logs for its services.

Information sent directly to A PRASA

If you voluntarily contact A PRASA—for example through WhatsApp—the information you choose to send may be reviewed and used to:

• respond to your message;
• assess a submission;
• investigate a correction or report;
• verify information for editorial purposes;
• maintain the quality and accuracy of A PRASA's public information.

Do not send sensitive personal information unless it is genuinely necessary for the matter you are contacting A PRASA about.

Corrections and privacy questions

If you believe information published by A PRASA is incorrect, outdated, or raises a privacy concern, you can contact A PRASA through the contact options provided on the website.

A PRASA may need enough information to understand and evaluate the request, but you should provide only what is reasonably necessary.

Changes to this Privacy notice

A PRASA may update this Privacy notice when the website, its services, or its data practices materially change.

The current public version should reflect the practices actually in use rather than planned future features.